The following is a brief overview of how to configure your AUT to work with any virtual assets, message proxies, and JDBC controllers you have provisioned. For complete details, see the Virtualize User’s Guide.

Message Proxies

To direct your AUT to a proxy, point it to the endpoint (e.g., an HTTP path, MQ destination/client queue, or JMS destination/client topic or queue) where the proxy is listening for incoming messages. This is shown in Endpoint Report page.

To access this report, click the Endpoints link in a page header.

Virtual Assets

If you are provisioning a virtual asset that is not controlled via a message proxy, you can point your application to the virtual asset’s endpoint. For HTTP/S endpoints, select the virtual asset in tree, then use the endpoint shown on the right.

For MQ and JMS endpoints, endpoint information is shown on the Deployed Virtual Asset’s detail page.

JDBC Controllers

The following Java system properties are required startup parameters for the AUT:

• parasoft.virtualize.group.id: The equivalent of the virtualizeGroupId driver property; the default is hostname.
• parasoft.virtualize.server.url: The equivalent of the virtualizeServerUrl driver property.

CTP's Endpoint Report provides the system properties that your AUT needs to use. To access this report, click the Endpoints link in a page header.

In some cases, (e.g., for standalone Java applications that are deployed in application servers that do not manage data source configurations), you also need to specify parasoft.virtualize.driver.register.jdbcproxydriver.in.drivermanager, which defaults to false. This flag determines whether Parasoft's JDBC driver should register itself in the runtime's java.sql.DriverManager using the DriverManager.registerDriver() method. This option depends on whether:

• The application uses a java.sql.DriverManager to create an instance of java.sql.Driver (in which case "true" is the common setting). This applies to the ParaBank sample application, where this property should be set to true.
• The driver is being used in a Web application environment (such as WebSphere or WebLogic). In this case, this property should be left false.

You can usually specify these either through the Admin GUI or as command-line arguments to Java using the –D<prop_name>=<prop_value> syntax.

For additional help, see the Virtualize User’s Guide (Using the Parasoft JDBC Driver).

The following is a brief overview of how to configure your AUT to work with any virtual assets, message proxies, and JDBC controllers you have provisioned. For complete details, see the Virtualize User’s Guide.

Message Proxies

To direct your AUT to a proxy, point it to the endpoint (e.g., an HTTP path, MQ destination/client queue, or JMS destination/client topic or queue) where the proxy is listening for incoming messages. This is shown in Endpoint Report page.

To access this report, click the Endpoints link in a page header.

Virtual Assets

You can directly access a virtual asset (e.g., if your virtual asset is not controlled by a proxy) by pointing your application to the virtual asset’s endpoint. For HTTP/S endpoints, select the virtual asset in the tree, then use the endpoint shown on the right.

For MQ and JMS endpoints, endpoint information is shown on the Deployed Virtual Asset’s detail page.

JDBC Controllers

The following Java system properties are required startup parameters for the AUT:
parasoft.virtualize.group.id: The equivalent of the virtualizeGroupId driver property; the default is hostname.
parasoft.virtualize.server.url: The equivalent of the virtualizeServerUrl driver property.

In some cases, (e.g., for standalone Java applications that are deployed in application servers that do not manage data source configurations), you also need to specify parasoft.virtualize.driver.register.jdbcproxydriver.in.drivermanager, which defaults to false. This flag determines whether Parasoft's JDBCProxyDriver should register itself in the runtime's java.sql.DriverManager using the DriverManager.registerDriver() method. This option depends on whether:

• The application uses a java.sql.DriverManager to create an instance of java.sql.Driver (in which case "true" is the common setting). This applies to the ParaBank sample application, where this property should be set to true.
• The driver is being used in a Web application environment (such as WebSphere or WebLogic). In this case, this property should be left false.

You can usually specify these either through the Admin GUI or as command-line arguments to Java using the –D<prop_name>=<prop_value> syntax.

CTP's Endpoint Report provides the system properties that your AUT needs to use. To access this report, click the Endpoints link in a page header.

For additional help, see the Virtualize User’s Guide (Using the Parasoft JDBC Driver).