Configuring the web application server for your JDBC driver

The web application server where you plan to deploy Collaborate 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.

WebSphere

About this task

If you are using WebSphere and if you allow the installer to create the data source when you install the product, then you can skip the step in the following procedure about setting the classpath. Otherwise, if you want to allow the installer to create the data source, then perform the following step.

Procedure

To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Datasource checkbox and provide information about your application server WebSphere profile.

WebLogic

About this task

If you are using WebLogic, perform the complete steps.

Procedure

  1. Obtain the latest vendor-provided Type 4 JDBC driver for your system table database that is supported by HCL Unica, 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 Unica Collaborate, 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 Unica Collaborate.
  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 Unica Collaborate.
    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="/opt/drivers/ojdbc8.jar":
      ${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH} 
      ${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
      export CLASSPATH
      

      product="Campaign DAOP DistMkt Deliver Interact Leads Plan Optimize Platform AttribMod IntHist"> Windows™

      set CLASSPATH=c:\oracle\jdbc\lib\ojdbc8.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 Unica Collaborate.
  3. Make a note of the database driver class path in the Unica Collaborate 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.

JBoss

About this task

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

Procedure

  1. Obtain the latest vendor-provided Type 4 JDBC driver for your system table database that is supported by HCL Unica, 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 Unica Collaborate, 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 Unica Collaborate.
  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 Unica Collaborate.
    Use the following guidelines.
    • For all supported versions of JBoss, add the JDBC driver as module. Use the following procedure to add the JDBC driver as a module.

      For example, for SQL Server:

      module add --name=com.microsoft.sqlserver.jdbc --resources=<JDBC_Driver_Location>\sqljdbc4.jar --dependencies=javax.api,javax.transaction.api
    • Register this SQL JDBC Driver using the following guidelines: For example:
      • /subsystem=datasources/jdbc-driver=sql:add(driver-module-name=com.microsoft.sqlserver.jdbc,driver-name=sql,driver-xa-datasource-class-name=com.microsoft.sqlserver.jdbc.SQLServerXADataSource)
      • /subsystem=datasources/jdbc-driver=sql:read-resource
      • /subsystem=ee/service=default-bindings:write-attribute(name=datasource, value=undefined)
  3. Make a note of the database driver class path in the Unica Collaborate 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.

Apache Tomcat

About this task

If you are using Apache Tomcat, you must perform this entire procedure.

Procedure

  1. Obtain the latest vendor-provided Type 4 JDBC driver for your system table database that is supported by HCL Unica, 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 Collaborate, 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 Unica Collaborate.
  2. Add the full path to the driver, including the file name, to the class path of the (<Tomcat_Installed Location>/lib) web application server where you plan to deploy Collaborate.
  3. Make a note of the database driver class path in the Unica Collaborate 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.