SIEBEL PROTOCOL SCRIPTING USING LOADRUNNER

Preparation before record – Internet Explorer Settings
To avoid problems, verify the following Internet Explorer’s settings before you proceed to record:

1. Enable all ActiveX controls and plug-ins. This option is available in Internet Explorer > Tools > Internet Options > Security > Custom Level.
2. Enable the “Use HTTP 1.1 through proxy connection” option. This option is available in Internet Explorer > Tools > Internet Options > Advanced, under the “HTTP 1.1 settings” radio button.

Recording Siebel script with Auto-Correlation option
For Siebel script, you can instruct VuGen to automatically apply correlation during recording using one of the following methods:
· VuGen Native Siebel Correlation
The native, built-in rules, work on a low level, allowing you to debug your script and understand the correlations in depth.
· Siebel Correlation Library
The Siebel correlation library automatically correlates most of the dynamic values, creating a concise script that you can replay easily. Note that this is only available for Siebel 7.7 and the library is distributed by Siebel.
How to record with VuGen Native Siebel Correlation
VuGen’s native built-in rules for the Siebel server detect the Siebel server variables and strings, automatically saving them for use at a later point within the script. It is available in VuGen recording option by default; you do not need to have any additional components installed.

Steps to record with Native Siebel correlation:

1. From the ‘New Multiple Protocol Script’ window, add ‘Siebel-Web’ and click OK.
2. Set the following Recording Options:
• Internet Protocol: Recording:
• Select ‘ HTML based script
• Click on ‘HTML Advanced’ and select the following
• Script Type: a script containing explicit URLs only
• Non HTML-generated elements: Do not record
• Internet Protocol: Advanced:
• Clear the ‘Reset context for each action’ option.
• Select ‘Support Charset’ then select ‘UTF-8’
• Internet Protocol: Correlation:
• Make sure that you have ‘Enable Correlation during recording’
• Make sure that ‘Siebel’ is selected. You can expand the list to see the details about each rule if you wish.
• Leave other options as default.

Challenges Faced
Error: “We detected an Error which may have occurred for one or more of the following reasons: We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.”

Diagnosis: A HTTP request has been sent twice to the server. This could be an individual web_url request or part of the resources being downloaded from another request. When sending the second request to the server, the Siebel 7.x server detects multiple requests and thus, issues the above error.

Solution:
1. Change the Mode in earlier call from "Mode=HTML" to “Mode=HTTP”
The idea behind changing the mode from HTML to HTTP is to avoid parsing the HTML page that is returned by the server, so that resources are not downloaded. This helps to avoid multiple downloads of same request.

2. Disable the Run-Time Viewer:
If the script still fails on the first iteration after the change from step 1, try after closing the Run-Time Viewer.

3. Correlate SWECount or SWEC
If you are able to run the first iteration, but the script fails on the second iteration or onwards, you will need to correlate SWECount (7.0.3) or SWEC (7.0.4) from the previous step “start.sweXXX.”

4. Run the script with the extended log
If none of the above helps, replay the script with the extended log and identify the HTTP request that is being downloaded multiple times. Search for a similar HTTP Request being sent earlier in the execution log. Once you locate the same, set “Mode=HTTP” so that the resources for that request are not downloaded, and try replaying the script again.