Configuration if Using Tomcat to Host a Java Action Processor

The following are configuration functions you must perform if you are using Tomcat to host a Java Action Processor:

• Modify the apConfig.xml file if Using RMI
• Update the Java library path
• Add security filter to enable secure HTTP header
• Start Tomcat to start the Action Processor

These are described in the following sections.

Modify the apConfig.xml File if Using RMI

This is required only if you are using RMI.

When RMI is selected during installation, the installer includes two java.naming.factory.initial entries in the apConfig.xml file by default, as follows:

<JNDIEnv>

   <Name>java.naming.factory.initial</Name>

   <Value>com.sun.jndi.rmi.registry.RegistryContextFactory</Value>

</JNDIEnv>

<JNDIEnv>

   <Name>java.naming.factory.initial</Name>

   <Value>com.sun.jndi.cosnaming.CNCtxFactory</Value>

</JNDIEnv>

You need to remove one of these entries.

— The first entry (com.sun.jndi.rmi.registry.RegistryContextFactory) is the correct entry if you are using JRMP.
— The second entry (com.sun.jndi.cosnaming.CNCtxFactory) is the correct entry if you are using IIOP.

Remove the entry that does not apply to the protocol you are using.

The default location of the apConfig.xml file is:

   TomcatInstallDir\webapps\TIBCOAcrProc\

Update the Java Library Path

Update the Java library path so that it points to the TIBCO iProcess Server Objects (Java) JAR file.

The following subsections describe how to do this, depending on whether you are installing on Windows or UNIX.

Note: You need to perform the steps in this section only if you are using a version of Tomcat other than the one that is embedded in, and installed with, the iProcess Engine. If you are using the embedded Tomcat, the Java library path is updated when you run smserv.bat (Windows) or smstart (UNIX) to start the embedded Tomcat. If you are using a version of Tomcat other than the embedded one, you must explicitly update the Java library path as described in this section.

Windows Systems

To update the Java library path in Windows:

1. Start the Tomcat monitoring/configuration program by executing one of the following: 
   TomcatDir\bin\tomcat8w.exe   [Tomcat 8.x] or 
   TomcatDir\bin\tomcat9w.exe   [Tomcat 9.x]

The following dialog is displayed:

2. Click the Java tab.
3. In the Java Options section, ensure the following line is included in the entries. If it is not already included, add it after the existing entries. 
   -Djava.library.path=TomcatDir\lib   [Tomcat 8.x and 9.x]

where TomcatDir is the directory in which Tomcat is installed.

The Java Options section should now appear similar to the following:

4. Click OK to save the changes and close the Tomcat monitoring program.

UNIX Systems

To check the Java library path on UNIX systems:

  1. Open the following file with an editor:

       TomcatDir/bin/catalina.sh

  2. Locate “RUNJAVA” in the catalina.sh file and ensure the following line is included:

    -Djava.library.path=TomcatDir/lib \  [Tomcat 8.x and 9.x]

    where TomcatDir in the directory in which Tomcat is installed.

    For example:

    "$_RUNJAVA" $JAVA_OPTS $CATALINA_OPTS \ 
        -Djava.library.path=/tomcat/lib \
        -Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH" \
        -Dcatalina.base="$CATALINA_BASE" \
        -Dcatalina.home="$CATALINA_HOME" \
        -Djava.io.tmpdir="$CATALINA_TMPDIR" \

  3. Save and close the catalina.sh file.