Modes control how the Parasoft JDBC Driver responds to the JDBC calls it receives. For example, will it pass them to the actual JDBC driver and record the responses? Route them to a virtual asset? Pass them to the actual JDBC driver without any recording?
Modes can be changed at any time from the Virtualize Server UI or Environment Manager. You do NOT need to restart the AUT before or after changing modes.
Available modes are:
| Mode | Description |
|---|---|
| Passthrough | The Parasoft JDBC Driver will delegate JDBC calls to the original driver implementation class with no data capture or recording. This mode is designed 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. |
| Record | The Parasoft JDBC Driver will delegate JDBC calls to the original driver implementation class while capturing SQL queries and ResultSet data that is returned from the original driver. The cap-tured data is transmitted to the Virtualize Server connected to this Parasoft JDBC Driver. |
| Virtualize | JDBC calls received by the Parasoft JDBC Driver will be routed to the Parasoft Virtualize Server, and the ResultSet data received from the 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 - Overview for details). For details on how to control which virtual asset is called, see Specifying which Virtual Asset the Parasoft JDBC Driver Calls. |
| Hybrid | In this mode, the Parasoft JDBC Driver behavior will be the same as in Virtualize mode—except when no matching virtualization data is found. For those cases, it will delegate the JDBC calls to the original driver implementation class with no data capture or recording. For details on how to control which virtual asset is called, see Specifying which Virtual Asset the Parasoft JDBC Driver Calls. |
| Failover | In this mode, the Parasoft JDBC Driver will delegate JDBC calls to the original driver implementation class unless a failure (SQL exception) occurs. If a failure occurs, JDBC calls received by the Parasoft JDBC Driver will be rerouted to the Parasoft Virtualize Server, and the ResultSet data received from the Virtualize server will be returned to the application. For details on how to control which virtual asset is called, see Specifying which Virtual Asset the Parasoft JDBC Driver Calls. This mode requires Virtualize 9.9.4 or later. |
Switching Modes From the Virtualize UI
To switch modes from the Virtualize UI:
- Ensure that your application and its corresponding JDBC/Data Source configuration is set up to use the Parasoft JDBC Driver. See About the Parasoft JDBC Driver for links to the available configuration topics.
- Right-click the appropriate JDBC Controller and choose the desired mode.
Note that the icon will change to indicate the driver’s current state.
| Icon | Mode |
|---|---|
| Passthrough |
| Record |
| Virtualize, Hybrid, Failover |
Switching Modes From Environment Manager
See the Environment Manager User’s Guide.
