Using CA Service Virtualization › Using the Workstation and Console with CA Service Virtualization › Virtualizing a Service › Deploy and Run a Virtual Service

Deploy and Run a Virtual Service

Follow these steps:

1. On the VSE Console, click Deploy a new virtual service to the environment.

   The Deploy Virtual Service window opens.

2. Enter the name of a model archive (MAR) to upload, then click Deploy.
   • The MAR must contain a virtual service. When you click Deploy, the service loads into the VSE Console and the service is available to run.
   • Alternatively, go to the project panel in DevTest Workstation and right-click a virtual service model (VSM) to open the Deploy Virtual Service window.

   The Deploy Virtual Service window opens.

3. Modify the fields as necessary:

   Name

   Displays the name of the virtual service that the VSM you selected references.

   VS model

   Displays the virtual service model that you selected.

   Configuration

   (Optional) Lets you select an alternate configuration file.

   Group Tag

   Specifies the name of the virtual service group for this virtual service. If deployed virtual services have group tags, they are available in the drop-down list. A group tag must start with an alphanumeric character and can contain alphanumeric characters and the following special characters:

   • Period (.)
   • Dash (-)
   • Underscore (_)
   • Dollar sign ($)

   Concurrent capacity

   Specifies a number that indicates the load capacity. Capacity is how many virtual users (instances) can simultaneously execute with the VSM. Capacity here indicates how many threads there are to service requests for this service model.

   VSE allocates a number of threads equivalent to the total concurrent capacity. Each thread consumes some system resources, even when dormant. Therefore, for optimal overall system performance, set this setting as low as possible. Determine the correct settings empirically by adjusting them until you achieve the desired performance, or until increasing it further yields no performance improvement.

   Out of the box protocols use a framework-level task execution service to minimize thread usage. For these protocols, a concurrent capacity of more than 2-3 per core is rarely useful, unless the VSM has been highly customized.

   For extensions and any VSM that does not use an out of the box protocol, setting a long Think Time may consume a thread for the duration of the think time. In these cases, you may need to increase the concurrent capacity.

   The following formula gives an approximate initial setting in these cases:

   Concurrent Capacity = (Desired transactions per second / 1000) * Average Think Time in ms * (Think Scale / 100)
   

   Example:

   Assume that you are using a custom protocol that does not use the framework task execution service to handle think times. You want an overall throughput of 100 transactions per second. The average think time across the service image is 200 ms, and the virtual service is deployed with a 100 percent think scale.

   (100 Transactions per second / 1000) * 200ms * (100 / 100) = 20
   

   In this case, each thread blocks for an average of approximately 200 ms before responding, and during that time is unable to handle new requests. We therefore need a capacity of 20 to accommodate 100 transactions per second. A thread would become available, on average, every 10 ms, which would be sufficient to achieve 100 transactions per second.

   Default: 1

   Think time scale

   Specifies the think time percentage for the recorded think time.

   Note: A step subtracts its own processing time from the think time to have consistent pacing of test executions.

   Default: 100

   Examples:

   • To double the think time, use 200.
   • To halve the think time, use 50.

   Start the service on deployment

   Specifies whether to deploy and start the service immediately.

   Values:

   • Selected: The service deploys and starts immediately.
   • Cleared: The service deploys, then you start it manually from the VSE Console.

   If service ends, automatically restart it

   Specifies whether to keep the service running even after an emulation session reaches its end point.

   Values:

   • Selected: Continues running the service after the emulation service ends.
   • Cleared: Stops the service when the emulation service ends.

   Default: Selected

4. Click Deploy.

   The VSE Console displays the virtual service status as loaded.

Note: A virtual service can be in the following states:

Deployed

No service with the name you entered is already deployed. The service is deployed.

Redeployed

A service with the name you entered is deployed with the same .vsm file as the service you entered. The service is redeployed.

Overridden

A service with the name you entered is deployed with a .vsm file that is different from the one associated with the service you entered. The application prompts you to override the deployed service.