Differences in Virtual Services created from the Portal vs Workstation regarding properties, custom DPHs, live routing

Products

• CA Application Test

Issue/Introduction

Virtual Services created from the Workstation can have these features:

1. A scriptable Data Protocol Handler (custom DPH) writes each individual request and response to a file on the server. Using a specific format and filenames.
2. A Virtual Service hits the live server in case a request from the VS itself is not matching.
3. A proxy is configured through a Companion -> Configure DevTest to Use a Web Proxy.
4.  A property is used for the keystore password in the SSL listen step such that only the administrator can see and update the password.

Are these options/features available in the Virtual Services created from the DevTest Portal.

Environment

All supported Service Virtualization releases.

Resolution

1. There is no equivalent to the scriptable protocols that you can use in a VS created in the Workstation. 
   So only the standard log files and the inspection view in the Portal are available.
2. The behaviour of the VS that needs to be configured is "Fall Through to live system if no virtualized response (Stand in)". 
   In Monitor -> VSE -> your VS -> Execution Mode this can be selected for a VS that was created in the Workstation. But unfortunately this is not available in a Portal created VS. The only options are Most Efficient, Tranaction Tracking, Dynamic
3. The companion functionality is not available in the Portal.
4. Properties can not be used in the Portal.