To configure a JDBC controller:
If you want to adjust the pre-populated controller settings (taken from the controller’s current state), modify them using the available controls.
|Passthrough||The Parasoft JDBC Proxy 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 Parasoft driver is not there. Note that the JDBC calls still go through the driver and are delegated to the original driver – the Parasoft driver is still there in the middle.|
|Record||The Parasoft JDBC Proxy 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 captured data is transmitted to the Virtualize Server connected to this Parasoft JDBC Proxy 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 Proxy Driver.|
Reroutes traffic upon virtual asset failure or database failure (depending on the failover behavior setting). With "Virtual to Live" failover behavior, traffic will be rerouted to the live database if a data source correlation (for matching virtual assets) is not found. With "Live to Virtual" failover behavior, traffic will be rerouted to a virtual asset if a database failure (SQL exception) occurs.
Virtualize desktop users: Note that Virtualize’s Hybrid mode is represented in this UI with Failover mode> Virtual to Live failover behavior.