| || |
Does anyone have any experience testing
siebel 2000 with Loadrunner
Siebel 2000 has a thick and thin client
The thick is a siebel/odbc/db vuser no sweat
But the thin client uses a quasi-active x thing in the browser that really sits ontop of the tcpip layer and uses siebels own protocal.
I have tried to record this as a web vuser with no success with either of the two recording options with different settings for recording of non html and all resources. With no success
I tried recording this as a socket script by using ie as the exe and going to the site no luck.
I then tried Dcom/com since sometimes you can do it this way for active x with ie as my exe no luck.
Next I tried the siebel protocals no luck ( that would be to easy right .
Next I tried ODBC no luck.
Anyone have any experience or have any recomendations?
I have some SR's in to mercs customer support and also have some calls to mercury technical reps.
Any tips would be nice
Re: Siebel 2000
I got the answer from a mercury engineer.
Nope cannot due it
Due to Siebel thin cleint using its one API and its own protocal on top of tcp/ip
Siebel is scheduled to release soon
Siebel 2001 which is straight web/http
which would then be ok for Loadrunner to do