Configuring the web application server for your JDBC driver

The web application server where you plan to deploy Distributed Marketing must contain the correct JAR file to support JDBC connections. This enables your web application to connect to the system tables. The location of the JAR file must be included in the class path of the web application server.

About this task

If you are using WebSphere, and if you allow the installer to create the data source when you install the product, you can skip the step in this procedure about setting the classpath. To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Distributed Marketing Datasource check box and supply information about your WebSphere profile. If you do not want to allow the installer to create the data source, then perform this entire procedure.

If you are using WebLogic, you must perform this entire procedure.

Procedure

Obtain the latest vendor-provided Type 4 JDBC driver for your system table database that is supported by IBM® Marketing Software, as described in the Recommended Software Environments and Minimum System Requirements guide.
Use the following guidelines after you obtain the JDBC driver.
- If the driver does not exist on the server where you plan to deploy Distributed Marketing, obtain it and unpack it on the server. Unpack the drivers in a path that does not include spaces.
- If you obtain the driver from a server where the data source client is installed, verify that the version is the latest supported by Distributed Marketing.
Note: For Oracle, use the database drivers from Oracle 12. If you use the database drivers from Oracle 11, you might face memory issues.
Include the full path to the driver in the class path of the web application servers where you plan to deploy IBM Marketing Software products, as follows.
- For all supported versions of WebLogic, set the class path 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 class path 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/12.1.0.2/jdbc/lib/ojdbc6.jar:
		${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH} 
		${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
export CLASSPATH
```
  Windows™
```
set CLASSPATH=c:\oracle12.1.0.2\jdbc\lib\ojdbc6.jar;%PRE_CLASSPATH%;
%WEBLOGIC_CLASSPATH%;%POST_CLASSPATH%;%WLP_POST_CLASSPATH%
```
- For all supported versions of WebSphere®, set the class path in the Administration console while you are setting up the JDBC providers for the IBM Marketing Software products.
Restart the web application server so your changes take effect.
During startup, monitor the console log to confirm that the class path contains the path to the database driver.