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 direct proxy traffic to a virtual asset that is deployed at http://virtualize.parasoft.com:9080/path on a remote server, you might use: 

  • Service host:virtualize.parasoft.com
  • Service port: 9080
  • Proxy listen path: /path
     


If you already have your application pointing directly to a virtual asset deployed at /existing, you would 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:

  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.

  • No labels