Deploying JDBC proxy into TIBCO BusinessWorks

You must deploy the JDBC proxy on each application server that is running TIBCO BusinessWorks. With the JDBC proxy, you can enable a server that hosts applications to use JDBC to access a live database that you want to record or virtualize.

About this task

In BusinessWorks, the set of applications that can be used are hosted within the TIBCO Runtime Agent. These applications are configured through individual TRA files, which are used to specify the application configuration.

To deploy the JDBC proxy into BusinessWorks:

Procedure

  1. Download and extract the JDBC driver that is provided with HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel). For more information, see DevOps Test Integrations and APIs tool packages.
  2. Copy the files that are listed in the following table and the JDBC proxy configuration file (registration.xml) from the downloaded JDBCIntercept.zip package to <TIBCO installation directory>\tpcl\<Version number>\jdbc or to whichever BusinessWorks folder that contain JDBC drivers.
    JDBC / Java™ version File name Description
    JDBC 4, Java™ 1.6 or later

    com.ibm.rational.rit.jdbcdriver4.jar

    jsqlparser15.jar and antlr-3.4.jar

    The JDBC proxy.

    Supporting libraries.

    Notes:
    • Currently, JDBC 4, Java 1.6 or later is supported for the JDBC proxy and its supporting libraries. You must add the three JAR files com.ibm.rational.rit.jdbcdriver4.jar, jsqlparser15.jar and antlr-3.4.jar to each application server directory that contains JDBC drivers.
    • The following items are not supported for vendor-specific Oracle SQLs:
      • Oracle-specific DDL statements
      • Custom functions
      • Subqueries
      • PIVOT and UNPIVOT statements
      • Nested tables containing multiple columns or single column of user-defined-types
      • Stubs with nested tables
    Warning: If you copy the files to <TIBCO installation directory>\tpcl\<Version number>\lib in addition to, or instead of, copying them to <TIBCO installation directory>\tpcl\<Version number>\jdbc, TIBCO Designer, and the JDBC proxy might not work properly.
  3. Configure the relevant TRA file (for example, for TIBCO Designer 5.6, the location of the file might be <TIBCO installation directory>\designer\5.6\bin\designer.tra) by adding the following text: 
    java.property.jbdc.drivers com.greenhat.jdbc.Driver
  4. Save and close the TRA file.
  5. If necessary, edit the server tag in the registration.xml file to the URL of the Test Virtualization Control Panel installation that is being used.

    For information about modifying this file, see Modifying the configuration settings of the JDBC proxy.

  6. Optional: Edit the domain and environment tags in the registration.xml file.
    Important: If these tags are modified, the JDBC proxy is used only when you record and stub within the specified domain and environment.
  7. Use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) and Test Virtualization Control Panel to control JDBC recording and stubbing. For more information, see API Tester Reference and DevOps Test Virtualization overview.