Deploying Unica Contact Central

Prerequisites

Unica Contact Central requires JRE 1.8 or higher to work.

Note: Unica Contact Central does not support clustered environment.

ContactCentralDS JNDI resource for Contact Central database is required.

Setting Unica Contact Central and Unica Platform home JVM argument

Add the following JVM argument to the application server, where Unica Contact Central is required to be deployed.

- DCONTACTCENTRAL_HOME = path_where_contact_central_is_installed

- DUNICA_PLATFORM_HOME = platform_installation_home_directory_path

For example: CONTACTCENTRAL_HOME =/opt/Platform/ContactCentral

Point CONTACTCENTRAL_HOME to the directory, where Unica Contact Central is installed. It is installed within the ContactCentral directory under UNICA_PLATFORM_HOME.

Provide write permissions to the logs directory already created inside CONTACTCENTRAL_HOME.

Deployment procedure

You must follow a set of guidelines, when you deploy Unica Contact Central on your web application server When you ran the suite installer, you completed the following action:

  • You created the WAR file of Unica Contact Central (ContactCentral.war) inside UNICA_PLATFORM_HOME/ContactCentral directory. UNICA_PLATFORM_HOME refers to the Unica Platform installation location.
Note:
  • It is assumed that you possess information on how to work with your web application server. For more information, see the web application server documentation.
  • Contact Central deployment is not supported on WebLogic and JBoss.

Guidelines for deploying Unica Contact Central on WebSphere

You must follow a set of guidelines when you deploy Unica Contact Central onWebSphere. Ensure that the version of WebSphere meets the requirements that are described in the Recommended Software Environments and Minimum System Requirements document, including any required fix packs. Use the following guidelines when deploying Unica Contact Central on WebSphere:

  1. Set a custom property in WebSphere®.
    • Click Servers > Server Types > Websphere Application Server > <server_name> > Web Container Settings > Web Container
    • Under additional settings click on Custom Properties
    • On Custom Properties page, click New and enter com.ibm.ws.webcontainer.invokefilterscompatibility as the property name and true as the value.
    • Save the update and restart the server.
  2. Deploy the ContactCentral.war file as an enterprise application. When you deploy the ContactCentral.war file, ensure that the JDK source level is set to 18 for SDK 1.8:
    1. In the form, select the WAR file, select Show me all installation options and parameters so the Select Installation Options wizard runs.
    2. In step 3 of the Select Installation Options wizard, ensure that the JDK SourceLevel is set to 18 for SDK 1.8.
    3. In step 8 of the Select Installation Options wizard, select ContactCentralDS as the matching Target Resource. ContactCentralDS JNDI resource must be present for Contact Central. Guidelines for setting up ContactCentralDS remains same as setting up UnicaPlatformDS datasource for Platform. For more information on setting up UnicaPlatformDS datasource, see Unica Platform Installation Guide.
    4. In step 10 of the Select Installation Options wizard, the context root must be set to /ContactCentral.
  3. For your installation to support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters, add the following arguments to Generic JVMArguments at the server level.

    -Dfile.encoding=UTF-8

    -Dclient.encoding.override=UTF-8

    Note: Navigation tip: Select Servers > Application Servers > Java and ProcessManagement > Process Definition > Java Virtual Machine > Generic JVM Arguments.See the WebSphere documentation for additional details.
  4. In the Applications > Enterprise Applications section of the server, select the WAR filethat you deployed, then
    • For Class loader order, select Classes loaded with local class loader first (parentlast).
    • For WAR class loader policy, select Single class loader for application.
  5. Start your deployment. If your instance of WebSphere is configured to use a JVMversion 1.8 or higher, complete the following steps to work around an issue with thetime zone database.
    1. Stop WebSphere.
    2. Download the Time Zone Update Utility for Java (JTZU).
    3. Follow the steps provided by the IBM (JTZU) to update the time zone data in yourJVM.
    4. Restart WebSphere.
  6. In Websphere Enterprise Applications, select your Application > Manage Modules >Your Application > Class Loader Order > Classes loaded with local class loader first(parent last).
  7. The recommended minimum heap size for the basic functioning of the application is 512 MB and the recommended maximum heap size is 1024 MB. Complete the following tasks to specify the heap size.
    1. In WebSphere Enterprise Applications, select Servers > WebSphere application servers > server1 > Server Infrastructure > Java and Process Management >Process definition > Java Virtual Machine.
    2. Set the initial heap size to 512m.
    3. Set the maximum heap size to 1024m.
    Note: See the WebSphere documentation for more information about sizing.

For DB2, set progressiveStreaming = 2 in WebSphere console at following path: JDBC>Data sources > ContactCentralDS > Custom properties.

Guidelines for deploying Unica Contact Central on Apache Tomcat®

You must follow a set of guidelines when you deploy Unica Contact Central onApache Tomcat. Ensure that the version of Apache Tomcat meets the requirementsthat are described in the Recommended Software Environments and Minimum SystemRequirements document. Use the following guidelines when you deploy Unica ContentIntegration on Apache Tomcat.
  1. Deploy the HCL ContactCentral.war file as an enterprise application on TomcatApache server. Complete the following tasks if your installation must support non-ASCIIcharacters, for example for Portuguese or for locales that require multi-byte characters.
  2. Edit the setenv.sh file for the respective product instances script in the bindirectory under your tomcat instances directory to add -Dfile.encoding=UTF-8Dclient.encoding.override=UTF-8.
  3. You must add Unica Platform and Contact Central data source in ContactCentral.xml along with the path of ContactCentral.war to the ContactCentral Tomcat instance. For example

    <Context docBase="<Platform_Install_Path>\platform\ContactCentral\ContactCental.war">

    <Resource name="UnicaPlatformDS" factory="com.unica.manager.tomcat.utils.TomcatDSFactory" auth="Application" type="javax.sql.DataSource"

    maxActive="30" maxIdle="10" maxWait="10000" username="<db user for Platform schema>" password="<db password>" driverClassName= "<db specific class name>" url="<db specific jdbc url>"/>

    <Resource name="ContactCentralDS" factory="com.unica.manager.tomcat.utils.TomcatDSFactory" auth="Application" type="javax.sql.DataSource"

    maxActive="30" maxIdle="10" maxWait="10000"

    username="<db user for Contact central schema>" password="<db password>" driverClassName=

    "<db specific class name>" url="<db specific jdbc url>

    </Context>"/>

  4. Restart Tomcat.
Note: This is the sample xml configuration.

Unica Contact Central | User Role Creation

The procedure included in this section is not required for the following scenarios:

It is a fresh installation. The installation process creates this role under default partition(partition1).

It is an upgrade and only one partition exists in the current system.

In case, it is an upgrade and system contains more than one partition, you must execute the following command manually for each partition, except partition1. The command exists under <PLATFORM_HOME>\tools\bin directory inside your Platform installation directory. This creates a Contact Central user role under each partition.

On Windows

populateDb.bat -n ContactCentral -p <partition_name>

On Unix

populateDb.sh -n ContactCentral -p <partition_name>