Step: Create the JDBC connections in the web application server
The Campaign web application must be able to communicate with the required databases using JDBC connections. You create these JDBC connections in the web application server where you plan to deploy Campaign.
1.
Use the following list to determine which JDBC connections you must create for the Campaign web application. The list includes the suggested and required JNDI names.
*
A connection to the database holding the Campaign system tables:
*
If there is one partition, the suggested JNDI name is campaignPartition1DS.
*
If there is more than one partition, a best practice is to use campaignPartition1DS for the first connection, campaignPartition2DS for the second, and so on.
*
This practice is provided as an example only. You can specify any JNDI names for Campaign system table connections.
*
A connection to the database holding the Marketing Platform system tables. Use UnicaPlatformDS as the JNDI name.
UnicaPlatformDS is the required JNDI name.
If you are deploying Campaign in the same JVM as your Marketing Platform deployment, you have probably already set up this connection.
For more information about creating JDBC connections in your web application server, see the WebLogic or WebSphere® documentation.
*
If you are using WebLogic to configure a data source 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. For more information, see your WebLogic documentation.
2.
Record all JNDI names in theIBM Campaign database information checklist.
Information for creating JDBC connections
Copyright IBM Corporation 2015. All Rights Reserved.