Configuring the web application server for your JDBC driver
The web application server where you plan to deploy Campaign must contain the correct JAR file to support JDBC connections. You must add the location of the JAR file to the class path of the web application server.
Complete the following actions for each database type that Campaign will connect to, so the Campaign Java component can access the Campaign system tables.
1.
Consult the Recommended Software Environments and Minimum System Requirements document to determine the correct JAR file for your database type.
The following database drivers are supported:
*
*
For IBM® DB2® 9.7: db2jcc.jar
*
For IBM® DB2® 10.1: db2jcc4.jar
*
2.
*
If the driver does not exist on the machine where you plan to deploy Campaign, copy the driver to any location on that machine. Unpack the driver in a path that does not include spaces.
*
3.
*
For all supported versions of WebLogic, set the classpath in the setDomainEnv script in the WebLogic_domain_directory/bin directory where environment variables are configured.
The driver must be the first entry in the CLASSPATH list of values before any existing values. For example:
UNIX
CLASSPATH="/home/oracle/product/<version>/jdbc/lib/ojdbc6.jar:
${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}
${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
export CLASSPATH
Windows
set CLASSPATH=c:\oracle\jdbc\lib\ojdbc6.jar;%PRE_CLASSPATH%;
%WEBLOGIC_CLASSPATH%;%POST_CLASSPATH%;%WLP_POST_CLASSPATH%
*
For all supported versions of WebSphere®, set the classpath in the Administration console when you set up the JDBC providers for the IBM® EMM products.
4.
During startup, monitor the console log to confirm that the classpath contains the path to the database driver.