This topic explains how to configure your application under test (AUT) to interact with Virtualize’s message proxies.

In this section:

Modifying the Application Endpoint

To direct your AUT to a proxy, point it to the endpoint  (e.g., an HTTP path, MQ destination/client queue, or JMS destination/client topic or queue) where the proxy is listening for incoming messages.

For HTTP, the endpoint to use is shown in the HTTP connection configuration panel’s Proxy URL field.

For example, assume that:

In this case, you would set the AUT to the URL

Note that you can use HTTPS if SSL is used. Also, if additional ports are configured on the Virtualize Server side, the port could be different.

Modifying the Proxy Settings

If you can’t (or don’t want to) modify the application endpoint, you can send traffic to a message proxy by modifying the AUT’s proxy settings.

To do this, deploy the Virtualize message proxy at the same path as the actual backend. Then, once the proxy or proxies are set up, direct your AUT’s proxy to the Virtualize Server host and port.

For example, assume that you have one or more backends which sit at endpoints of the format http(s):/ /<host>:<port>/<path>

For each backend, create a proxy that is configured as follows:

The key is to have the Virtualize message proxy deployed at the same path as the actual backend.

Once the proxy or proxies are set up, configure your AUT’s proxy as follows:

For an HTTP Proxy:

For an HTTPS Proxy: