Configuring the web application server for your JDBC driver

Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM® SPSS® Modeler Advantage Enterprise Marketing Management Edition requires 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 where you plan to deploy Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition.

Procedure

  1. Obtain the latest vendor-provided Type 4 JDBC driver that is supported by IBM EMM, 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 Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition, 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 Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition.
    The following table lists the driver file name or names.
    Table 1. Driver files for the databases

    This two-columned table provides information about the database in one column, and the driver files in the second column.
    Database Files

    Oracle

    ojdbc6.jar, ojdbc5.jar

    Use the database drivers from Oracle 12. Memory issues can occur if you use the database drivers from Oracle 11.

    DB2®

    db2jcc.jar

    db2jcc4.jar- required for V10.1

    db2jcc_license_cu.jar - not required in V9.5 and higher

    SQL Server

    Use version 2.0 of the SQL Server driver and above. See the Recommended Software Environments & Minimum System Requirements guide for the exact version of the driver to use.

    sqljdbc4.jar
    The following table lists the driver file name or names for the databases that are supported for system tables.
    Database Files

    DB2

    db2jcc4.jar - required for V10.1

    db2jcc_license_cu.jar - not required in V9.5 and higher

    Oracle 11 and 11g

    ojdbc6.jar

    Use the database drivers from Oracle 12. Memory issues can occur if you use the database drivers from Oracle 11.

    Oracle 11 and 11g is supported only for profile tables.
  2. Add the full path to the driver, including the file name, to the class path of the web application server where you plan to deploy Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition.
    According to the web application server where you plan to deploy Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition, use the following guidelines.
    • 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/11.0.0/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 class path when you set up the JDBC providers for Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition.
  3. Make a note of the database driver class path in the Marketing PlatformCampaignDistributed MarketingeMessageContact OptimizationInteractLeadsOpportunity DetectDigital Analytics for On PremisesCustomerInsightPredictiveInsightMarketing OperationsInteraction HistoryAttribution ModelerIBM SPSS Modeler Advantage Enterprise Marketing Management Edition installation worksheet, as you must enter the path when you run the installer.
  4. Restart the web application server so that your changes take effect.

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