Configuring the web application server for your JDBC driver
The web application server where you plan to deploy Unica Journey 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
Automatic Datasource Creation by the installer is not supported in the Journey Application. We need to do Manual steps to create the DataSources for the Journey Application.
Perform the following step to create the datasource:
- Access the WebSphere Admin Console
- Set Up the Data Source in WebSphere
- Continue the Wizard: Set Up the JDBC Provider
- Specify Security Aliases
- Test the Data Source
For more information, please refer the WebSphere documentation.
JBoss
About this task
If you are using JBoss, 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 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 Journey, 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 Journey.
-
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 Journey.
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>\mssql-jdbc-7.0.0.jre8.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)
- For all supported versions of JBoss, add the JDBC driver as
module. Use the following procedure to add the JDBC driver as a
module.
- Make a note of the database driver class path in the Unica Journey installation worksheet, as you must enter the path when you run the installer.
-
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
-
Obtain the latest vendor-provided Type 4 JDBC driver for your system table
database that is supported by 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 Journey, 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.
- 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 Unica Journey.
- Make a note of the database driver class path in the Unica Journey installation worksheet, as you must enter the path when you run the installer.
-
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.