Set Up Database Connectivity for the Content Store Database

If you are using a database other than Cognos Content Database as the content store, you may have to install database client software, or JDBC drivers, or both, on each computer where you install Content Manager. Doing this allows Content Manager to access the content store database.

Steps for DB2

1. If you are using type 2 JDBC connectivity, install the DB2 client software on the Content Manager computers.

   If you use type 4 JDBC connectivity for DB2, you are not required to install the DB2 client software where Content Manager is installed. If you are using a DB2 database on z/OS for the content store, you must use type 4 JDBC connectivity.

   For more information about the differences between type 2 and type 4 drivers, see JDBC Driver Options for Using DB2 Database as a Content Store.

2. If you are using type 2 JDBC connectivity, and the content store is on a different computer than Content Manager, configure a database alias to the content store.

   On Windows, run the DB2 Client Configuration Assistant.

   On UNIX or Linux, use the DB2 command line interface.

   If the content store database and Content Manager are on the same computer, the content store name automatically becomes the alias.

   When you configure the Content Manager computers, ensure that they are all configured to use the same content store.

3. On Windows, stop the DB2 services and the HTML Search Server.

4. Copy the following files from DB2_installation/sqllib/java directory to the c8_location/webapps/p2pd/WEB-INF/lib directory.

   • the universal driver file, db2jcc.jar

   • the license file

     for DB2 on Linux, UNIX, or Windows, db2jcc_license_cu.jar

     for DB2 on z/OS, db2jcc_license_cisuz.jar

   If you are connecting to DB2 on z/OS, use the driver version from Linux, UNIX, or Windows version 9.1 fix pack 5 or version 9.5 fix pack 2.

   Tip: To check the driver version, run the following command

   java -cp path\db2jcc.jar com.ibm.db2.jcc.DB2Jjcc -version

5. On Windows, restart the DB2 services and the HTML Search Server.

6. On UNIX, if you are using type 2 JDBC connectivity, ensure that the 32-bit DB2 libraries are in the library search path, which is usually the $DB2DIR/lib directory or the $DB2DIR/lib32 directory.

7. Repeat this entire procedure on the IBM Cognos 8 computers where Content Manager is installed or where notification is sent to a DB2 database.

You can tune the database to take advantage of DB2 features. For more information, see the Tuning a DB2 Content Store.

Steps for Oracle

1. On the computer where the Oracle client is installed, go to the ORACLE_HOME/jdbc/lib directory.

2. Copy the appropriate JAR file to the c8_location/webapps/p2pd/WEB-INF/lib directory on computers where Content Manager is installed and where notification is sent to an Oracle database.

   • If you use Java 1.4, copy the ojdbc14.jar file

   • If you use Java 1.5, copy the ojdbc5.jar file

   If the directory contains the classes12.jar file, delete it before installing the ojdbc14.jar or ojdbc5.jar file.

   The driver is available from an Oracle client or server install, and it can also be downloaded from the Oracle technology Web site (http://www.oracle.com/technology).

Steps for Sybase

1. On the computer where Sybase is installed, go to the Sybase_location/jConnect-5_5/classes directory.

2. Copy the jconn2.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on every computer where Content Manager is installed and where notification is sent to a Sybase database.