The following steps explain how to set up the Parasoft JDBC Driver for the sample ParaBank application that ships with Parasoft Virtualize:
ParasoftJDBCDriver.jar
file to ParaBank/WebContent/WEB-INF/lib
. C:\Users\<username>\parasoft\<your_workspace>\ParaBank\WebContent\WEB-INF\lib
.ParaBank/src/jdbc.properties
file to read as follows (with no extra spaces):jdbc.driverClassName=com.parasoft.xtest.jdbc.virt.driver.JDBCProxyDriver
jdbc.url=jdbc:parasoft:proxydriver:org.hsqldb.jdbcDriver:@jdbc:hsqldb:hsql://localhost/parabank
jdbc.username=sa
jdbc.password=
Under the Arguments tab, add the following Parasoft JDBC Driver flags to what is already listed in the VM arguments section:
-Dparasoft.virtualize.server.url=http://localhost:9080 -Dparasoft.virtualize.group.id=parabank -Dparasoft.virtualize.driver.register.jdbcproxydriver.in.drivermanager=true -Dparasoft.virtualize.driver.proxy.direct=true |
If the related JDBC Controller does not appear, try refreshing the project, cleaning the project, cleaning the server, then restarting the server.
If you upgrade from a previous installation of Virtualize and the browser displays a 404 Error
message after the upgrade—even if the Java perspective reports that the server started properly—you need to clean the workspace as follows: