Using CA Service Virtualization › Installation and Configuration › Install the Database Simulator

Install the Database Simulator

To record JDBC traffic, install the DevTest simulation JDBC driver on the database client. The database client uses the DevTest driver instead of the actual driver.

Follow these steps:

1. Copy the JAR file lisajdbcsim.jar in the LISA_HOME\lib directory to the classpath of your database.

   This JAR file contains the DevTest simulation JDBC driver. To help with the use of demo server as the database client, the driver is already copied into the demo server in the DEMO_HOME\jboss\server\default\lib directory.

2. Set the driver class to com.itko.lisa.vse.jdbc.driver.Driver. Set the driver class, depending on the style of JDBC that the database client uses:

   DriverManager Style

   In an application server, it is not likely that the database client uses the Java DriverManager to acquire connections. If the application server does, add the following command to the startup command for the database client:

   -Djdbc.drivers=com.itko.lisa.vse.jdbc.driver.Driver
   

   If this property is already used, add the DevTest driver to the front. Separate the DevTest driver from the rest of the driver class names with a colon ( : ).

   DataSource Style

   If the database client uses the DataSource style for acquiring a connection (as the Demo Server does), then update its configuration. Where the configuration specifies a data source definition, specify com.itko.lisa.vse.jdbc.driver.Driver as the JDBC driver to use, and a connection URL.

3. To achieve a pass through, modify the connection URL so that the DevTest Simulation JDBC driver can identify the real driver information. Format the connection URL as follows:

   name=value[;name=value...]
   

   name

   jdbc:lisasim:driver: The value must be the fully qualified class name of the real JDBC driver to use.

   url: The value must be set to the connection URL that the real driver expects. (It must be defined as the last property so that it can contain semi-colons.)

   Note: VSE does not support the Oracle thin driver as a pass through driver. The Oracle thin driver does not provide the full JDBC implementation. If you use Oracle as a database, use other JDBC drivers for virtualization.

For an example of setting the connection URL, see DEMO_HOME\jboss\server\default\deploy\itko-example-ds.xml.

The following graphic shows an example of virtualizing the database in a WebMethods environment.

To use both the simulation and CA Continuous Application Insight drivers, make the simulation driver the "outside" driver. Specify the CAI class and URL. See the itko-example-ds.xml file in the DEMO_HOME\jboss\server\default\deploy folder for an example that defines a DevTest data source to JBoss for DevTest demo server.

Other Startup Properties

Regardless of the connection style of the database client, you can add the following properties to the startup command for the database client to affect the simulation driver.

lisa.jdbc.sim.require.remote

Specifies whether the driver requires an active connection with a DevTest Workstation or VSE Server to run. This method is the best way to have a database client synchronize with VSE to record or play back any startup database activity that the server performs.

Values:

• true: The driver blocks until there is an active connection with a DevTest Workstation or VSE Server.
• false: The driver does not require an active connection.

Default: false

lisa.jdbc.sim.port

Defines the IP port on which the driver listens for connections from a recorder or a running virtual service model.

Default: 2999