Siebel Architecture
Siebel Load Runner- Recording - Prerequisites
Siebel High Interactivity Frame Work automatically install once you run Siebel client first time. Some user get below error after entering userid/pwd.
Siebel Recording Setup:
Siebel LR Scripting Issues & Solutions• Document Business Process required to be performance tested with following details:
• User Responsibility
• User Position
• Detailed Screen Navigations
• Test Data Required for each Step
• SLA for transactions.
• The library file, ssdtcorr.dll, must be available to all machines where a Load Generator, Controller, or Tuning Console resides
Issue 1: An end of file error has occurred.Steps for Troubleshooting:
- Check the script where it failed and check for the rowid.
- Now go to the place in script where the web_reg_save_param () is placed and select the succeeding request in the script.
Issue 2: The selected record has been modified by another user since it was retrieved.Steps for Troubleshooting:
- Select the request and check for the parameter that is getting passed.
- Open the Siebel Application and navigate thru the workflow to check if the value has been already used for the particular scenario. If yes, delete the value in Parameter file and run it.
Issue 3:Wrong field values or value types detected in field %1. Please re-enter your field values.Steps for troubleshooting:
- This error happens when the LR date format doesn't match with the Siebel date format.
- If the Field name you were searching for, is found, Check for the values you have provided as input.
Issue 4:We detected an Error which may have occurred for one or more of the following reasons. We are unable to process your request.Steps for troubleshooting:
• This error happens due to difference in SWEC values or uncorrelated SWEC values.• Make sure that you correlate the SWEC values and use it in subsequent requests or follow the addition approach used in LR.
- Ensure User Setup and Test Data setup is completed before commencing test scripts development.
- Ensure User Responsibilities and positions are intact to access required screens and data. Parameterize the data specific to user profile. Do not use the Admin responsibility, if it is not required for scripts development or execution.
- Define Search /Query criteria inline to business needs, response times significantly vary depending on Fields populated and values used to populate the fields, User responsibility and Position
- Ensure at least one record present all default views -> list applets / form applets before commencing test scripts development.
- Ensure following data fields are either correlated or parameterized.
- Unique Constraints
- Data Dependent Fields
- Date and Time Zone Fields
- Search / Query Fields
- Ensure “Think times” and “Pacing” are intact with Seibel Session timeout value.
- In List Applet, ensure columns displayed, order of columns displayed same as what was record. Otherwise, scripts will fail.
- If possible, restart the Siebel Services in between the performance tests to clear any orphan sessions.
- Ensure that environment configured as close as possible to production.
- Ensure all “Actions” are independent and do not dependent on data correlated in previous “Action”. Start and Stop all the actions by Clicking on ‘Sitemap’.
- Reset the SWE Count to the SWEC value in beginning of each iteration. Otherwise it may throw ‘Back or Refresh Error’.
- Ensure that all the Row ID parameters are correlated or parameterized. Otherwise it may throw errors ‘End of file Error occurred’, ‘Can’t locate record’ or ‘Restoring the context error’.
- Ensure multiple users are not updating the same record at same time. This will result in concurrency errors.
- If you decide to correlate the Siebel Dynamic values manually then, make sure that you use star array for correlating SWERowid appearing in the script. Because, the star array would have all the necessary details about the record manipulated/selected. There will be also a same value appearing with `i` as Left Boundary and ` as right boundary which would not be suitable for correlation in rare cases.