Re: LR 11.51 Siebel script is failing for 2nd iteration (166 Views)
Reply
Occasional Advisor
Nishanth Soundararajan
Posts: 11
Registered: ‎06-11-2010
Message 1 of 5 (231 Views)

LR 11.51 Siebel script is failing for 2nd iteration

Hi,

I have recorded the Siebel CRM using the Loadrunner 11.51Siebel web protocol. 
I have used the Siebel correlation library while recording the script. 

 

I have done manual correlation for _sn.I have also incresed the parameter length of problemetic parameter  Siebel_Star_Array110_rowid to 99999.


The replay is sucessful for a single iteration.

 

But when we are running for mutiple iterations, the script is only passing the 1st iteration and failing at the subsequent iterations.

 

The script is passing at the correlated parameter "Siebel_Star_Array110_rowid" while running for the 1st iteration.

Replay extended log(with parameter substitution) for 1st Iteration:

 

Action.c(437): web_submit_data("start.swe_16") started      [MsgId: MMSG-26355]
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_rowid" =  "1SIA-5VT8"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_SWECount" =  "6"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_1" =  "04757GC1B837DC526"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" =  "Vehicle Admin"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" =  "Vehicle Admin"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" =  "Vehicle Admin"
Action.c(437): Notify: Parameter Substitution: parameter "SRN_Param" =  "em5VZBI694AirMRd1NSi9fAOUADi9YcdBcPnjccapR4b"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_5" =  "Hyundai"
Action.c(437): Notify: Parameter Substitution: parameter "SiebelTimeStamp" =  "1383655597773"
Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" =  "Vehicle Admin"
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_1 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_2 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_3 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_4 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_5 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_6 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_7 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_8 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_9 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_10 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_11 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_12 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_13 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_14 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_15 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_16 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_17 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_18 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_19 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_20 = SADMIN".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_21 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_22 = Default Organization".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_23 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_24 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_25 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_26 = USD".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_27 = 11/05/2013".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_28 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_29 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_30 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_31 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_32 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_33 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_34 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_35 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_36 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_37 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_38 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_39 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_40 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_41 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_42 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_43 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_44 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_45 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_46 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_47 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_48 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_49 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_50 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_51 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_52 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_53 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_54 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_55 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_56 = ".
Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110_rowid = 1-1X7Q9F".
Action.c(437): web_submit_data("start.swe_16") was successful, 4161 body bytes, 293 header bytes    [MsgId: MMSG-26386]

But the script is failing at the correlated parameter "Siebel_Star_Array110_rowid" while running for the 2nd iteration.

 

Replay extended log(with parameter substitution) for 2nd Iteration: 

Action.c(437): web_submit_data("start.swe_16") started [MsgId: MMSG-26355]

Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_rowid" = "1SIA-JN6P" Action.c(437): Notify: Parameter Substitution: parameter "Siebel_SWECount" = "11"

Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_1" = "0FORDJIKJI890909080" Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" = "1SIA-5VT8" Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" = "1SIA-5VT8" Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" = "1SIA-5VT8" Action.c(437): Notify: Parameter Substitution: parameter "SRN_Param" = "em5VZBI694AirMRd1NSi9fAOUADi9YcdBcPnjccapR4b"

Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op90_5" = "Mercedez" Action.c(437): Notify: Parameter Substitution: parameter "SiebelTimeStamp" = "1383655607466"

Action.c(437): Notify: Parameter Substitution: parameter "Siebel_Star_Array_Op92_rowid" = "1SIA-5VT8" Action.c(437): Error -26377: No match found for the requested parameter "Siebel_Star_Array110". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 99999 bytes, use web_set_max_html_param_len to increase the parameter size [MsgId: MERR-26377] Action.c(437): Notify: Saving Parameter "Siebel_Star_Array110 = ". Action.c(437): web_submit_data("start.swe_16") highest severity level was "ERROR", 980 body bytes, 267 header bytes [MsgId: MMSG-26388]

 

Please help me resolving the above issue.

Please use plain text.
Frequent Advisor
xtom
Posts: 52
Registered: ‎06-06-2012
Message 2 of 5 (211 Views)

Re: LR 11.51 Siebel script is failing for 2nd iteration

Hello!

 

My experience in SIEBEL is that a second iteration in an active session is not the same as the first iteration. To see the difference do the follwing:

 

1. Use the init section to log in

2. Use the action section to do the flow

3. Create a new action block and record exactly the same flow as you did in step 2 in the action section

4. Use the end section to log off

 

Then you have to compare the first and the second action section and see what needs to be correlated.

 

But this also means:

If you do the login, the flow and the logout together in the action section, you can do as many iterations as you like.

 

The SIEBEL behaviour only is different if you try to repeat a flow without log out. Some numbers are increased in the second iteration. They need to be correlated.

 

Regards

Thomas

Please use plain text.
Occasional Advisor
Nishanth Soundararajan
Posts: 11
Registered: ‎06-11-2010
Message 3 of 5 (199 Views)

Re: LR 11.51 Siebel script is failing for 2nd iteration

Thank Thomas.

 

I recoredred the same flow in two actiosna nd compared the both.I couldnot be able to find the culprit parameter number which can be correlated.I have attached the 2 actions script for your reference.Please help me out in resolving this issue.

 

Note:For the first time I m using Siebel web portocol for testing.

 

Thanks in advance for your help.

 

 

Please use plain text.
Frequent Advisor
xtom
Posts: 52
Registered: ‎06-06-2012
Message 4 of 5 (176 Views)

Re: LR 11.51 Siebel script is failing for 2nd iteration

Hello!

 

I did not use SiebelWeb protocol. I used Web/HTTP/HTML). So i do not have experience in this.

Maybe you should try to record using the web protocol to get more details that can help you.

But if you try another recording then the automatic correlation should be disabled and the flow should be exactly the same. Comparing the two flows showed some differences.

 

Regards

Thomas

Please use plain text.
Frequent Advisor
Nan_Raso
Posts: 36
Registered: ‎04-15-2013
Message 5 of 5 (166 Views)

Re: LR 11.51 Siebel script is failing for 2nd iteration

Hello Nisanth, 

if the script works fine for the first iteration and fails for the second, then it sould be session timout problem or correlation is not happening because of previously captured values in iteration 1 is not any more valid.

 

So, Try using the login and logoff part both in action part .

I believe it should work, if 1st iteration works correctly.

Thanks,
Nan Raso
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation