This topic explains the general procedure for creating message proxies.

In this section:

Adding Proxies

1. Open the 

   Virtualize Server view

   and right-click the server where you want the proxy deployed (Local machine or a remote server).

2. Choose Add Message Proxy.
    

A new Proxy node will be added under the Message Proxies folder (which will be created if not already present). The added proxy will initially be set to a disabled state. The proxy will need to be configured before it can be used.

Configuring Proxies

Double-click the added node to open its configuration panel.

1. In the General tab, rename the proxy and enter a description (optional).
2. Click the Http Listeners tab so that you can configure the ports on which your HTTP(S) listeners should listen. HTTP listeners simplify the connection configuration for recording HTTP traffic: 
   1. Click Add Listener and specify a name for the listener.
   2. Click Add Port and enter a port number. You can enable the message proxy to automatically assign a port by specifying 0 as the port number. When the proxy is enabled, the assigned port number will appear in the console. The port is randomly assigned every time the message proxy is changed/enabled. You can also send a GET request to the messageProxies API endpoint to return the automatically-assigned port number. See Testing through the REST API for additional information. 
   3. If the client sends traffic over SSL, enable the Secure option and enable your verification options. See SSL Settings for Listener Ports for details.
   4. Click OK to exit the port editor.
   5. Click Add to add additional ports to the listener or OK again to finish adding the listener.
3. Open the Connections tab to specify the endpoints where the proxy should listen for messages and where the received messages should be directed. For each endpoint you want to use the proxy, do the following:
   1. Click Add.
   2. Select the appropriate transport type.
   3. Complete the proxy settings as follows:
      • HTTP/HTTPS: See HTTP Configuration.
      • JMS: See JMS Configuration.
      • MQ: See MQ Configuration.
      • Internal: See Internal Transport Configuration. Internal proxies can direct traffic to virtual assets or other internal-transport proxies. This can reduce the number of queues when deploying complex virtual assets as well as increase the performance of virtual assets when routing internally.
   4. In the Traffic file field, specify where you want to save the traffic data that will be captured when the proxy is set to record mode. You can later use this traffic file to generate virtual assets that represent the live traffic captured in record mode. See Transferring Files Between the Remote Server and the Local Machine for an easy way to access the recorded traffic file.
      • By default, traffic will be recorded in a file named %n_%d_%t.txt(<proxy_name>_<current_date>_<current_time>.txt). It will be stored within the recorded_traffic folder (this will be created if it does not exist). You can modify the file name, but not the folder. The folder is always located within the VirtualAssets project.
      • When specifying the file name, you can use variables such as %d (current date) %t (current time), %n (proxy name), and %u (unique time-based id). Wildcards can be used together and mixed in with the name. For example, you could use %nProxyTraffic%d or %u_%d%nTraffic
      • Do not configure multiple proxy connections to write to the same traffic file at the same time. This could corrupt the traffic file.
   5. In the Recording Session area, specify how you want traffic data recorded in traffic files:
      • Append new session data adds new traffic data to an existing traffic file (the one specified in the Traffic file field). If the specified file does not already exist, a new file will be created. See More on Recording Session Options below for additional details.
      • Overwrite session data overwrites the traffic data in an existing traffic file (the one specified in the Traffic file field). If the specified file does not already exist, a new file will be created. See More on Recording Session Options below for additional details.
      • New session file for each message pair (HTTP and internal only) creates a separate traffic file for each request/response pair. See More on Recording Session Options below for additional details.
4. Click OK.

You can now enable the proxy as described in Enabling and Disabling Proxies then start recording as described in Recording Traffic from Message Proxies.

More on Recording Session Options

The following table explains how traffic data is recorded with different combinations of traffic file name values and recording session options:

If a proxy uses the internal protocol and receives MQ traffic while recording, the New session file for each message pair option is not supported. If this option is selected, the default Overwrite session data behavior will be used.

Moving Proxies Across Servers

You can drag a proxy from one server to another to move it. Alternatively, you can copy from one server and paste it to another server.

Proxies can connect to an MQ manager using a global configuration or a local configuration. Global configurations are defined per Virtualizer Server and can be used by  proxies or virtual assets deployed to the server (see Connections Tab). Local configurations are defined for individual proxies or assets.

You can not deploy a proxy or asset connected to a global MQ manager if the MQ manager connection configuration does not exist on the destination Virtualize Server. If you need to move or copy a proxy/asset to another Virtualize Server, you can manually define the MQ manager connection or use the copy function to add the connection settings to the destination server (see Copying an MQ Manager Connection).  

Preventing Infinite Loops

If your proxies and/or Message Forward tools inadvertently set up a forwarding cycle like A> B> C> A, this could result in an infinite loop. To prevent such loops,Virtualize is  configured to stop forwarding after 10 hops. You can change this by setting the system property parasoft.proxy.loop.max.limit (e.g., parasoft.proxy.loop.max.limit=5).

The built-in loop detection only applies to internally-routed forwarding (e.g., routing to localhost, not routing to a host name).