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.
For example, to send traffic to a virtual asset on a remote server, you might use:
- Proxy listen path: /proxyPath
- Service host: server.parasoft.com
- Service port: 9080
- Service forward path: /assetPath
To send traffic to a virtual asset on a local server using an HTTP Listener, you might use:
- Reverse Proxy: 7070
- Service host: [Virtualize]
To send traffic to a virtual asset on a local server without an HTTP Listener, you might use:
- Proxy listen path: /proxyPath
- Service host: [Virtualize]
- Service forward path: /assetPath
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 because the proxy doesn't allow forwarding to itself.
If you already have your application pointing directly to a virtual asset deployed at /existing, set the Service forward path to /existing.
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:
- Edit the virtual asset to prefix its path with
/pva/path - Deploy the proxy to
/pathwith 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.
