Deploy Virtual Services
You can deploy virtual services from ldt Portal.
You can deploy virtual services from
The following video shows an example of deploying and monitoring virtual services.
Ensure the virtual service port number is not in use. A virtual service that was created by recording or with
Application Insightwill have the same port number where it was recorded.
Follow these steps:
- Go to the home page ofDevTestPortal.
- SelectManage,Virtual Servicesin the left navigation menu.TheManage Virtual Serviceswindow opens.
- Locate the virtual service in the table.
- Click theOptionsbutton in theActionscolumn and selectDeploy.TheDeploy Virtual Servicedialog opens.
- Select theVSEServer where you want to deploy.
- Modify the fields as necessary:
- Group TagSpecifies 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 capacitySpecifies a number that indicates the load capacity.Capacityis how many virtual users (instances) can simultaneously execute with the virtual service. Capacity here indicates how many threads there are to service requests for this service model.TheConcurrent capacityfield appears only in Service Virtualization for Performance mode.VSEallocates various 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 virtual service has been highly customized.For extensions and any virtual service that does not use an out of the box protocol, setting a long Think Time may consume a thread during 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) = 20In 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 ScaleSpecifies the think time percentage for the recorded think time.A step subtracts its own processing time from the think time to have consistent pacing of test executions.Default:100xamples:
- To double the think time, use 200.
- To halve the think time, use 50.
A virtual service can be in the following states:
- DeployedNo service with the name you entered is already deployed. The service is deployed.
- RedeployedA service with the name you entered is deployed with the same .vsm file as the service you entered. The service is redeployed.
- OverriddenA 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.