Preparing for installation

Configure Single Sign-On and install an iFix for Connections 6.0 installations. Then, edit the installation properties file before running the installation program for HCL Connections Engagement Center.

Before you begin

Single Sign-On integration between HCL Connections applications must be configured. See Configuring Single Sign-On. Single Sign-On for the Windows desktop with Kerberos is also supported, but is optional.


  1. On the Deployment Manager where you will install Connections Engagement Center, log on as root (AIX, Linux) or the system administrator (Windows).
  2. If you're running HCL Connections 6.0, download and install iFix: HCL Connections: The ifix is not needed for Connections 5.5 environments.

    For information on installing an iFix, see Installing interim fixes in interactive mode.

  3. Create a directory to contain installation files; for example: /opt/software/icec-installer.
  4. Download the Connections Engagement Center installation package and extract it to the new directory.
  5. Open and edit the file to configure settings for your environment.
    1. Enter WebSphere Application Server environment names. Note that the profilePath isn't the full path, but just the part after wasRoot. For example: section for was detail

      Note that for Windows, the wasRoot and profilePath use backslashes. For example:
      #websphere root path
      #path to the Dmgr profile e.g. /profiles/Dmgr01
    2. Enter the name for the JDBC Provider if you are creating a JDBC Provider that is separate from the one used for Activities. By default, ICEC uses the Activities JDBC Provider. The following example shows the same userId and password used by the script to create an Oracle database. Credentials here must always match those in the database creation script. showing section for jdbc provider

    3. Enter the database details for your environment. For example: section showing database details such as name, driver, server name, and port number.

    4. Enter the name for the datasource and datastore helper. For example: section for datasource and datastore helper.

    5. Enter admin names, group names, path to ear file, app name, and context root. For example: section for adding admin names

      Note: The installer supports the following system encodings: codepage 850, 437, 65001. If the operating system is configured to use a different codepage, 932 for example, follow these instructions:
      1. Change the earPath in the file as follows:
      2. Move the icec-6.0.1.ear file to the installer directory. In the example above it would be icec-installer.
      Note: The path to the ear file on Windows uses forward slashes. For example:
      #path to ear file to be installed
    6. Save and close the file.