Step: Configure the web application server for your JDBC driver

You must obtain the correct JAR file for the JDBC connections the Marketing Platform requires. You must also add the location of the file to the classpath of the web application server where you plan to deploy the Marketing Platform.

1.	Obtain the latest vendor-provided Type 4 JDBC driver supported by IBM® EMM, as described the Recommended Software Environments and Minimum System Requirements document.

If the driver does not exist on the machine where the Marketing Platform will be deployed, obtain it and unpack it on the machine where you plan to deploy the Marketing Platform. Unpack the drivers in a path that does not include spaces.

If you obtain the driver from a machine where the data source client is installed, verify that the version is the latest supported by IBM® .

2.	Include the full path to the driver, including the file name, in the classpath of the web application server where you plan to deploy the Marketing Platform, as follows.

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. Your driver entry must be the first entry in the CLASSPATH list of values, before any existing values, to ensure that the web application server uses the correct driver. For example:

UNIX™

CLASSPATH="/home/oracle/product/10.2.0/jdbc/lib/ojdbc14.jar:
${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}
${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
export CLASSPATH

Windows™

set CLASSPATH=c:\oracle\jdbc\lib\ojdbc14.jar;%PRE_CLASSPATH%;
%WEBLOGIC_CLASSPATH%;%POST_CLASSPATH%;%WLP_POST_CLASSPATH%

For all supported versions of WebSphere®, you set the classpath in the next step, while you are setting up the JDBC providers for the Marketing Platform.

3.	Make a note of this database driver classpath in the Marketing Platform database information checklist, as you will need to enter it when you run the installer.

4.	Restart the web application server so your changes take effect.

During startup, monitor the console log to confirm that the classpath contains the path to the database driver.