Deploying JDBC proxy into Software AG webMethods Integration Server

You must deploy the JDBC proxy on each application server that is running webMethods Integration Server (WMIS). With the JDBC proxy, you can allow a server that hosts applications to use JDBC to access a live database to be recorded or virtualized.

About this task

Important: Differences between WMIS 7.x/8.0 and WMIS 8.2 (or later) are indicated where relevant.

After you install the HCL OneTest™ API webMethods Integration Server adapter package, deploy the JDBC proxy into WMIS:

Procedure

  1. Download and extract the JDBC driver package that is provided with HCL Quality Server. For more information, see HCL OneTest API 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 <Software AG installation directory>\IntegrationServer\lib\jars or to whichever WMIS folder that contains 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
  3. Configure the server start script (Software AG installation directory\IntegrationServer\bin\server.bat) as follows:
    WMIS 7.x/8.0 WMIS 8.2 and later
    Change %JAVA_RUN% -DWM_HOME= to 
    %JAVA_RUN% -Djbdc.drivers=com.greenhat.jdbc.Driver -DWM_HOME=
    		 Change SET JAVA_OPTS=-Dsun.lang.classLoader to 
    SET JAVA_OPTS=-Djdbc.drivers=com.greenhat.jdbc.Driver -Dsun.lang.classLoader
    Note: If the server.bat file does not have the JAVA_OPTS environment variable, add the line 
    SET JAVA_OPTS=-Djdbc.drivers=com.greenhat.jdbc.Driver
    to the file.
    Tip: For Unix-like installations, use server.sh, forward slashes ("/") instead of backslashes ("\"), and the appropriate Unix-like directory names.
  4. Save and close the file.
  5. If necessary, edit the server tag in the registration.xml file to the URL of the HCL Quality Server 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 OneTest™ API and HCL Quality Server to control JDBC recording and stubbing. For more information, see HCL OneTest API reference and HCL OneTest Virtualization overview.