...
Note that each AUT can use either:
- A locally - controlled Parasoft JDBC Driver
- A remotely - controlled Parasoft JDBC Driver
- System properties
...
If you are using one of the specialized driver classes (any of the implementation classes above except the “Generic/Other Driver”), then the following properties can be applied through the application server framework. The application server sets these custom properties to the Parasoft JDBC Driver (or any other driver) by attempting to invoke a set method with the same name to the provided driver class. For example, if a property named logLevel is provided, then the application server will use reflection to invoke a method named setLogLevel with a single string argument.
...
virtualize: Sets the Parasoft JDBC Driver in virtualization mode. JDBC calls received by the Parasoft JDBC Driver will be routed to Parasoft Virtualize Server, and the ResultSet data received from Virtualize server will be returned to the application. This mode assumes that recording has already been performed and that Virtualize Server has been configured with a virtual asset so it can respond to the Parasoft JDBC Driver (see Deploying Virtual Assets Virtualize for details).
passthrough: The Parasoft JDBC Driver will delegate JDBC calls to the original driver implementation class with no data capture or recording. The intention of this mode is to effectively turn the Parasoft JDBC Driver off and have the system at a state similar to the original configuration as if the driver is not there. Note that the JDBC calls still go through the driver and are delegated to the original driver – the Parasoft JDBC Driver is still there in the middle.
...
This property refers to the location of the local log file that is produced for debugging purposes (e.g. for example, events and exceptions coming from the actual JDBC driver). This is NOT the location of the file that logs recorded data. That file is always stored in the Virtual Assets project.
...
server: Submits the logging data to a remote Parasoft Virtualize Server so it can be viewed and analyzed there. This is convenient so that configuration debugging can be performed without having to access access local log files on the application server where the Parasoft JDBC Driver is is installed. The logging events are buffered, then transmitted in bursts every 5 seconds. See Configuring Logging for JDBC Operations for details.
stdout: Routes Parasoft JDBC Driver logging logging events to the standard console output.
...
1: Log errors only. Stack traces are included in such errors.
2: Log errors and informational events to help debug and analyze issues.
3: Include stack traces with each logging entry.
4: Include traffic communicated between the Parasoft JDBC Driver and the Virtualize Server, but with no stack traces.
5: Includes 3 and 4 data.
Use logging levels 3 and 5 with caution under limited circumstances and scenario runs only. Including stack traces for each informational log entry tends to grow the log file content very rapidly.
...
If you are using one of the “Generic/Other Drivers” then the Parasoft JDBC Driver Implementation Implementation uses the following system properties:
...