Prerequisites

Prerequisites are different for Campaign and Journey.

Prerequisites for Campaign

  1. As the Unica Platform user, you should:
    • Know the host name of the listener host

      For the serverHost parameter under ‘Settings’ enter the hostname of unicaACListener (Affinium|Campaign|unicaACListener) instead of the default "localhost". For example: serverHost = zebra658.nonprod.hclpnp.com.

    • To log on to Unica Director for a particular environment, user must know the Unica platform credentials.
  2. Unica Director Agent must always be running.
  3. Applicable only to Windows OS: On the Unica Director - Agent system (on the computer where the Unica Campaign Listener is installed), ensure that the following performance counters are available.
    • Processor Time
    • Working Set
    These counters help the HCL Unica Director - Agent application to gather the statistics on the Unica Campaign listener or server processes for memory and CPU utilization.
    Note: If the performance counters are not available, open the command prompt as an administrator on the target server and enter the following commands to rebuild the performance counters. Otherwise you will not be able to see the data in the System Usage Graph on the Windows Operating System.
    For 32 bit machines:
    • cd %windir%\system32\
    • lodctr /R
    For 64 bit machines:
    • cd C:\Windows\SysWOW64\
    • lodctr /R
  4. For Unica Campaign application, the flowchart timeline to receive and dispatch execution events to and from Unica Director, Active Message Queue (MQ) should be available. Flowchart execution events (flowchart execution started, stopped, paused, completed, failed) are communicated to Unica Director using Active MQ. Flowchart timeline may show incorrect statistics if Active MQ is unavailable.
  5. Unica Platform users who will be using Unica Director, should be a Unica Campaign Admin user, so that they are can see all the Unica Campaign objects. This user should additionally have all the permissions for executing the following Unica Campaign Utilities:
    • Access monitoring area
    • Run svradm Command line tool
    • Terminate Unica Campaign listener
    • Run sesutil Command line tool
    • Perform cleanup operations.
  6. From Platform users page, assign all the Unica Campaign system and user data sources to the Unica Platform users who will be using Unica Director.

Prerequisites for Journey

To work Journey Datasource health check properly following datasource jndi-names are mandatory. User can define properties in <JOURNEY_HOME>/Web/application.properties file.

Web server type: Websphere, Tomcat

journey.datasource.jndi-name=JourneyDS

journey.report.datasource.jndi-name=JourneyReportDS

Web server type: JBOSS

journey.datasource.jndi-name=java:jboss/JourneyDS

journey.report.datasource.jndi-name=java:jboss/JourneyReportDS

OR

journey.datasource.jndi-name=java:/JourneyDS

journey.report.datasource.jndi-name=java:/JourneyReportDS

Note: Director does not support login with LDAP users. Also, it does not support integration with any authentication provider tools such as SiteMinder, IBM Security Access Manager etc.