Prerequisites

Before you install or upgrade any Unica Journey product, you must ensure that your computer complies with all of the prerequisite software and hardware.

System requirements

For information about system requirements, see the Recommended Software Environments and Minimum System Requirements guide.

Network domain requirements

The Unica products that are installed as a suite must be installed on the same network domain to comply with the browser restrictions that are designed to limit the security risks that can occur with cross-site scripting. Note: Unica Journey and Unica Link installation must be done with domain name specified for the application URLs.

JVM requirements

Unica applications within a suite must be deployed on a dedicated Java™ virtual machine (JVM). Unica products customize the JVM that is used by the web application server.

Knowledge requirements

To install Unica products, you must have a thorough knowledge of the environment in which the products are installed. This knowledge includes knowledge about operating systems, databases, Kafka, and web application servers.

Internet browser settings

Make sure that your internet browser complies with the following settings:
  • The browser must not cache web pages.
  • The browser must not block pop-up windows.

Access permissions

Verify that you have the following network permissions to complete the installation tasks:
  • Administration access for all necessary databases Note: Administrator must have CREATE, SELECT, INSERT, UPDATE, DELETE, and DROP rights for both tables and views.
  • Read and write access to the relevant directory and sub-directories for the operating system account that you use to run the web application server and Unica components.
  • Write permission for all files that you must edit.
  • Write permission for all directories where you must save a file, such as the installation directory and backup directory if you are upgrading.
  • Appropriate read, write, and execute permissions to run the installer.

Verify that you have the administrative password for your web application server. For UNIX, all installer files for products must have full permissions, for example, rwxr-xr-x.

The following additional permissions are necessary for UNIX:
  • The user account that installs Unica Journey and Unica Platform must be a member of the same group as the Unica Journey users. This user account must have a valid home directory and have write permissions for that directory.
  • All installer files for HCL Unica products must have full permissions, for example, rwxr-xrx.

Points to consider before you install Unica Journey

For Unica Journey installation you are required to consider the following points.

JAVA_HOME environment variable

If a JAVA_HOME environment variable is defined on the computer where you install a Unica product, verify that the variable points to a supported version of JRE. For information about system requirements, see the Recommended Software Environments and Minimum System Requirements guide.

If the JAVA_HOME environment variable points to an incorrect JRE, you must clear the JAVA_HOME variable before you run the Unica installers.

You can clear the JAVA_HOME environment variable by using one of the following methods:
  • Windows: In a command window, enter set JAVA_HOME= (leave empty) and press Enter.
  • UNIX: In the terminal, enter export JAVA_HOME= (leave empty) and press Enter.

You can clear the JAVA_HOME environment variable by running the following command in the terminal:

export JAVA_HOME= (leave empty)

The Unica installer installs a JRE in the top-level directory for the Unica installation. Individual Unica application installers do not install a JRE. Instead, they point to the location of the JRE that is installed by the Unica installer. You can reset the environment variable after all installations are complete.

For more information about the supported JRE, see the Recommended Software Environments and Minimum System Requirements guide.

Unica Platform requirements

User must install support base Unica Platform Version before installing and upgrading Journey. For each group of products that work together, you must install or upgrade Unica Platform only once. Each product installer checks whether the required products are installed. If your product or version is not registered with Unica Platform, a message prompts you to install or upgrade Unica Platform before you proceed with your installation.

Unica Platform must be deployed and running before you can set any properties on the Settings > Configuration page.

Platform and Journey can be installed on different servers. In such case, when Platform is installed on a different server then make sure that Journey application should have access to Platform URL. Journey host should be able to communicate with Platform host through the unica application port.

Database pre-requisites

User need to provide Journey System DB privileges to Reports DB user and vice versa for the performance tab to work efficiently. For Journey installation we recommend to use the separate schema for Journey system tables and Journey report tables.

For MariaDB use the following commands:

grant all privileges on {Journey_SystemDB}.* to '{Journey_Reports_User}'@'%' identified by '{Journey_Reports_User_Password}';

GRANT ALL ON {Journey_SystemDB}.* TO '{Journey_Reports_User}'@'%';

grant all privileges on {Journey_ReportsDB}.* to '{Journey_SystemDB_User}'@'%' identified by '{Journey_SystemDB_User_Password}';

GRANT ALL ON {Journey_ReportsDB}.* TO '{Journey_SystemDB_User}'@'%';

For Oracle

For oracle database create a system user account and a report user for creating Report schema. The system user account must have the following rights:
  • CREATE TABLES
  • CREATE VIEWS (for reporting)
  • CREATE SEQUENCE (Oracle only)
  • CREATE INDICES
  • ALTER TABLE
  • INSERT
  • UPDATE
  • DELETE
Note: Report user also have the above mentioned rights. In addition, report user have to grant permission to system user for accessing the Report schema table. Run the following command

GRANT ALL PRIVILEGES TO (SYSTEM_SCHEMA_USER_NAME)

For DB2

Perform the following setup before starting the installer:
  1. DB2 Server setting

    Run db2start

    Run db2set DB2_COMPATIBILITY_VECTOR=ORA

    Run db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES

    Run db2stop

    Run db2start

  2. Create two Schema/user in DB2
    1. journeydb
    2. reportdb
  3. Grant below command to Journey system schema user DB and Journey Report DB user by DB2 system user

    GRANT
    1. GRANT

      DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM ON DATABASE TO USER reportdb

    2. GRANT

      GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM ON DATABASE TO USER <Journey Report schema user DB>

Distributed Environment for Journey:

Journey engine files location needs to be shared on Journey engine and Web machine. If Journey engine is installed on multiple machines, then this file directory needs to be shared/ mounted on the same path across all machines.