...
| Note | ||
|---|---|---|
| ||
HTTP traffic files recorded in Virtualize or SOAtest 9.10.x and later cannot be used with 9.9.x verions versions and earlier. |
In this section:
...
| Listener | You can choose an HTTP listener that you defined when creating the proxy (see Creating Proxies) from the drop-down menu or use the default listener. You can add HTTP listeners in these sectionsections:
|
|---|---|
| Proxy listen path | Enter the path where the proxy should listen for incoming connections. No two message proxies can have HTTP connections with the same proxy path or with a path that matches an existing virtual asset’s HTTP path. See Service Forward Path and Proxy Listen Path for more details. |
| Proxy URL | Displays the URL that should be given to the AUT.See Directing AUTs to Proxies for additional information. |
...
| Key store file | Specify the path to the key store file. You can enter the path manually or browse the file system or workspace. |
|---|---|
| Key store password | Specify the password to access the keystore. |
| Key store type | Choose a keystore type from the drop-down menu and click Load. |
| Certificate | From the Certificate drop-down menu, choose the certificate alias to present to the server. The menu will be empty if there are configuration errors, such as an incorrect password or keystore type. |
...
| Service URL | Contains the full URL for the target application (comprising the service host, service port, and forward path). You can enter a complete URL here and/or edit specific components in the following fields. Updates made in one area will be propagated to the other (e.g., if you modify the port in the URL, the value in the Service port field will be updated automatically). |
|---|---|
| Service host | Enter the host name hostname of the machine where the service resides. This is the machine to which the proxy will send messages. If you want the proxy to forward foward to a virtual asset on the local server without consuming an HTTP connection, enter |
| Service port | Enter the port where the service is listening. This is the port to which the proxy will send messages. |
| Service forward path | (Optional) Enter the path to which the proxy should forward the messages that it receives. If blank, this defaults to the value in the Proxy listen path field. If the HTTP proxy is sending to messages localhost, you must enter a Service forward path because the proxy doesn't allow forwarding to itself. If the Service forward path sends a redirect, the proxy will follow the redirect and then respond back. It will not pass the redirect back to the client. See Service Forward Path and Proxy Listen Path for more details. |
...
- Record on both connections: Records traffic for both the primary and secondary connections. Error messages from the primary will not be recorded; instead, the messages will be sent to the secondary and the responses will be recorded. Errors reported by the secondary will be recorded.
- Record on primary connection only: Records traffic for the primary connection. Does not record errors.
- Record on secondary connection only: Records traffic for the secondary connection, including errors.
...
- Set the service host and port to that of the Virtualize Server where the virtual asset is deployed. If you want the proxy to forward foward to a virtual asset on the local Virtualize server without consuming an HTTP connection, enter
localhostor enterlocalhostor127.0.0.1rather rather than the actual host name. - Set the proxy connection’s Service forward path to the virtual asset’s path (found in the virtual asset’s Transports> HTTP tab, under HTTP endpoint).
...
You can change the default port number (9080), enable SSL, and configure other server settings. See Configuring Virtualize Server Configuration for details.
| Anchor | ||||
|---|---|---|---|---|
|
...