This topic explains how to direct message proxies to your virtual assets. A proxy can use a virtual asset on a SOAtest/Virtualize Server as its target service by directing your proxy to send traffic to the SOAtest/Virtualize server as if it were any other service.

Using HTTP listeners is the recommended connection configuration for recording HTTP traffic, as it simplifies updating the client application to point to the Virtualize server’s host and HTTP listener port without requiring any changes to the paths. This applies whether forwarding traffic to a live service or a virtual asset.

For example, to send traffic to a virtual asset on a remote server using an HTTP listener, you could use:

To send traffic to a virtual asset on a local server using an HTTP listener, you might use:

  • Reverse Proxy: 7070 listener
  • Proxy listen path: [All]
  • Primary (Virtualize):  /assetPath

To send traffic to a virtual asset on a remote server using an HTTP listener and fail over to a virtual asset on the local server, you could use:

When you have set both a primary and secondary connection, you can set one as the active forwarding connection and use the other as a fallback connection in case the active connection fails. You can also switch which is primary and which is secondary easily from the Server view. See HTTP Configuration for more information.

To send traffic to a virtual asset on a local server without an HTTP listener, you might use:


The HTTP Reverse proxy makes no distinction between a virtual asset and an actual service. Both are configured the same way. However, if the Default HTTP Reverse proxy (without an HTTP Listener) is sending to Virtualize or localhost, you must specify a service forward path (for example, /assetPath) because the proxy doesn't allow forwarding to itself.

If you already have your application pointing directly to a virtual asset deployed at /assetPath, set the service forward path to /assetPath.

If you already have your application pointing directly to a virtual asset and you can’t easily change the path where the AUT sends messages:

  1. Edit the virtual asset to prefix its path with /pva/path
  2. Deploy the proxy to /path with a forward path set to /pva/path

This configuration would allow you to add a proxy between your application and the virtual asset without making any changes to the AUT.

For more information about setting up HTTP proxies, see HTTP Reverse Proxy Configuration.

  • No labels

Need assistance? Visit our support page