Installing Contact Optimization

You must run the HCL® Marketing Software installer to start the installation of Contact Optimization. The HCL Marketing Software installer starts the Contact Optimization installer during the installation process. Make sure that the HCL Marketing Software installer and the product installer are saved at the same location.

Each time that you run the HCL Marketing Software suite installer, you must first enter database connection information for the Marketing Platform system tables. When the Contact Optimization installer starts, you must enter the required information for Contact Optimization.
Note: The HCL Marketing Software installer requires information about Marketing Platform.

After installing Contact Optimization, 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.

After installing Opportunity Detect, you can create an EAR file if necessary.

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

For information about installing Contact Optimization on clustered environment, see "Cluster Configuration" in the IBM SPSS® Collaboration and Deployment Services (C&DS) Guide.

Note: Information about using web application clustering in HCL Campaign is provided in HCL Campaign web application clustering.

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.

Product_N.N.N.N_win.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.

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

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

UNIX: Console mode Product_N.N.N.N.bin, where Product is the name of your product, and N.N.N.N is the version number of your product. This file can be used for installation on all UNIX operating systems.
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 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.
UNIX: Console mode Product_N.N.N.N.bin, where Product is the name of your product, and N.N.N.N is the version number of your product. This file can be used for installation on all UNIX-based operating systems.