Creating JDBC data sources

You must configure a JDBC data source for every Unica application for which you want to enable reporting.

About this task

The Unica Reports SQL Generator tool must be able to connect to the Unica application databases to generate SQL scripts that create reporting tables. The Reports SQL Generator can generate SQL scripts that create views or materialized views without access to the application databases. However, the SQL generator cannot validate the SQL code without a data source connection.

If you need more help with this task, see the application documentation.

To create the JDBC data source, complete the following steps.


To configure JDBC data sources, use the default JNDI name that is listed in the following table.
Note: If you do not use the default JNDI names, make a note of the names that you use. You must specify the correct name of the data source when you run the SQL Generator tool.
Table 1. Default JNDI names

This two-columned table provides information about the HCL applications in one column, and the default JNDI name in the second column.

HCL application Default JNDI name
Unica Campaign campaignPartition1DS

If there are multiple partitions, create a data source for each partition.

Unica Interact
  • For the design-time database: campaignPartition1DS
  • For the runtime database: InteractRTDS
  • For the learning tables: InteractLearningDS