...
| Note | ||
|---|---|---|
| ||
HTTP traffic files recorded in inVirtualize 99.10.x and later cannot be used with 9.9.x verions and earlier. |
...
You will need the host, port, and path of the service you are targeting in order to are creating a virtual forto set up basic HTTP connection options. Use the settings you would normally use to directly message the service.
...
| 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 section:
|
|---|---|
| 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. |
...
| 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 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. |
...
The Service SSL section needs to be completed only if the service you are working with uses SSL.
If the service theservice being virtualized uses virtualizeduses SSL and/or other authentication (basic/digest, Kerberos, NTLM), additional configuration may be required.
...
The wildcard can only be used for one segment of the path. A path configured as ast /path/*/service will NOT match /path/1/2/service. If you want your path to match both /path/1/2/service and /path/3/4/service, use the pattern /path/*/*/service.
...
- 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
localhostor127.0.0.1rather 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).
...
- Copy the following jar files into tomcat's
libdirectory:jna.jar, platform.jar, wafflejna.jar. Add the following to
tomcat/conf/server.xml.Code Block <Context> <Valve className="waffle.apache.NegotiateAuthenticator" principalFormat="fqn" roleFormat="both"/> <Realm className="waffle.apache.WindowsRealm" /> </Context>
Info title Where is server.xml? If you installed SOAtest but not Virtualize: Launch SOAtest, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>[SOAtest install dir]/eclipse/plugins/com.parasoft.ptestxtest.libs.web_<VERSION>[version]/root/tomcat/conf/server.xml
If you installed Virtualize but not SOAtest: Launch Virtualize, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>[Virtualize install dir]/eclipse/plugins/com.parasoft.ptestxtest.libs.web_<VERSION>[version]/root/tomcat/conf/server.xml
If you installed Virtualize and SOAtest together: Launch Virtualize, ensure that at least one responder has been created, then modify the server.xml file at <INSTALL>[SOAtest install dir]/eclipse/plugins/com.parasoft.ptestxtest.libs.web_[SOAtest_<VERSION>ver]/root/tomcat/conf/server.xml
Add the following to
tomcat/conf/web.xml.Code Block <security-role> <role-name>Everyone</role-name> </security-role> <security-constraint> <display-name>Waffle Security Constraint</display-name> <web-resource-collection> <web-resource-name>Protected Area</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>Everyone</role-name> </auth-constraint> </security-constraint>- Restart the server.
...