Installing Collaborate

You must run the HCL Unica installer to start the installation of Collaborate. The HCL Unica installer starts the Collaborate installer during the installation process. Make sure that the HCL Unica installer and the product installer are saved at the same location.

Note: Collaborate 12.1.0.0 installation is supported by HCL_Unica_Installer_12.1.0.3. Previous versions of HCL Unica Installers will not detect Collaborate binaries for installation.
Each time that you run the HCL Unica suite installer, you must first enter database connection information for the Platform system tables. When the Collaborate installer starts, you must enter the required information for Collaborate.
Note: The HCL Unica installer requires information about Platform.

After installing Collaborate, you can create an EAR file for your product, and you can install the reports package for your product. Creating the EAR file and installing the reports package are not mandatory actions.

Important: Before you install Collaborate, make sure that the available temporary space on the computer where you install Collaborate is more than three times the size of the Collaborate installer.

Collaborate installation on MariaDB

If you want to install Collaborate on MariaDB, then you can directly install Collaborate 12.1.0.4 without installing Collaborate 12.1.0. Installation of Collaborate 12.1.0.4 on MariaDB will act as a clean installation for Collaborate, creating a clean system database. There are two options for Collaborate database during the installation.
  • Automatic Database setup: This will create clean system database as part of installation.
  • Manual Database setup: Installation will complete without creating any database and user has to create database using udmdbsetup utility after the installation is complete.
Note:

If Collaborate installation is on MariadB system database, after installation is complete, you are required to execute the following SQL file on Campaign database.

Campaign_Home\ddl\clb_systab_mariadb.sql ( For non-unicode system DB )

Campaign_Home\ddl\unicode\clb_systab_mariadb.sql ( For unicode system DB )

Installation files

The installation files are named according to the version of the product and the operating system on which they must be installed, except UNIX™. For UNIX, different installation files exist for the X Window System mode and the console mode.

The following table displays examples of the installation files that are named according to the product version and the operating system:
Table 1. Installation files

This two-columned table provides the name of the operating systems in one column, and the name of the installation files for the operating system in the second column.

Operating system Installation file
Windows™: GUI and console mode

Product_N.N.N.N_win64.exe, where Product is the name of your product, N.N.N.N is the version number of your product, and Windows 64-bit is the operating system on which the file must be installed.

UNIX: X Window System mode

Product_N.N.N.N_linux.bin, where Product is the name of your product, and N.N.N.N is the version number of your product.

Table 2. Installation files

This two-columned table provides the name of the operating systems in one column, and the name of the installation files for the operating system in the second column.

Operating system Installation file
UNIX: X Window System and Console mode Product_N.N.N.N_aix.bin, where Product is the name of your product, N.N.N.N is the version number of your product.