Creating JDBC connections in web application server

Create JDBC connections on each of the web application servers where Unica Campaign is deployed. Unica Campaign uses the JDBC connections to access the required databases.

About this task

Use the following list to determine which JDBC connections you must create for the Unica Campaign web application. The steps include the suggested and required JNDI names.
Note: JNDI for Unica Platform and Unica Campaign must be separate. You must not use the same JNDI (even if underlying database is same) for Unica Platform and Unica Campaign.

For more information about creating JDBC connections in your web application server, see the WebLogic or WebSphere® documentation.


  1. 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 Unica Campaign in the same JVM as your Unica 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.
  2. Create a connection to the database holding the Unica Campaign system tables.

    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.
  3. Record all JNDI names in theUnica Campaign installation worksheet