Versions Compared

Old Version 3

changes.mady.by.user user-50d80

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (lstevens)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2020.2

...

Note
titleVersion Compatibility

HTTP traffic files recorded inVirtualize in Virtualize or SOAtest9SOAtest 9.10.x and later cannot be used with 9.9.x verions versions and earlier. 

In this section: 

...

You will need the host, port, and path of the service you are testing or creating a virtual service forto are targeting in order to 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 sectionsections:

  1. Click New and specify a name for the listener.
  2. Click Add Port and and enter a port number. You can enable the message proxy to automatically assign a port by specifying 0 as specifying 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 API endpoint to return the automatically - assigned port number. See Testing Creating and Modifying Assets 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.
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 fileSpecify the path to the key store file. You can enter the path manually or browse the file system or workspace.
Key store passwordSpecify the password to access the keystore.
Key store type

Choose a keystore type from the drop-down menu and click Load.

CertificateFrom 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 URLContains 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 foward to a virtual asset on the local server without consuming an HTTP connection, enter localhost or 127.0.0.1 rather than the actual host name. 

Service portEnter 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.

...

The Service SSL section needs to be completed only if the service you are working with uses SSL.

If theservice the service being virtualized and/or the application under testuses test uses 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 ast as /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.

...

  1. Set the service host and port to that of the Virtualize Server where the virtual asset is deployed. If you want the proxy to foward to a virtual asset on the local Virtualize server without consuming an HTTP connection, enter localhost or enter localhost or 127.0.0.1 rather  rather than the actual host name. 
  2. 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
Using NTLM with WAFFLE
Using NTLM with WAFFLE
Using NTLM with WAFFLE

...

  1. Copy the following jar files into tomcat's lib directory: jna.jar, platform.jar, wafflejna.jar.

  2. 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
    titleWhere 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 [SOAtest install dir]/eclipse<INSTALL>/plugins/com.parasoft.xtestptest.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 [Virtualize install dir]/eclipse<INSTALL>/plugins/com.parasoft.xtestptest.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 [SOAtest install dir]/eclipse/<INSTALL>/plugins/com.parasoft.xtestptest.libs.web_[SOAtest_ver]<VERSION>/root/tomcat/conf/server.xml

  3. 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>
  4. Restart the server.

...