Creating the JDBC connections in the web application server

The Marketing Operations web application uses JDBC connections to communicate with the system table database and with the HCL® Marketing Platform system table database.

About this task

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

You can allow the installer to create this data source when you install Marketing Operations. To enable automatic data source creation during installation, on the Datasource Creation panel, select the Create Marketing Operations 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.

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

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

Important: For the connection to the database holding the Marketing Operations 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 Marketing Platform system tables, you must use UnicaPlatformDS as the JNDI name. This is the required JNDI name. If you are deploying Marketing Operations and Marketing Platform in the same JVM, this connection should already exist.

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