Versions Compared

Key

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

...

  1. Place the Parasoft JDBC Driver jar file on the application server (the following sections indicate exactly where it should be placed on each type of server). The driver (, ParasoftJDBCDriver.jar), ships with Parasoft Virtualize under [virtualize installation directory]under <INSTALL-DIR>/proxies.
  2. Configure the driver to register with the appropriate Virtualize Server. The method for configuring the Parasoft JDBC Driver varies depending on how your application is deployed. For details on how to perform the configurations appropriate for your specific environment, see:
  3. Start the application under test (AUT). When the driver is initialized, it will automatically connect to Virtualize and either create a new deployment configuration for that group ID or get settings from an existing deployment configuration with the same group ID. The Console view will report a message that the driver is registered:
  4. Verify that the JDBC Controller for this Parasoft JDBC Driver appears in the Virtualize Server view.

From that point forward, you will be able to control the JDBC driver mode and logging via the Virtualize Server view or Environment Manager. By default, the driver starts in passthrough mode with log level 1.

Anchor
Properties Required
Properties Required
Driver/System Properties Required for All Environments

...

  • virtualizeServerUrl: Specifies the hostname of Parasoft Virtualize Server. This should have the format http:///[Virtualize Server host name or IP address]<VIRTUALIZE SERVER HOST NAME/IP ADDRESS>:9080. Port number 9080 is the default. Use a port number other than 9080 only if Virtualize Server has been configured with a different port number.
  • virtualizeGroupId: The group name used to create the JDBC Controller in Virtualize. Multiple drivers may share the same group idID. All drivers that share a single group id ID will all be updated by any configuration changes made from the related controller. For example, if you have a cluster of nodes and want to be able to start or stop recording in unison, configure them share a single group idID. If you want to control them individually, assign them each a distinct group idID.
    • If you use an existing group idID, the current Parasoft JDBC Driver will be assigned to that group’s JDBC Controller.
    • If you use a new group idID, a new JDBC Controller will be created for that new group idID.
       

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.
     


These properties can be set as part of the driver URL. For example, the following sets the group ID and server URL:

...

Alternatively, you can usually specify these either through the Admin GUI or as command-line arguments to Java using the –D<prop_name>=<prop_value> –D<PROP NAME>=<PROP VALUE> syntax.

To see the exact system properties that your AUT needs to use, see Parasoft Environment Manager’s endpoint report. For example: 
 

...

By default, the Parasoft JDBC Driver calls the virtual asset deployed at /virtualDb (when in Virtualize or Hybrid mode—or mode or in Failover mode and an a failure occurs). To have it call a virtual asset that is deployed at a different endpoint, use the optional driver/system property:

...

This property should be set to the virtual asset deployment configuration path. For example, if your vir-tual virtual asset is deployed at /myVirtualDb, you would configure this in either of the following ways:

...

The default (poall) provider uses a simple HTTP connection to check whether any Parasoft JDBC Driver updates (e.g.for example, JDBC driver mode changes) have been set in the Virtualize Server view.

...