JDBC Driver for Recording Database Behavior
The Parasoft JDBC Driver (for recording live database behavior so it can be simulated) was updated in 9.10. JDBC Drivers released prior to Virtualize 9.10 will not able to communicate with the 9.10 Virtualize Server. If you were using an older JDBC driver, be sure to replace it with the new driver from the 9.10 installation. The new driver will be able to communicate with older versions of Virtualize.
Traffic File Format Change
Virtualize 9.10 introduces a new traffic format to accommodate enhancements in the traffic processing engine. Traffic files created in Virtualize 9.10 cannot be used in earlier versions.
Service Enabled License
A Service Enabled license is now required for:
- Connecting the Virtualize server to CTP
- Managing Virtualize server from external Virtualize desktops
- Accessing the REST API of the Virtualize server
- Starting the Virtualize server in headless mode
Built on Eclipse 4.6 (Neon)
Parasoft Virtualize and Parasoft SOAtest desktop (standalone version) are now built on Eclipse 4.6, which ships with Java 8.
JavaScript Engine Changes
SOAtest/Virtualize versions prior to 9.10 shipped with Java 7, which included the Mozilla Rhino JavaScript engine. SOAtest/Virtualize 9.10 ships with Java 8, which uses the Oracle Nashorn JavaScript engine as the default. Scripts saved in earlier versions of SOAtest/Virtualize with the Mozilla Rhino engine will now run in the Oracle Nashorn engine with Mozilla compatibility extensions loaded. The scripts will continue to function as before, but with significantly improved runtime performance. For additional details, see the SOAtest/Virtualize user's guide.
JDBC ODBC Driver Changes
The recommended best practice for connecting to databases via ODBC in SOAtest/Virtualize is to use vendor-specific ODBC drivers. SOAtest/Virtualize versions prior to 9.10 shipped with Java 7, which included a JDBC-ODBC driver in the associated JDK. This is deprecated in Java 8, so it is no longer available with SOAtest/Virtualize 9.10. Any DB Tools or data sources which were configured to use the previous JDBC ODBC driver will need to be reconfigured to use a different driver.
