Unica Plan

Create the JDBC connections in the application server

You must create this JDBC connection in the web application server where you plan to deploy Unica Plan.

You can allow the installer to create this data source when you install Unica Plan. To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Plan Datasource check box and supply information about your application server.

  • The installer creates the data source using plands 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.
  • Also, if you are using Tomcat, you must add the JDBC driver to your classpath manually even if you allow the installer to create the data source.
  • Automatic data source creation during installation is not supported for the JBoss Application Server.

Follow these guidelines if you decide to create the data source manually.

In WebSphere®, set the classpath for your database driver during this process.

In Tomcat®, set the classpath for your database driver during this process.
Note: You must manually encrypt password using encryptTomcatDBPasswords.sh utility available under Platform_HOME/tools/bin.

In JBoss®, set the classpath for your database driver by adding the module for the JDBC driver and register the SQL JDBC driver.

Important: For the connection to the database holding the Unica Plan system tables, you must use plands as the Java™ Naming and Directory Interface (JNDI) name. This value is the required JNDI name.
Important: For the connection to the database holding the Unica Plan system tables, you must use UnicaPlatformDS as the JNDI name. This is the required JNDI name. If you are deploying Unica Plan and Unica Plan in the same JVM, this connection should already exist.

If you expect to have many concurrent users in Unica Plan, you may need to increase the number of connections in your web server. For best results, set your web server to allow 50 connections.

The following sections provide information on creating JDBC connections on different application servers.

Information for creating JDBC connections

Note: If you are not using the default port setting for your database, make sure that you change it to the correct value.
Note: Plan requires the following settings in JDBC connection string.

IFX_ISOLATION_LEVEL=2

IFX_LOCK_MODE_WAIT=60

WebLogic

Use the following values if your application server is WebLogic.

OneDB

  • Database Driver: IBM's Informix Driver (Type 4 XA) Versions: Any
  • Default port: NA
  • Driver class: com.informix.jdbc.IfxDriver
  • Driver URL: jdbc:informix-sqli://<your_hostname>:<your_port>/<your_databaseName>:INFORMIXSERVER=<your_serverName>
  • Properties: Add user=<your_db_user_name>

Tomcat

Use the following values if your application server is Tomcat.

OneDB
  • Driver: OneDB JDBC Driver
  • Default port: NA
  • Driver class: com.informix.jdbc.IfxDriver
  • Driver URL: jdbc:informix-sqli://<your_hostname>:<your_port>/<your_databaseName>:INFORMIXSERVER=<your_serverName>
  • Properties: Add user=<your_db_user_name>

JBOSS

Use the following values if your application server is JBOSS.

OneDB
  • Database Driver: Onedb jdbc driver
  • Database type: informix_jdbc-4.50.3.jar
  • Default port: NA
  • Driver class: com.informix.jdbc.IfxDriver
  • Driver UR: jdbc:informix-sqli://<your_hostname>:<your_port>/<your_databaseName>:INFORMIXSERVER=<your_serverName>;IFX_ISOLATION_LEVEL=2;IFX_LOCK_MODE_WAIT=60

  • valid-connection-checker class-name= org.jboss.jca.adapters.jdbc.extensions.informix.InformixExceptionSorter

  • driver: xa-datasource-class-name= com.informix.jdbc.IfxDriver
    Note: See the JBOSS documentation for more details.

WebSphere

OneDB
  • Database Driver: OnedB jdbc driver
  • Default port: NA
  • Driver class: com.informix.jdbc.IfxDriver
  • Driver URL: jdbc:informix-sqli://<your_hostname>:<your_port>/<your_databaseName>:INFORMIXSERVER=<your_serverName>
  • Properties: Add user=<your_db_user_name>