The following steps explain how to set up the Parasoft JDBC Driver for the sample ParaBank application that ships with Parasoft Virtualize:

  1. If you haven’t already done so, start the Virtualize server (see Working with the Local Virtualize Server or Working with a Remote Dedicated Virtualize Server).
  2. Create the ParaBank project:
    1. Go to File > New > Project.
    2. Choose Virtualize > ParaBank Example Project and click Next.
    3. Enter a name for the project, then click Finish.
  3. Open the Java perspective and ensure that the project is configured to build automatically by selecting the ParaBank project in the Package Explorer view and opening the Project menu to check that Build automatically is enabled. If it's not, enable it.
  4. Copy the ParasoftJDBCDriver.jar file shipped with Parasoft Virtualize (located in <INSTALL_DIR>/proxies).
  5. Open the Package Explorer view and paste the ParasoftJDBCDriver.jar file to Parabank/src/main/webapp/WEB-INF/lib.
  6. Edit the jdbc.properties file (located in ParaBank/src/main/java) in the Package Explorer view 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=

  7. In the Java perspective, choose Run > Run Configurations.
  8. Select Apache Tomcat > ParaBank Tomcat <VERSION> Server.

  9. 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

  10. Start (or restart) the ParaBank server with the updated Run Configuration.
  11. Open a web browser and log in to ParaBank.
  12. Refresh the Virtualize Server view and confirm the JDBC Controller is shown under the server tree. See Recording Queries and Data for the next steps.

If the related JDBC Controller does not appear in the Virtualize Server view, try refreshing the project, cleaning the project, cleaning the server, then restarting the server.

Troubleshooting ParaBank

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:

  1. Open the Java perspective.
  2. Open the Servers view.
  3. In the Servers view, right-click ParaBank Tomcat <VERSION> Server and choose Clean.
  4. Right-click ParaBank Tomcat <VERSION> Server and choose Restart.
  • No labels

Need assistance? Visit our support page