18_Siebel Scripting Standards and Best Practices

7/26/2019 18_Siebel Scripting Standards and Best Practices

1/17

Siebel Scripting Standardsand Best Practices

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL1

upes arg, runa r s na


2/17

Siebel Scripting Standards and Best Practices

Introduction to Siebel Scripting Standards

Siebel Architecture


Siebel Load Runner- Recording Prerequisites

Siebel Load Runner Scripting Issues & Solutions

Siebel Scripting Best Practices


3/17

Introduction to Siebel Scripting



4/17

Introduction

This PPT makes a sincere attempt to explain what the key challenges

in Siebel scripting are and what are the best practices to be followed toavoid it. It can serve as practical guide for technical users, consultants,and programmers who design and implement test scripts and scenarioswith Load Runner. Most of the information contained in this document


based on "real-life" problems encountered in the field. This documentgives guidelines on virtual user script recording & playback, andcontroller configuration & settings.


5/17

Siebel Architecture



6/17

Siebel Architecture



7/17

Siebel Load Runner- Recording



8/17


Siebel Application Launch Prerequisite:

Siebel High Interactivity Frame Work automatically install once yourun Siebel client first time. Some user get below error after enteringuserid/pwd.



9/17


Siebel Recording Setup:

Document Business Process required to be performance tested withfollowing details:

User Responsibility


Detailed Screen Navigations

Test Data Required for each Step

SLA for transactions.

The library file, ssdtcorr.dll, must be available to all machines where aLoad Generator, Controller, or Tuning Console resides


10/17

Siebel Load Runner Scripting Issues &



11/17

Siebel LR Scripting Issues & Solutions

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 itwas 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 ifthe value has been already used for the particular scenario. If yes,delete the value in Parameter file and run it.


12/17

Siebel LR Scripting Issues & Solutions

Issue 3:Wrong field values or value types detected in field %1. Pleasere-enter your field values.

Steps for troubleshooting:

This error happens when the LR date format doesnt match with theSiebel date format.

If the Fieldname you were searching for, is found, Check for thevalues you have provided as input.


Issue 4:We detected an Error which may have occurred for one ormore of the following reasons. We are unable to process your request.

Steps for troubleshooting:

This error happens due to difference in SWEC values or uncorrelatedSWEC values.

Make sure that you correlate the SWEC values and use it insubsequent requests or follow the addition approach used in LR.


13/17

Siebel Scripting Best Practices



14/17

Siebel Scripting Best Practices(i)

Ensure User Setup and Test Data setup is completed beforecommencing test scripts development.

Ensure User Responsibilities and positions are intact to accessrequired screens and data. Parameterize the data specific to userprofile. Do not use the Admin responsibility, if it is not required forscripts development or execution.

Define Search /Query criteria inline to business needs, response


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


15/17

Siebel Scripting Best Practices(ii)

Ensure Think times and Pacing are intact with Seibel Sessiontimeout value.

In List Applet, ensure columns displayed, order of columns displayedsame as what was record. Otherwise, scripts will fail.

If possible, restart the Siebel Services in between the performancetests to clear any orphan sessions.


Ensure that environment configured as close as possible toproduction.

Ensure all Actions are independent and do not dependent on datacorrelated in previous Action. Start and Stop all the actions byClicking on Sitemap.

Reset the SWE Count to the SWEC value in beginning of eachiteration. Otherwise it may throw Back or Refresh Error.


16/17

Siebel Scripting Best Practices(iii)

Ensure that all the Row ID parameters are correlated or

parameterized. Otherwise it may throw errors End of file Erroroccurred, Cant locate record or Restoring the context error.

Ensure multiple users are not updating the same record at sametime. 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 SWERowidappearing in the script. Because, the star array would have all thenecessary details about the record manipulated/selected. There willbe also a same value appearing with `i` as Left Boundary and ` as

right boundary which would not be suitable for correlation in rarecases.


17/17

Aruna & Krishna

Performance Test Engineers


Date post:	01-Mar-2018
Category:	Documents
Upload:	pratik-rohit
View:	214 times
Download:	0 times

18_Siebel Scripting Standards and Best Practices

Documents