IBM® Content Manager supports only the IBM DB2® Driver for JDBC and SQLJ (type 2 and type 4). This driver is sometimes referred to as the JCC JDBC driver. This driver requirement affects the IBM Content Manager connector.
The type 4 driver is a pure Java™ driver, which means that the application requires only the JAR files and does not require the DB2 Runtime Client. However, in this mode, when the IBM Content Manager application uses the JDBC driver, you must explicitly specify the host name and the port of the database that is being connected to. Specifying the host name and port eliminates the need to use the database catalog. However, if the host name, port, or the remote database are not specified in the cmbicmsrvs.ini file for IBM Content Manager connector, the type 2 connection is used by default. The type 2 connection requires the DB2 Runtime Client and a database cataloged on the local system.
If the host name, port, and the remote database name are specified, but the values are incorrect, an error results when IBM Content Manager attempts to make a type 4 connection, for example: DGL0394A: Error in::DriverManager.getConnection; [jcc][10389][12245][3.50.152] Failure in loading native library db2jcct2
To correct this error, you must update the INI file to include the correct information.
export LD_LIBRARY_PATH=/export/home/db2inst1/sqllib
/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib:$LD_LIBRARY_PATH
export LIBPATH=/home/db2inst1/sqllib/lib:$LIBPATH
[DB2 Instance Dir]/sqllib/lib ->
[DB2 Instance Dir]/sqllib/lib64 ->
[DB2 Product Installation Dir]/lib64
[DB2 Instance Dir]/sqllib/lib32 -> [DB2 Product Installation Dir]/lib32
If a 32-bit JVM is used to run the Java IBM Content Manager application and the type 2 connection is configured, then the path to 32-bit libraries must be listed before the path to the 64-bit libraries in LD_LIBRARY_PATH or LIBPATH. For example, on AIX:
export LIBPATH=/opt/IBM/db2/V9.7/lib32:$LIBPATH
The JAR files that are required for IBM DB2 Driver for JDBC and SQLJ (type 2 and type 4) are:
These JAR files are packaged with IBM Content Manager. An additional JAR file, db2jcc_license_cisuz.jar is required to connect to zSeries® servers. The db2jcc_license_cisuz.jar is also packaged with IBM Content Manager.
The existing cmbicmsrvs.ini file for the IBM Content Manager connector supports IBM DB2 Driver for JDBC and SQLJ.
IBM Content Manager also allows you to override the host name, port, and remote database name values by specifying the JDBC driver and JDBC URL directly. To specify the JDBC driver and the JDBC URL directly, IBM Content Manager provides two properties, ICMJDBCDRIVER and ICMJDBCURL in the cmbicmsrvs.ini file for IBM Content Manager connector. You can also provide the JDBCURL and JDBCDRIVER properties by using the connect_string parameter associated with the DKDatastoreICM::connect method.
In IBM Content Manager, these properties are optional and do not have any values. You can specify the values of these properties by choosing either of the following ways:
Setting both the URL and the driver is not a requirement. You might specify either the URL or the driver.
To specify a driver other than the IBM DB2 Driver for JDBC and SQLJ, the values for the ICMJDBCDRIVER and ICMJDBCURL properties must be manually set in the cmbicmsrvs.ini file. IBM Content Manager supports only the IBM DB2 Driver for JDBC and SQLJ when connecting to a DB2 database. IBM Content Manager does not support any other driver for a DB2 database.
You can set the values for the ICMJDBCDRIVER and ICMJDBCURL properties in the INI file:
ICMJDBCDRIVER=com.ibm.db2.jcc.DB2Driver
ICMJDBCURL=jdbc:db2://myhostname.ibm.com:50000/icmnlsdb
When an IP address is used instead of a host name in the JDBC URL, square brackets ([ and ]) must enclose the IP address if IPv6 is used. For example, the connect string for IPv6 address 2007::9:181:141:150 must be entered in the following format:
JDBCURL=jdbc:db2://[2007::9:181:141:150]:50000/icmnlsdb