Home
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 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
B. Configure the Hive ODBC Driver
This is the second step to integrate Unica Campaign with Hive-based Apache Hadoop data sources. You must configure the driver that you installed (either the DataDirect Hive ODBC Driver from Progress Software or the Cloudera Hive ODBC driver from Cloudera, Inc.).
Configuring the Hortonworks Hive ODBC driver
If you are using the Hortonworks Hive ODBC driver to integrate Unica Campaign with a big data source, you must configure the driver after installing it.

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 MariaDB 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 datasources for Unica Campaign
    Follow these guidelines to use a Vertica database as a data source 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
    - Requirements and restrictions for Hive-based Hadoop data sources
      The following requirements and restrictions apply to using Hive-based Hadoop data sources with Unica Campaign.
    - Overview of the Unica Campaign integration with Hadoop
      Integrating Unica Campaign with Hadoop data sources demands extra software that is not part of the standard Unica Campaign installation requirement. You must be familiar with the terminology and structure of the integration and be able to access various resources that are available to support the integration.
    - A. Install a Hive ODBC driver
      This is the first step to integrate Unica Campaign with Hive-based Apache Hadoop data sources. You must install either the DataDirect Hive ODBC Driver from Progress Software or the Cloudera Hive ODBC driver from Cloudera, Inc.
    - B. Configure the Hive ODBC Driver
      This is the second step to integrate Unica Campaign with Hive-based Apache Hadoop data sources. You must configure the driver that you installed (either the DataDirect Hive ODBC Driver from Progress Software or the Cloudera Hive ODBC driver from Cloudera, Inc.).
      - Configuring the DataDirect Hive ODBC driver
        If you are using the DataDirect Hive ODBC driver to integrate Unica Campaign with a big data source, you must configure the driver after installing it.
      - Configuring the Cloudera ODBC driver
        If you are using the Cloudera ODBC driver to integrate Unica Campaign with a big data source, you must configure the driver after installing it.
      - Configuring the Hortonworks Hive ODBC driver
        If you are using the Hortonworks Hive ODBC driver to integrate Unica Campaign with a big data source, you must configure the driver after installing it.
    - C. Map existing HBase tables to Hive
      This is the third step to integrate Unica Campaign with Hive-based Apache Hadoop data sources. If you do not have existing tables that were created in Apache HBase, you can skip this step.
    - D. Import and configure the BigDataODBCHiveTemplate data source template in Unica Campaign
      This is the fourth step to integrate Unica Campaign with Hive-based Apache Hadoop data sources.
    - E. Configure SSH on the Unica Campaign listener server
      This is the fifth step to integrate Unica Campaign with Hive-based Apache Hadoop data sources.
    - F. Map the Hive datasource in Unica Campaign
      This is the sixth and final step to integrate Unica Campaign with Hive-based Apache Hadoop data sources.
  - 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 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 IBM eMessage system tables and register Unica Campaign, Unica Optimize, and IBM eMessage 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 eMessage
  Configure multiple partitions in IBM eMessage to isolate and secure data for different groups of IBM eMessage users. As each partition has its own set of configuration properties, you can customize IBM eMessage for each group of users.
- Unica 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.

Configuring the Hortonworks Hive ODBC driver

If you are using the Hortonworks Hive ODBC driver to integrate Unica Campaign with a big data source, you must configure the driver after installing it.

Before you begin

Complete the Hortonworks driver installation that is described in Installing the Hortonworks Hive ODBC driver.

Procedure

Modify the ODBC.ini file to specify the Hive server information, using the values shown in the following example. Be sure to customize the items in bold to match your own configuration.

The default location of odbc.ini file is: /usr/lib/hive/lib/native/hiveodbc/Setup/odbc.ini


[ODBC] [ODBC Data Sources] HWDS [HWDS] Description=Hortonworks Hive ODBC Driver (64-bit) DSN Driver=/usr/lib/hive/lib/native/Linux™-amd64-64/libhortonworkshiveodbc64.so HOST=<hostname or ip of Hive server on Hadoop Distribution machine> PORT=<port number of Hive server on Hadoop Distribution machine> Schema=<schema-name> ServiceDiscoveryMode=0 ZKNamespace= HiveServerType=2 AuthMech=2 ThriftTransport=1 UseNativeQuery=0 UID=hue KrbServiceName=<Hive Server 2 Kerberos service name> KrbRealm=<Hive Server 2 Kerberos realm> SSL=0 TwoWaySSL=0 ClientCert= ClientPrivateKey= ClientPrivateKeyPassword=

Enable the unixODBC manager and disable Generic ODBCInstLib in the hortonworks.hiveodbc.ini as follows.
The default location of hortonworks.hiveodbc.ini is /usr/lib/hive/lib/native/Linux-amd64-64/hortonworks.hiveodbc.ini.

Comment out the following line by adding a hash character (#) at the beginning: # ODBCInstLib=libiodbcinst.so

Un-comment the following line by removing the hash character (#) at the beginning: ODBCInstLib=/usr/local/unixODBC/lib/libodbcinst.so
Edit the Campaign/bin/setenv.sh as follows.
1. Ensure that your LD_LIBRARY_PATH includes the following path: /usr/local/unixODBC/lib
2. Set your ODBCINI variable to point to the correct INI file.
  For example:
  ODBCINI=/usr/lib/hive/lib/native/hiveodbc/Setup/odbc.ini
  
  export ODBCINII
  
  HORTONWORKSHIVEINI=/usr/lib/hive/lib/native/Linux-amd64-64/hortonworks.hiveodbc.ini
  
  export HORTONWORKSHIVEINI

What to do next

C. Map existing HBase tables to Hive

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.