Unica Campaign, Unica Optimize, Unica COM, Unica Deliver
Creating JDBC connections in web application server
Create JDBC connections on each of the web application servers where Campaign is deployed. Campaign uses the JDBC connections to access the required databases.
For more information about creating JDBC connections in your web application server, see the WebLogic or WebSphere® documentation.
- Create a connection to the database holding the Unica Platform system
tables. Use UnicaPlatformDS as the JNDI name.Important: UnicaPlatformDS is the required JNDI name.
If you are deploying Campaign in the same JVM as your Platform deployment, you have probably already set up this connection.
Note: If you are using WebLogic to configure a connection to an Oracle or DB2® database, you must also specify the database user name in the form user=<DBUser> in the Properties section on the Connection Pool tab. - Create a connection to the database holding the Unica Campaign system
tables.Note: You can allow the installer to create this data source (for one partition only) when you install Unica Campaign.
To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Campaign Datasource check box and supply information about your application server.
- The installer creates the data source using campaignPartition1DS as the JNDI name.
- Note that, if you are using WebLogic, you must add the JDBC driver to your classpath manually even if you allow the installer to create the data source. The installer does this automatically for WebSphere.
- Automatic DataSource creation during installation is not supported for the JBOSS application server.
If you do not want to allow the installer to create the data source, then you must create this data source.
If there is one partition, the suggested JNDI name is campaignPartition1DS.
If there are multiple partitions, a best practice is to use campaignPartition1DS for the first connection, campaignPartition2DS for the second, and so on.Note: This practice is provided as an example. You can specify any JNDI names for Unica Campaign system table connections.
The following sections provide information on creating JDBC connections on different application servers.
WebLogic
Use the following values if your application server is WebLogic.
OneDB
- Driver: ONEDB JDBC DRIVER
- Default port:
<OneDB port>
- Driver class:
com.informix.jdbc.IfxDriver Driver URL: jdbc:informixsqli:// <your_db_host>:<your_db_service_port>/ <your_db_name>:INFORMIXSERVER=<OneDB_servername>
- Properties:
INFORMIXSERVER user=<your_db_user_name>
- Properties::
INFORMIXSERVER password=<your_db_password>
WebSphere
Use the following values if your application server is WebSphere.
- Database Type - Informix
- Provider Type - Informix JDBC Driver
- Implementation type - Connection pool data source
On the next step - mention directory location where onedb-jdbc-8.0.0.1-complete.jar is located.
JNDI creation steps
- Provider JNDI name:
- OneDB lock mode wait = 2
- Server name = name of the server <onedb>
- Database name = name of database
- ifxIFXHOST - database host machine name
Tomcat
Use the following values if your application server is Tomcat.
- Driver: ONEDB JDBC DRIVER
- Default port:
<OneDB port>
- Driver class:
com.informix.jdbc.IfxDriver
- Driver URL:
jdbc:informix-sqli://< your_db_host>:<your_db_service_port>/ <your_db_name>:INFORMIXSERVER=<onedb_servername>
- Properties: Add user=
<your_db_user_name>
- Properties: Add password=
<your_db_password>
JBOSS
Use the following values if your application server is JBOSS.
- Database Driver: OneDB JDBC driver
- Default port:
<OneDB port>
- Driver class:
com.informix.jdbc.IfxDriver
- Driver URL:
jdbc:informix-sqli://< your_db_host>:<your_db_service_port>/ <your_db_name>:INFORMIXSERVER=<onedb_servername>
- valid-connection-checker class-name=
org.jboss.jca.adapters.jdbc.extensions.informix.InformixExceptionSorter
- driver-xa-datasource-class-name=
com.informix.jdbc.IfxDriver