Adding the JDBC drivers to the Oracle WebLogic Server startup script

You must add the JDBC drivers for your database to the Oracle WebLogic Server startup script to so that IBM® Content Navigator can access its configuration database table.

About this task

The version of the JDBC driver file that you use must match the JDBC driver version on the system where Oracle WebLogic Server is installed. See Prerequisites for installing IBM Content Navigator for information about the software that is supported for your database type.

Important: If you plan to deploy IBM Content Navigator in a highly available cluster, you must complete the following steps for each node in the cluster.

To prepare Oracle WebLogic Server for IBM Content Navigator:

1. Copy the JDBC drivers for your database to the IBM Content Navigator server.
   1. Obtain the JDBC drivers for your database type:

      DB2®

      Access the IBM Support website and find the version of the Redistributable DB2 JDBC Driver that matches the version of the JDK on the system where Oracle WebLogic Server is installed.

      Microsoft SQL Server

      Access the Microsoft Support website and find the version of the SQL Server JDBC Driver that matches the version of the JDK on the system where Oracle WebLogic Server is installed.

      Oracle

      Access the Oracle Software Downloads web page and find the JDBC driver file that matches the version of the JDK on the system where Oracle WebLogic Server is installed.

   2. Extract the JDBC driver file to a directory on the IBM Content Navigator server. For example:

      Table 1. Suggested location of the JDBC driver file on the IBM Content Navigator server

      Operating system	Recommended directory
      AIX®	/opt/jars
      Linux	/opt/jars
      Linux for System z®	/opt/jars
      Windows	C:\jars

2. Open the Oracle WebLogic Server startup script, startWebLogic.cmd or startWebLogic.sh, by default, the startup script is in the following directory:
   • AIX: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
   • Linux: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
   • Linux for System z: /opt/Oracle/Middlware/user_projects/domains/domain_name/bin/startWebLogic.sh
   • Windows: C:\Oracle\Middleware\user_projects\domains\domain_name\bin\startWebLogic.cmd
3. Add the JDBC driver to the startup script:
   • DB2
     Add the db2jcc.jar and db2jcc_license_cu.jar files to the Oracle WebLogic Server class path:

     • For example, on AIX, Linux, and Linux for System z, enter:

       JDBC_PATH="/opt/jars/db2jcc.jar:opt/jars/db2jcc_license_cu.jar"
       
       SAVE_CLASSPATH="${CLASSPATH}:${JDBC_PATH}"

     • For example, on Windows, enter:

       set JDBC_PATH=C:\jars\db2jcc.jar;C:\jars\db2jcc_license_cu.jar
       set CLASSPATH=%JDBC_PATH%;%CLASSPATH%

     Remember: These examples assume that you saved the JDBC files to either /opt/jars or C:\jars
   • Microsoft SQL
     Add the sqljdbcn.jar file to the Oracle WebLogic Server class path, where n is the version of the JDBC driver:

     • For example, on AIX, Linux, and Linux for System z, enter:

       JDBC_PATH="/opt/jars/sqljdbcn.jar"
       
       SAVE_CLASSPATH="${CLASSPATH}:${JDBC_PATH}"

     • For example, on Windows, enter:

       set JDBC_PATH=C:\jars\sqljdbc4.jar
       set CLASSPATH=%JDBC_PATH%;%CLASSPATH%

     Remember: These examples assume that you saved the JDBC files to either /opt/jars or C:\jars
   • Oracle
     Add the ojdbcn.jar file to the Oracle WebLogic Server class path, where n is the version of the JDBC driver:

     • For example, on AIX, Linux, and Linux for System z, enter:

       JDBC_PATH="/opt/jars/ojdbcn.jar"
       
       SAVE_CLASSPATH="${CLASSPATH}:${JDBC_PATH}"

     • For example, on Windows, enter:

       set JDBC_PATH=C:\jars\ojdbc6.jar
       set CLASSPATH=%JDBC_PATH%;%CLASSPATH%

     Remember: These examples assume that you saved the JDBC files to either /opt/jars or C:\jars
4. Save your changes to the startup script.
5. Restart the application server and verify that the application server starts without errors.