Virtual Services (beta)

• HTTP
• HTTPS
• Native IBM® MQ

• gRPC
• JMS
• Files

• Each Traffic Parrot server can host one or more virtual services
• Each virtual service has a separate configuration directory on the filesystem, including:
  • Separate request to response mappings
  • Separate virtual service properties file
• HTTP virtual services can be run on multiple ports
• MQ virtual services can connect to multiple queue managers

The virtual services can be managed using the Virtual Services UI page:

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

HTTP

To configure a HTTP virtual service you should:

1. (optional) Follow the instructions to add a new virtual service and specify a HTTP port
2. Follow the instructions to select a virtual service
3. Use the HTTP UI to Add/Edit mappings

HTTPS

To configure a HTTPS virtual service you should:

1. Follow the instructions to configure a HTTP virtual service and specify a HTTPS port
2. (optional) Configure HTTPS configuration in the scenarios/ServiceName/service.properties file:
   • https.key.store.path=certs/server.jks
   • https.key.store.password=password
   • https.key.manager.password=password
   • https.key.store.type=JKS
   • https.need.client.auth=true
   • https.trust.store.path=certs/servertrust.jks
   • https.trust.store.password=password
   • https.trust.store.type=JKS

Native IBM® MQ

To configure a Native IBM® MQ virtual service you should:

1. Configure the required IBM® MQ JARs (only needs to be done once per Traffic Parrot instance)
2. (optional) Follow the instructions to add a new virtual service
3. Follow the instructions to select a virtual service
4. Use the Native IBM® MQ UI to Add/Edit mappings
5. Configure the scenarios/ServiceName/ibm-mq-connections.json file
6. Use the Native IBM® MQ UI to Add/Edit mappings and turn on replay mode
7. (optional) Configure Native IBM® MQ startup configuration in the scenarios/ServiceName/service.properties file:
   • ibm.mq.queue.replay.on.startup=true
   • ibm.mq.queue.replay.request.queue.manager=REQ.QM
   • ibm.mq.queue.replay.response.queue.manager=RSP.QM

• The UI can only be used to make changes to one virtual service at a time
• The UI does not support editing the following configuration, which must be configured directly using the file system and a text editor:
  • scenarios/ServiceName/service.properties
  • scenarios/ServiceName/data
  • scenarios/ServiceName/ibm-mq-connections.json
  • scenarios/ServiceName/database-connections.json
• Live changes to virtual services names and ports are only picked up if the changes are made via the UI (changes directly to the filesystem of a running instance are not picked up dynamically)
• Only one JMS/Files/gRPC virtual service can be set to record or replay mode at a time
• Switching virtual service while replay mode is active for JMS/Files is not supported and replay must be stopped before switching