Deploying Unica Plan on Apache Tomcat®

You must follow a set of guidelines when you deploy Unica Plan on Apache Tomcat.

Set removeAbandoned=true and removeAbandonedTimeout=300 (5 minutes) for plands datasource configuration in <catalina home>/conf/Catalina/localhost/plan.xml file within the section that starts with the parameter Resource name="plands".

For example:
<Resource name="plands" auth="Application" type="javax.sql.DataSource" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" maxTotal="100" maxIdle="30" maxWaitMillis ="10000" username="abc" password="abc" driverClassName="org.mariadb.jdbc.Driver" removeAbandoned="true" removeAbandonedTimeout="300" url="jdbc:mysql://lp2-ap-51728467.prod.hclpnp.com:3306/pln121" />
Note: If the application executes SQL queries that requires more than 300 seconds of execution time, change the value of removeAbandonedTimeout.

Make sure that the version of Apache Tomcat meets the requirements that are described in the Unica Recommended Software Environments and Minimum System Requirements document. Use the following guidelines when you deploy Unica Plan on Apache Tomcat:

From the bin directory under your Apache Tomcat installation directory, locate or create the setenv.sh or setenv.bat script appropriate for your operating system in a text editor, and add or modify JAVA_OPTIONS property, and add the following entries. Use a space to separate entries.

  • -Dplan.home=<Plan_Home>

    Where <Plan_Home> is the path to the directory where you installed Unica Plan.

  • -Dfile.encoding=UTF-8
  1. Deploy the HCL plan.war file as an enterprise application on Tomcat Apache server.
    Note: Deployment of HCL EAR file is not supported in Tomcat.
  2. Complete the following tasks if your installation must support non-ASCII characters, for example for Portuguese or for locales that require multi-byte characters:
    1. Edit the setenv.sh file for the respective product instances script in the bin directory under your tomcat instances directory to add -Dfile.encoding=UTF-8 -Dclient.encoding.override=UTF-8 to JAVA_VENDOR.
    2. Restart Tomcat.
  3. If deploying in a production environment, you can add JVM heap setting for that tomcat instance in app-one/bin/setenv.sh file respectively for all the instances.
Note: Add prefix "java:/comp/env/" when defining datasource/JNDI.

After upgrading Plan on Apache Tomcat, you must encrypt the password again from the location <Installation_Location>/platform/tools/bin and manually make the changes in XMLs.

You can use the encryptTomcatDBPasswords utility and encrypt the database password which is used by the Tomcat Application server internally. It is used to encrypt database passwords used in Campaign.xml, unica.xml, and Plan.xml. The utility prints the encrypted password in the command line.

The command to run the utility is: encryptTomcatDBPasswords -d databasePassword.