Welcome
Installation Guides
Installation Guide
An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
Preparing data sources for Unica Campaign
The Unica Optimize runtime environment uses data sources to store user and interaction data.
Preparing Cloudera BigData instance using Kerberos authentication
Seamless Kerberos connection on Windows

Unica Optimize
Release Notes
System Requirements
Installation Guides
- Installation Guide
  An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
  - Installation overview
    An installation of HCL Unica products is complete when you install, configure, and deploy the HCL Unica products . The Installation Guide provides detailed information about installing, configuring, and deploying the products.
  - Planning the Unica Campaign Installation
    When you plan your Unica Campaign and Unica Optimize installation, you must ensure that you have set up your system correctly, and that you have configured your environment to deal with any failures.
  - Preparing data sources for Unica Campaign
    The Unica Optimize runtime environment uses data sources to store user and interaction data.
    - Prerequisites of Oracle 12c or Oracle 19.x database before Unica Campaign installation
    - Creating database or schema for Unica Campaign system tables
      The Unica Campaign system tables hold application data. The empty database that you set up for the system tables can have any name. To ensure that the system tables will be mapped automatically, the ODBC name for that database must be UA_SYSTEM_TABLES. If you have multiple partitions, create data sources for each partition where you want to enable Unica Campaign.
    - Creating ODBC or native connections
      Create ODBC or native connections so that the Unica Campaign server can access the Unica Campaign database. Create ODBC or native connections on the computer where you installed the Unica Campaign server.
    - Configuring the web application server for your JDBC driver
    - Creating JDBC connections in web application server
      Create JDBC connections on each of the web application servers where Unica Campaign is deployed. Unica Campaign uses the JDBC connections to access the required databases.
    - Preparing datasource for Unica Campaign using ODBC Connection
    - Preparing MariaDB datasource for Unica Campaign
    - Preparing Postgres datasource for Unica Campaign
    - Preparing DB2 on z/OS user datasource for Unica Campaign
      Follow these guidelines to use a DB2® database on z/OS® as a data source for Unica Campaign.
    - Preparing Vertica database as user database datasource for Unica Campaign
    - Preparing Amazon Redshift user data sources for Unica Campaign
      Follow these guidelines to use Amazon Redshift as a data source for Unica Campaign.
    - Preparing Apache Hadoop Hive user data sources for Unica Campaign
      Follow the steps below to enable Hive-based Apache Hadoop data sources to be used in Unica Campaign
    - Preparing Cloudera Hadoop Impala based user data sources for Unica Campaign
      Follow the steps below to enable Impala based Cloudera Hadoop data sources to be used in Unica Campaign
    - Preparing Cloudera BigData instance using Kerberos authentication
      - Installing and configuring MIT Kerberos for Windows
      - Downloading and installing Kerberos Packages for Linux
        Enable Kerberos authentication on Cloudera Bigdata for Linux Server.
      - Seamless Kerberos connection on Windows
      - Seamless Kerberos connection on Linux
      - Configuring the Impala-based Cloudera data sources using Kerberos
      - Configuring the Impala-based Cloudera data sources using Kerberos on Linux
      - Troubleshooting
    - Preparing Actian Vector user data source for Campaign
    - Preparing DataBricks database as user database datasource for Unica Campaign
    - Preparing AWS Athena database as user database datasource for Unica Campaign
      Unica Campaign supports Athena as User databases. For AIX it is not supported.
    - Preparing Snowflake database as user database datasource for Unica Campaign
      Unica Campaign supports Snowflake as User databases. For AIX and SUSE we do not support Snowflake as a User Database.
  - Configuring MariaDB if used as system database
    If you are installing Unica and using MariaDB as the System database, ensure that the MariaDB configuration and database settings are updated to use the following default character set and collation:
  - Installing Unica Campaign and Unica Optimize
    You must run the Unica installer to start the installation of Unica Campaign and Unica Optimize. The Unica installer starts the product installer during the installation process. Make sure that the Unica installer and the product installer are saved at the same location.
  - Configuring Unica Campaign and Unica Optimize before deployment
    Before you deploy, create and populate the Unica Campaign , Unica Optimize, and Unica Deliver system tables and register Unica Campaign, Unica Optimize, and Unica Deliver manually.
  - Deploying the Unica Campaign web application
    You can deploy the Unica Campaign web application by using an EAR file or you can deploy the individual WAR files.
  - Configuring Unica Campaign and Unica Optimize after deployment
    After you deploy Unica Campaign, you must verify that the Unica Campaign listener is running, set up the Unica Campaign system user, set Unica Campaign configuration properties, and verify the Unica Campaign installation.
  - Configuring multiple partitions for Unica Campaign
    In the Unica family of products, partitions provide a way to secure the data that is associated with different groups of users. When you configure Unica Campaign or a related Unica application to operate with multiple partitions, users can see each partition as a separate instance of the application. There is no indication that other partitions exist on the same computer.
  - Configuring multiple partitions for Unica Optimize
    In the Unica family of products, partitions provide a way to secure the data that is associated with different groups of users. When you configure Unica Campaign or a related Unica application to operate with multiple partitions, users can see each partition as a separate instance of the application. There is no indication that other partitions exist on the same computer.
  - Configuring multiple partitions in Deliver
    Configure multiple partitions in Unica Deliver to isolate and secure data for different groups of Unica Deliver users. As each partition has its own set of configuration properties, you can customize Unica Deliver for each group of users.
  - Unica Platform utilities
    This section provides an overview of the Unica Platform utilities, including some details that apply to all the utilities and which are not included in the individual utility descriptions.
  - Uninstalling Unica Campaign and Unica Optimize
    Run the Unica Campaign and Unica Optimize uninstaller to uninstall Unica Campaign and Unica Optimize. When you run the uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.
  - Unica Campaign web application clustering
    You can configure the Unica Campaign web application (J2EE application) in a cluster by completing additional tasks during the Unica Campaign installation.
  - Installing a clustered listener environment
    Follow these instructions if you want to install a clustered listener configuration. A listener cluster is a set of two or more listeners that act as a unit to provide load balancing and high availability. Unica Campaign listener clusters are Active-Active; meaning each node serves requests using the load-balanced approach. Each Unica Campaign listener provides an interface between front-end clients (such as the Unica Campaign web application) and back-end analytical server processes.
