Virtual Services (beta)

Add Virtual Service

To add a virtual service, click the new virtual service button: Which will show a create dialog:

Click the submit button to create the virtual service. If a valid free HTTP/HTTPS port is specified, then the virtual service will be accessible on the ports specified.

Edit Virtual Service

To edit a virtual service, click the edit virtual service button for an existing virtual service in the list:

Click the submit button to edit the virtual service. If a valid free HTTP/HTTPS port is specified, then the virtual service will be accessible on those ports. The service will no longer be accessible on the old ports.

Delete Virtual Service

To delete a virtual service, click the delete virtual service button for an existing virtual service in the list:

Click the delete button to delete the virtual service. The service will no longer be accessible on the old port. The deleted virtual service mappings will be backed up in the deleted-scenarios directory.

Select Virtual Service

To select a virtual service, click on the name of the virtual service in the dropdown at the top of the page. This can be accessed from any page.

Once selected, the following will happen:

• The default HTTP virtual service port of 8080 will serve the selected virtual service over HTTP
• The default HTTPS virtual service port of 8081 will serve the selected virtual service over HTTPS
• The custom HTTP/HTTPS ports assigned to each virtual service remain active regardless of the currently selected virtual service
• The Add/Edit/Record/Replay pages for all protocols now impact the currently selected virtual service

Advanced Configuration

Each virtual service has a service.properties file that can be used to specify advanced configuration such as custom HTTPS certificates:

Property name	Description	Example usage
http.port	The HTTP port for the virtual service	http.port=9017
https.port	The HTTPS port for the virtual service	https.port=9018
https.key.store.path	Path to the HTTPS key store to use	https.key.store.path=certs/server.jks
https.key.store.password	The password for the HTTPS key store	https.key.store.password=password
https.key.manager.password	The password for the HTTPS key store manager	https.key.manager.password=password
https.key.store.type	The type of key store used, for example JKS or PKCS12	https.key.store.type=JKS
https.need.client.auth	Whether client authentication is required. Set to true or false.	https.need.client.auth=true
https.trust.store.path	Path to the HTTPS trust store to use	https.trust.store.path=certs/servertrust.jks
https.trust.store.password	The password for the HTTPS trust store	https.trust.store.password=password
https.trust.store.type	The type of trust store used, for example JKS or PKCS12	https.trust.store.type=JKS