Siebel CRM software

This tutorial takes you through the recording of a Siebel application. To gain the most from this tutorial, it is recommended to read Siebel requests.

Understand the context

In the same way that NeoLoad lets you define and load test HTTP exchanges, NeoLoad provides the means to load test Siebel requests, which are themselves based on the HTTP protocol. Siebel requests are in many ways similar to standard HTTP requests, which means that all the features NeoLoad provides for HTTP requests will be available for Siebel. This includes, among others, using variables, defining validation expressions and of course obtaining load test results.

Record a Siebel request

To record Siebel requests, see Record a test scenario.

It is important to remember that Siebel requests and responses use a specific formalism. One of the simplest examples of the syntax used is the delimiting of each value by the integer representing the number of characters it contains. Thus, the list of values "software, NeoLoad, Siebel" is encoded as "8*software7*NeoLoad6*Siebel". Other, more complex data formatting would normally make configuring a scenario impossible without some kind of decoding tool.

Recording a Siebel scenario is straightforward however and requires no configuring. To record a Siebel request, follow these steps:

  1. When you close the browser at the end of recording, the Post-Recording wizard is displayed.

  2. One of the steps in the wizard allows you to integrate Siebel framework parameters. For more information about the Siebel framework parameters generated by NeoLoad, read Identifiers handled by NeoLoad. For more information about the next steps in the wizard, see Post-recording wizard.

  3. For each request and response, NeoLoad replaces the raw content with an XML file.

Note: In the Virtual User, the Siebel requests are identified by a special icon. An appropriate page name is automatically provided by NeoLoad according to the request that was executed.

Detect Siebel errors

Error messages may be returned by the Siebel server. For example, when a user carries out an action on a badly-configured Siebel component, a warning message is displayed.

Checking a Virtual User validity enables these types of errors to be detected. For more information about validating Virtual Users, see Post-recording wizard.