Upgrade Guide
User Guide
Unica Optimize provides documentation and help for users, administrators, and developers.
Troubleshooting and Tuning Guide
Unica Optimize is a web-based extension of Unica Campaign that allows you to determine the optimal contact strategy for each customer. You can optimize over time, looking across the proposed offers and channels across multiple marketing campaigns.
System Tables
The Unica Optimize system tables document is intended to help your company understand the Unica Optimize data model for integration purposes.
Licensing Guide
Glossary
Notices

Seamless Kerberos connection on Windows

About this task

You need to run unica_kerbKeyGenRenew.bat script to obtain the Ticket for the Kerberos principal. The purpose of this script is to run continuously and :

Renew the TGT before its renewable time.
Regenerate the token before expiry.

By default, it renews the ticket every 24 hours and regenerates a new ticket after 7 days. You can also override the default setting for regenerating and renewing the tickets by setting environment variables.
Prerequisite for running the Script

Requires MIT Kerberos to be installed and configured.
Keytab file is already present for the said principal.
The following environment variables are set:
1. TGT_EXPIRY_DAYS: number of days after which this TGT will expire, and can no longer be renewed (specify value in days)
2. TGT_RENEWAL_HOURS: number of hours within which this TGT needs to be renewed (specify value in hours)
3. KRB5CCNAME: path to the cache file
4. KEYTAB_FILE_PATH: path to keytab file for this principal
From command line run “Where kinit" command should point MIT Kerberos
For example: C:\Kerbores\Campaign\bin>where kinit
C:\Program Files\MIT\Kerberos\bin\kinit.exe
Copy the Keytab file to the Campaign System for the principal you want to authenticate.

Procedure to run the Script

Procedure

Make sure the prerequisites are satisfied.
Then run the following:
<campaign_home>/bin/unica_kerbKeyGenRenew.bat <principal>
For example: unica_kerbKeyGenRenew.bat impala/quickstart.cloudera@CLOUDERA
The script will start running, and do the following:
1. Generate the TGT.
2. Check every 1 minute for renewal and regeneration of the TGT.
3. Using the values in TGT_EXPIRY_DAYS and TGT_RENEWAL_HOURS, keep checking for renewal or expiry.
4. Before renewal time - renew the TGT.
  And before expiry time - regenerate the TGT.
Note:
1. TGT_RENEWAL HOURS AND TGT_EXPIRY_DAYS values needs to be same as Kerberos Server configuration. Please contact the Kerberos administrator to get the values.
2. By default Script sets 24 hours for TGT renewal and 7 days for TGT_EXPIRY.
Possible errors:

1. Usage

2. Principal is incorrect

3. Keytab file is not present for the Principal

4. One or more of the prerequisites is not set

5. Keytab file is not valid