Skip to main content

Siebel Web Protocol in Loadrunner - Challenging protocol in Loadrunner

Siebel Customer Relationship Management (CRM) is one of the top CRM applications, which help organizations to achieve maximum sales, marketing, customer service etc.

Siebel protocol is similar to Web (HTTP/HTML) protocol, but has made lot of changes to the settings to work with Siebel Web Protocol. It is one of the complex protocols where we face lot of issues during scripting, but HP has provided predefined correlation rules, which will help you the scripting easy.

Before recording make sure you set the following recording options:

  1. Go to Recording Options (CTRL+F7) -> Recording -> HTML-based script -> HTML Advanced and set “A script containing explicit URLs only (e.g. web_url, web_sumit_data)”.
    Siebel Recording Options 1
    Siebel Recording Options 1
  2. In, “Non HTML-generated elements (e.g. JavaScript, VBScript, ActiveX, Applets)” set “Do not Record”.
  3. Go to HTTP Properties -> Advanced node and set “clear the Reset context for each action check box”. 
    Siebel Recording Options 2
    Siebel Recording Options 2

Set the following run-time settings after recording:

Go to Run-time settings -> Browser -> Browser Emulation and set “simulate new user on each iteration”.

Siebel Runtime Settings
Siebel Runtime Settings
Some of the Common Errors in Siebel Protocol:

Back or Refresh Error:

We get error, when we pass the wrong TimeStamp or SWEC Count. For every request, the SWEC count will increase, if we pass the wrong SWEC, it will fail by throwing “Back or Refresh Error”.

Server Busy Error:

The following error is one of the common error which we get frequently during scripting and execution.

"The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[01:55:21] "

The main cause for this the sessions might be less, we should ask for Siebel administrator to increase the sessions in the server.

The following commands will be useful to increase the sessions in the server:

srvrmgr:dev_srv1> CHANGE PARAM MAXMTsERVERS=4 FOR COMP eautoObjMgr_DB
Command completed successfully.

srvrmgr:dev_srv1> CHANGE PARAM MAXTASKS=400 FOR COMP eautoObjMgr_DB
Command completed successfully.


Popular posts from this blog

File operations in loadrunner with examples

In this post I will explain how to capture a value from server response and save to a text file using vugen. How to capture and save to text file using loadrunner: First I have recorded the script using and then i searched for IBM. We will get 10 results. I have captured all the 10 values and saved to a file. Here is the code for that.

NeoLoad Interview Questions and Answers

Here are some of the interview questions and answers on NeoLoad: What is NeoLoad? NeoLoad is a performance testing tool designed to test different types of web, standalone and mobile applications. What is the difference between Loadrunner, JMeter and NeoLoad? Click here for differences What are the different counters you monitor in NeoLoad? Average Response Time(requests), average response time(pages), average requests/s, average throughput, current response time(requests), current response time(pages), current requests, current throughput, current users count, controller cpu load, controller memory load etc. What are the different type of tools you can integrate with NeoLoad? App Dynamics, CA APM Integration, Dyna trace integration, HP ALM or Quality Center Integration, Java and Jamo Solutions M-eux Test Integration, Jenkins Integration, perfecto mobile integration, selenium integration. What are the different type of Operating systems you can mon

LR Functions with Examples | Loadrunner Functions with Examples

LR Functions in Loadrunner with Examples. lr_abort Stops the script execution. lr_advance_param It will take the next value in the parameter list. lr_continue_on_error Continue on error even if the request is failed. lr_convert_string_encoding Converts a string to a UTF 8 or Unicode. lr_db_dataset_action Validates database contents by setting checkpoints. lr_db_connect Connects to a database. lr_db_dataset_action Performs an action on a dataset. lr_db_disconnect Disconnects from a database. lr_db_executeSQLStatement Submits an SQL statement to a database. lr_checkpoint Validates the value of a parameter against an expected value (checkpoint). lr_db_getValue Retrieves a value from a dataset. lr_debug_message Sends a debug message to the LoadRunner output or Application Management agent log file. lr_decrypt Decrypts an encoded string. lr_disable_ip_spoofing Disables IP Spoofing. lr_enable_ip_spoofing Enables IP Spoofing. lr_end_sub_transaction Marks the end of a sub-tr