Deploying Unica Interact

You must deploy the Unica Interact runtime environment for every instance of the runtime server that you install. The Interact design time environment is deployed automatically with the Campaign EAR or WAR file.

You must know how to work with your web application server. Consult your web application server documentation for details.

HTTP proxy support in API and the OMO gateway

  • When triggered messages are configured to use a HTTP connection, a HTTP proxy can be configured optionally with authentication between Interact and the endpoint.
  • When the client library (interact_client.jar) is used to connect the client to Interact run time servers, an HTTP proxy can be configured optionally with authentication between the client application and Interact runtime.

Deploying the design time environment

After you install Unica Interact, the design time environment is deployed automatically when you deploy Unica Campaign. After you deploy the Campaign.war file, configuration procedures automatically enable the Unica Interact design time environment in Campaign. The Campaign.war file is in the Campaign installation directory.

Deploying the runtime environment

You must deploy the Unica Interact runtime environment by deploying the InteractRT.war file for every instance of the runtime server that you install or upgrade. For example, if six instances of a runtime server exist, you must install and deploy the Unica Interact runtime environment six times. You can deploy the runtime environment on the same server as the design time environment, or you can deploy the Unica Interact runtime environment on a separate server. The InteractRT.war is in the Unica Interact installation directory.

Note: When you deploy the Unica Interact runtime environment, the context root must be set to /interact. Do not use any other value for the context root, or navigation to the runtime environment, and within Interact runtime links and pages, do not operate correctly.
Note: If Unica Interact is upgraded it is required to set the INTERACT_HOME environment variable pointing to the Unica Interact installation directory to generate interact.log file. Release 11.1 onwards, the log4j is changed to 'log4j2'. You will need to copy any custom entries from the 'interact_log4j.peoperties' file of base setup to the 11.1 target setup in the 'interact_log4j2.xml'.
Note: In case of deployment of Tomcat, include the following parameters in the instance_name/conf/server.xml file.

maxHttpHeaderSize="209715200"

maxPostSize="-1"