Difference between the recording via VSE Recorder launched from workstation and DevTest Portal

[Alex James]

Recording via the VSE Recorder launched from workstation will use the hostname of the machine where workstation is installed. If we are doing recording using the DevTest Portal, which hostname will the recorder will use if I have registry, portal, workstation, vse server - all in different machines.

 

We are able to record using the VSE Recorder launched from workstation without running the VSE server. Can we record using Portal without running the VSE Server

[Rick.Brown]

When recording through the Portal user interface, you are provided with a drop-down list box "Select VSE Server:" from which you select the VSE server on which to start the recorder. This is the name that the VSE used to register itself on the registry (so you can have multiple VSEs running on one host, so you can differentiate between VSEs for different projects, uses, locations, etc).

 

When you have selected the VSE server on which you want to record, the IP address of that VSE server is automatically filled under the "VS Recorder" graphic, so you know which IP address to redirect your application to.

 

So, it's all about the VSE server when you're recording through the Portal user interface. Your client to this is just a browser, so you don't start any local processes for recording, and you don't even need a local installation of Workstation running to enable your recording.

 

Record from Workstation: you need Workstation

Record from Portal: you need VSE

 

Rick

[Udhayakumar Sankaran]

Thank you Rick. :-)

[Alex James]

Thanks Rick for the quick reply.

 

In our case all the DevTest components (Registry, VSE, Workstation, DB etc)are in different machines and we have access only to the machine where workstation is installed. So once we did the recording using the portal from this machine, can we open the VSI/VSM file created from workstation and edit from there. Also can we deploy the virtual service to the VM and do Model healing from the same machine provided that the required ports are opened between the different machines.

[Rick.Brown]

Are the editing facilities provided by Portal insufficient for your requirements? What's your use case for needing local editing of the files?

     If so, you can download the recorded virtual service by going to "Manage; Virtual Services", clicking on the "Options" icon in the "Actions" column for your virtual service, and select "Download MAR".

     You will be able to extract this to your local machine (creating a new project, just for that virtual service), edit it and deploy to a VSE.

 

The other selection under the "Options" icon is "Deploy", which starts your virtual service on one of your VSEs.

 

When the virtual service is running, you can always select "Monitor; Virtual Service Environments" (introduced in DevTest v8.4 sandbox), or "Monitor; Virtual Services" (in older versions of DevTest) to view your VSE and change execution mode for any deployed virtual service.

[Alex James]

Thanks Rick. I thought about local editing because we will record only minimum scenarios and in order to support different request data we need to edit the VSI. Can we edit the VSI from DevTest Portal itself.

[Rick.Brown]

"Manage; Virtual Services" and select your virtual service. You can edit your VSI directly from the Portal user interface.

[Alex James]

Thanks Rick. See you soon with further queries :-))