Need Windows Host Script help for load runner VB script for BPM (HP Remote monitoring tool).
I am trying to find a way set up monitoring for the new citrix environment. This is a real VM environment slice. So was able to install BMP on it.
We can run standard load runner scripts to handle the HTML apps.
Now for the real application like Word and Excel want to create VB scripts to open edit and saves and wrap a transaction time around it. We want to try to leverage the Windows scripting Host scripting technologies to open and close apps instead of QTP.
Scenario 1 Have a Logrunner VB script open a word document edit it and save and close. Will wrap a standard load runner transaction around it.
Scenario 2 Have a the Load runner VB script open a VBS script and wait for it to complete then end.
Need to create Load runner VB script that opens a VBS script run it wait for it to complete and finish. I understand running a VBS script from another calling VBS script will not wait for it to finish so will end to quickly to time with a standard LR transaction time. Will need get the calling VB Logrunner script to wait for the VBS script to finish it to time it. Note this is just for simple timing metrics so do not need to produce exact response times just something simple to get base line on.
I am hoping someone already has done this and has some sample code. I have been able to avoid the citrix world for a while unfortunately allot of companies going to the VM space.
Re: Need Windows Host Script help for load runner VB
1. GUI Virtual user
2. Consider moving all of your VB script code into a single VB script virtual user which would allow you to time discrete components of your script.
Keep in mind that once you are in a virtual machine your clock inegrity is poor as the virtual machine clock will skew in relation to the physical system clock. It will have to catch up, resync to the physical clock periodically. History with these environmentss shows that the odds are high that this resync will take place while timing records are open, resulting in a timwed event which is recorded as longer than the actual amount of time needed to complete the event.
Just some things to keep in mind if you are going to be running inside of a virtual machine.