This topic explains the general procedure for creating message proxies.
In this section:
To create a message proxy:
- In the Virtualize Server tree, right-click the server where you want the proxy deployed (Local machine or a remote server), then 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.
- Double-click the added node to open its configuration panel.
- In the General tab, rename the proxy and enter a description (optional).
- 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:
- Click Add Listener and specify a name for the listener.
- Click Add Port and enter a port number.
- If the client sends traffic over SSL, enable the Secure option and enable your verification options. See SSL Settings for Listener Ports for details.
- Click OK to exit the port editor.
- Click Add to add additional ports to the listener or OK again to finish adding the listener.
- 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:
- Click Add.
- Select the appropriate transport type.
- 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.
- 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
<proxy_name>_<current_date>_<current_time>.txt). It will be stored within the
recorded_trafficfolder (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
- Do not configure multiple proxy connections to write to the same traffic file at the same time. This could corrupt the traffic file.
- By default, traffic will be recorded in a file named
- 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.
- Click OK.
Configuring an HTTP Message Proxy Video Tutorial
This video describes how to set up a message proxy that can capture live traffic.
More on Recording Session Options
The following table explains how Virtualize records traffic data with different combinations of traffic file name values and recording session options:
|Traffic file name||Recording session option||Result|
|Default / parameterized||Append new session data||Creates one new file that includes all request/response pairs in the recording session.|
|Static||Append new session data||Adds new traffic data to the specified traffic file (if it exists). Otherwise, creates one new file that includes all request/response pairs in the recording session.|
|Default / parameterized||Overwrite session data||Creates one new file that includes all request/response pairs in the recording session.|
|Static||Overwrite session data||Overwrites existing traffic data in the specified traffic file (if it exists). Otherwise, creates one new file that includes all request/response pairs in the recording session.|
|Default / parameterized||New session file for each message pair||Creates one new file for each request/response pair in the recording session. If multiple request/response pairs are detected, multiple files are created.|
|Static||New session file for each message pair|
If the specified file exists, overwrites existing traffic data every time an additional request/response pair is detected.
If the specified file does not exist, creates one new file for the first request/response pair, then overwrites existing traffic data every time an additional request/response pair is detected.
In both cases, the resulting file contains only the most recent request/response pair.
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, Virtualize will default to Overwrite session data behavior.
Moving Proxies Across Servers
To move a proxy from one Virtualize server to another, simply drag and drop (or copy/paste) it.
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
Note that this loop detection applies only to internally-routed forwarding (e.g., it applies to routing to localhost, not routing to a host name).