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 views or materialized views for Unica Interact only

You can use SQL scripts to create views or materialized views for Interact. The reports application uses views or materialized views to extract reportable data.

Before you create views or materialized views for Interact, verify that the language setting for the computer from where you run the lookup_create SQL script is enabled for UTF-8 encoding.

To create views or materialized views for Interact, complete the following steps.

Locate the SQL scripts that you generated and saved previously.
Use the database administration tools to run the appropriate script against the appropriate application database(s) for the report package that you are configuring.

Note: When you run a script that creates materialized views on a DB2 database, you may see the following error:

SQL20059W The materialized query
        table-name may not be used to optimize the processing of queries.

However, the materialized view is successfully created.

Under the Interact installation directory, in the tools subdirectory of report folder, find the uari_lookup_create_<db_type>.sql script for your database. For example, for SQL Server, script is available at <INTERACT_HOME>/Interact/reports/tools/uari_lookup_create_MSSQL.sql.
Run the uari_lookup_create script on the Interact design time database.
Locate the uari_lookup_populate.sql script under <INTERACT_HOME>/Interact/reports/tools path and run it on the Interact design time database.
Note: Ensure that the database tool that you have used commits the changes. For example, you may require to set the auto-commit option of the database to true.

Continue with Setting up data synchronization.

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.