Siebel - Web protocol

The Siebel - Web protocol is similar to the standard web Vuser protocol, with several changes in the default settings to allow it to work with the Siebel Customer Relationship Management (CRM) application. When you record a Siebel session, VuGen generates functions with a web_ prefix to emulate your actions.

Note: You can also generate a Siebel - Web Vuser script by analyzing an existing network traffic file (capture file). This method may be useful for creating Vuser scripts that emulate activity on mobile applications. For details, see Create a script from a captured traffic file.

Siebel - Web recording options and runtime settings

Before recording a Siebel - Web Vuser script, set the following recording options:

  • Recording node: HTML-based script

    HTML Advanced - Script type: A script containing explicit URLs only

    HTML Advanced - Non HTML-generated elements: Do not record

  • Advanced node: Clear the Reset context for each action check box.

    Before running the script, set the following runtime setting:

    In the Runtime Settings, clear the Simulate a new user on each iteration check box in the Browser Emulation node.

Record transaction breakdown information

VuGen provides a diagnostic tool for understanding the transaction components in your test—transaction breakdown. Using transaction breakdown, you can determine where the bottlenecks are and the issues that need to be resolved.

When preparing your script for transaction breakdown, we recommend that you add think time steps at the end of each transaction using the ratio of one second per hour of testing. For more information about adding think time steps, see Insert steps into a script.

In order to record the transaction breakdown information, you need to modify your the parameterization functions in your script.

Prepare your script for transaction breakdown

  1. Identify the script parameterization replacement of the Session ID.

     /* Registering parameter(s) from source task id 15
    // {Siebel_sn_body4} = "28eMu9uzkn.YGFFevN1FdrCfCCOc8c_"
    // */
    web_reg_save_param("Siebel_sn_body4",
        "LB/IC=_sn=",
        "RB/IC==;",
        "Ord=1",
        "Search=Body",
        "RelFrameId=1",
        LAST);

  2. Mark the next web_submit_data function as a transaction by enclosing it with lr_start_transaction and lr_end_transaction functions.

  3. Before the end of the transactions, add a call to lr_transaction_instance_add_info, where the first parameter, 0 is mandatory and the session ID has a SSQLBD prefix.

    lr_start_transaction("LoginSQLSync");
    web_submit_data("start.swe_2",
        "Action=http://design/callcenter_enu/start.swe",
        "Method=POST",
        "RecContentType=text/html",
        "Referer=http://design/callcenter_enu/start.swe",
        "Snapshot=t2.inf",
        "Mode=HTML",
        ITEMDATA,
        "Name=SWEUserName", "Value=wrun", ENDITEM,
        "Name=SWEPassword", "Value=wrun", ENDITEM,
        "Name=SWERememberUser", "Value=Yes", ENDITEM,
        "Name=SWENeedContext", "Value=false", ENDITEM,
        "Name=SWEFo", "Value=SWEEntryForm", ENDITEM,
        "Name=SWETS", "Value={SiebelTimeStamp}", ENDITEM,
        "Name=SWECmd", "Value=ExecuteLogin", ENDITEM,
        "Name=SWEBID", "Value=-1", ENDITEM,
        "Name=SWEC", "Value=0", ENDITEM,
        LAST);
lr_transaction_instance_add_info(0,lr_eval_string("SSQLBD:{Siebel_sn_body4}"));
lr_end_transaction("LoginSQLSync", LR_AUTO);

    Note: To avoid session ID conflicts, make sure that the Vusers log off from the database at the end of each session.

Known issues for Siebel - Web

This section describes troubleshooting and limitations for Siebel - Web Vuser scripts.

Tip: For general troubleshooting and limitations, see Known issues.

Recording High Interactivity client

The Siebel High Interactivity client is only supported with a 32-bit Internet Explorer, version 9 and earlier. To record this type of session, check your browser version and downgrade if necessary. Alternatively, you can use proxy recording. For details, see Record using a proxy.

Back or Refresh error

An error message relating to Back or Refresh typically has the following text:

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.

Cause: The possible causes of this problem may be:

  • The SWEC was not correlated correctly for the current request.

  • The SWETS was not correlated correctly for the current request.

  • The request was submitted twice to the Siebel server without the SWEC being updated.

  • A previous request should have opened a frame for the browser to download. This frame was not created on the server probably because the SWEMethod has changed since the recording.

Same Values

A typical web page response to the Same Values error is:

@0`0`3`3``0`UC`1`Status`Error`SWEC`10`0`1`Errors`0`2`0`Level0`0`ErrMsg`The same values for 'Name' already exist. If you would like to enter a new record, please make sure that the field values are unique.`ErrCode`28591`

Cause: The possible cause of this problem may be that one of the values in the request (in the above example, the value of the Name field) duplicates a value in another row of the database table. This value needs to be replaced with a unique value to be used for each iteration per user. The recommended solution is to replace the row ID with its parameter instead insuring that it is unique.

No Content HTTP Response

A typical HTTP response for a No Content HTTP Response type error is:

HTTP/1.1 204 No Content

Server: Microsoft-IIS/5.0

Date: Fri, 31 Jan 2003 21:52:30 GMT

Content-Language: en

Cache-Control: no-cache

Cause: The possible causes of this problem may be that the row ID is not correlated at all or that it is correlated incorrectly.

Restoring the Context

The typical web page response to the Restoring the Context type error is:

@0`0`3`3``0`UC`1`Status`Error`SWEC`9`0`1`Errors`0`2`0`Level0`0`ErrMsg`An error happened during restoring the context for requested location`ErrCode`27631`

Cause: The possible causes of this problem may be that the rowid is not correlated or that it is correlated incorrectly.

Cannot locate record

The typical web page response to the Cannot locate record type error is:

@0`0`3`3``0`UC`1`Status`Error`SWEC`23`0`2`Errors`0`2`0`Level0`0`ErrMsg`Cannot locate record within view: Contact Detail - Opportunities View applet: Opportunity List Applet.`ErrCode`27573`

Cause: The possible causes of this problem may be that the input name SWERowId does not contain a row ID for a record on the web page. This input name should have been parameterized. The parameter's source value may have changed its location.

End of File

The typical web page response to the End of File type error is:

@0`0`3`3``0`UC`1`Status`Error`SWEC`28`0`1`Errors`0`2`0`Level0`0`ErrMsg`An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.`ErrCode`28601`

Cause: The possible causes of this problem may be that the input name SWERowId does not contain a row ID for a record on the web page. This input name should have been parameterized. The parameter's source value may have changed its location.

Unable to Retrieve Search Categories

The typical web page response to the Unable to Retrieve Search Categories type error is:

Cause: A possible cause of this problem may be that the search frame was not downloaded from the server. This occurs when the previous request did not ask the server to create the search frame correctly.

See also