How to update the JDBC Driver in IBM Sterling B2B Integrator version 6.x

Steps

The examples below pertains to a Linux/UNIX installation of B2Bi using an Oracle DB.  The install path of B2Bi in this example: /installs/b2bi. Modify these values as appropriate for your environment.

1) Stop B2Bi.

2) Run the install3rdParty.sh/cmd found in the /installs/b2bi/bin directory.

The example below will install the new driver (ojdbc7.jar, in this example) into the B2Bi file system and modify some of the configuration files. The name of the DB jar will depend on the type of DB and the driver version being used.

/installs/b2bi/bin>./install3rdParty.sh Oracle 12.1.0.2 -d <path of the Oracle driver>/ojdbc7.jar

3) Verify the new driver is referenced in the configuration files below. If not, add an entry for the new driver manually. Make sure to comment out all the entries in dynamicclasspath.cfg, dynamicclasspath.cfg.in and dynamicclasspathAC.cfg that reference the old driver (e.g. ojdbc6.jar).

dynamicclasspath.cfg:
#VENDOR_JAR=/installs/b2bi/dbjar/jdbc/Oracle/ojdbc6.jar
#DB_JAR=/installs/b2bi/dbjar/jdbc/Oracle/ojdbc6.jar
DB_JAR=/installs/b2bi/dbjar/Oracle/12.1.0.2/ojdbc7.jar

dynamicclasspath.cfg.in:
#VENDOR_JAR=&INSTALL_DIR;/dbjar/jdbc/Oracle/ojdbc6.jar
#DB_JAR=&INSTALL_DIR;/dbjar/jdbc/Oracle/ojdbc6.jar
DB_JAR=&INSTALL_DIR;/dbjar/Oracle/12.1.0.2/ojdbc7.jar

dynamicclasspathAC.cfg:  (This file only exists if you setup an Adapter Container)
#VENDOR_JAR=/installs/b2bi/osgi/system_bundle/dbjar/jdbc/Oracle/ojdbc6.jar
#DB_JAR=/installs/b2bi/osgi/system_bundle/dbjar/jdbc/Oracle/ojdbc6.jar
DB_JAR=/installs/b2bi/osgi/system_bundle/dbjar/Oracle/12.1.0.2/ojdbc7.jar

4) Manually update sandbox.cfg as follows:
Example of old values:
JDBC_DRIVER=/installs/b2bi/dbjar/jdbc/Oracle/ojdbc6.jar
DB_DRIVERS=/installs/b2bi/dbjar/jdbc/Oracle/ojdbc6.jar

Example of new values:
JDBC_DRIVER=/installs/b2bi/dbjar/Oracle/12.1.0.2/ojdbc7.jar
DB_DRIVERS=/installs/b2bi/dbjar/Oracle/12.1.0.2/ojdbc7.jar

5) Verify the JDBC driver has been updated in the following files. If not, modify the entries to refer to the new driver manually:
AGENTDynamicclasspath.cfg
AGENTDynamicclasspath.cfg.in

ACTIVEMQDynamicclasspath.cfg
ACTIVEMQDynamicclasspath.cfg.in     

APPDynamicclasspath.cfg
APPDynamicclasspath.cfg.in

6) Delete the old driver (for example, /installs/b2bi/dbjar/jdbc/Oracle/ojdbc6.jar).

7) On Windows installs you will also need to delete the old driver (e.g. ojdbc6.jar) and replace it with the new driver (e.g. ojdbc7.jar) in the C:\Installs\b2bi\jdk\jre\lib\ext directory.

8) If using the B2Bi REST APIs and/or the Customization UI (which are hosted on the Liberty Server) then you will need to upgrade the driver in the /installs/b2bi/liberty/wlp/usr/servers/SIServer/apps/APIjarsLib directory by deleting the old driver (e.g. ojdbc6.jar) and replacing it with the new driver (e.g. ojdbc7.jar).

9) Run setupfiles.sh/cmd
Example:
/installs/b2bi/bin>./setupfiles.sh

10) Run dump_info to verify that the JDBC driver now reflects the new driver version:
Example:
/installs/b2bi/bin>./dump_info.sh >dump.txt
In the dump_info output you can verify the driver version under the <DatabaseMetaData> tag section.
You can also verify the correct driver jar is being loaded in the Dynamic Class Loader section of the dump_info output.

11) Restart B2Bi.