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.
Complete the following steps to specify the JDBC provider:
1.
2.
Go to Resources > JDBC > JDBC Providers .
3.
Click New to open the Create new JDBC provider window.
4.
In the Database type field, select one of the following database types:
*
DB2®
*
*
5.
In the Provider type field, select a type 4 JDBC driver that is appropriate for your database type.
6.
In the Implementation type field, select Connection pool data source.
7.
Click Next and enter the required information.
8.
Click Next to view the summary.
9.
Click Finish to configure the JDBC provider.
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.
*
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.
*
*
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.
Record all JNDI names in theCampaign installation worksheet
Information for creating JDBC connections