Reports
- Unica Insights Reports Installation and Configuration Guide
  - Overview
  - Plan your Unica Insights reports installation
  - Install and configure Unica Insights reports
  - Upgrade Unica Insights reports
  - Configuring a user with the Reports System role
  - Creating JDBC data sources
  - Loading templates for the Reports SQL Generator
    The HCL Unica Insights reports use reporting schemas containing SQL scripts. These SQL scripts load template SQL select statements into the uar_common_sql table. The Reports SQL Generator uses the templates when it generates SQL scripts to create reporting views and tables.
  - SQL scripts by data source
  - Creating and populating reporting tables for Unica Campaign and Unica Deliver
  - Copy the Campaign and Deliver reports folder in Unica Insights directory
    Campaign installer places report design folders or files under Campaign installation directory.
  - Creating views or materialized views for Unica Campaign and Unica Deliver only:
  - Copy the Plan report folder in Unica Insights directory
  - Copy the Collaborate report folder in Unica Insights directory
  - Creating views or materialized views for Unica Interact only
  - Copy the Interact reports folder in Unica Insights directory
  - Creating and populating reporting tables
  - Setting up data synchronization
  - For Unica Deliver only: Stored procedures for delta processing
    Unica Deliver reports require staging tables that are associated with the Unica Deliver system tables. The system tables are part of the Unica Campaign schema. You must periodically run stored procedures to process message response data for use in Unica Deliver reports.
  - Update data source in Unica Insights report design files using Unica Insights utility
  - For Unica Deliver only: How to schedule and run stored procedures
    Unica Deliver reports use the data that is contained in staging tables, which are populated by stored procedures. The stored procedures perform a delta refresh operation. Run the stored procedures at least once per day. If you run the procedures more frequently, the delta refresh method prevents multiple concurrent runs.
  - How to configure Unica Insights to use HCL Unica authentication
  - Reporting schemas
    You must create reporting views to implement reporting for Unica Campaign, Unica Interact, and Unica Deliver. Reports can extract reportable data in the reporting views. The report packages for Unica Campaign, Unica Interact, and Unica Deliver include reporting schemas that the Reporting SQL Generator uses to produce SQL scripts that create reporting views.
  - Campaign reports and reporting schemas
  - Interact reports and reporting schemas
    The Interact Report Package reports are supported by HCL reporting schemas. You can customize the schemas to specify time periods, configure audience levels, and create extra performance reporting schemas.
  - Format of the Unica Insights Reports
  - Integrate new custom reports in Unica
    Unica Insights enables you to integrate newly created custom reports with Unica for Campaign, Deliver, Plan, and Interact products.
  - Unica Insights Reports Customization
    You can create new reports, and modify and customize existing Unica Insights reports.
  - Customization of existing Unica Insights Reports for Campaign
  - Customization of existing Unica Insights Reports for Interact
  - Known issues
    The following is the list of Known Issues in Unica Insights Reports
- Cognos Reports Installation and Configuration Guide

Creating JDBC data sources

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

The HCL Unica Reports SQL Generator tool must be able to connect to the HCL 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 Product installation 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
Applications	Default JNDI name
Unica Campaign and Unica Deliver	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`
Unica Collaborate	campaignPartition1DS

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.