Post-Installation Configuration

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 4 Post-Installation Configuration : Post-Installation Configuration

Post-Installation Configuration

The post-installation configuration tasks are divided into the following sections.

•

Configuration if using IIS to host the iProcess Client and using TIBCO Forms— see page 40

•

Configuration if using IIS to host a .NET Action Processor—see page 42

•

Configuration if using Tomcat to host a Java Action Processor— page 47

Use the appropriate section depending on which software has been installed and which web server will be used to host them.

If you are installing on a Web server other than IIS or Tomcat, there may be configuration functions required by that Web server. Refer to that server’s documentation.

Note that the iProcess Workspace (Browser) installation program unpacks the iProcess Client’s WAR file during the installation process. If you are using an Application Server that requires WAR files, you will need to manually repack them into a WAR file after the installation is completed. For more information, see Packing/Unpacking WAR Files.

If you are hosting the .NET Action Processor in IIS 8.5 or 10, and you want the Action Processor to run in a .NET Framework 4.0 Application Pool, you must open the web.config file for the Action Processor’s web site, and uncomment the following line:



This is required because .NET Framework 4.0 disables switching off validation of HTML input (that is, it causes the Validate=false setting in ActionProcessor.aspx to be disregarded).

Configuration if Using IIS to Host the iProcess Client and Using TIBCO Forms

If you are hosting the iProcess Client in IIS, and you are using TIBCO Forms in your application, you must ensure the following MIME types are added to the virtual directories for your iProcess Client and TIBCO Forms (WebDAV directory):

•

.json

•

.form

To add MIME Types to IIS:

1.

Access Administrative Tools / Internet Information Services (IIS) Manager.

2.

In the Internet Information Services (IIS) Manager window, either:

−

click on a virtual directory, either for the iProcess Client or TIBCO Forms (WebDAV directory), in the left pane. If you choose to add the required MIME types for individual virtual directories, you will need to perform this procedure twice; once for the iProcess Client virtual directory, and again for the TIBCO Forms virtual directory (WebDAV directory), or

−

click on the machine name or the web site in the left pane; MIME types at the machine or web site level are inherited by the virtual directories below them.

3.

Scroll down the list in the MIME Types dialog and verify whether or not .json has been added. If it has, proceed to step 7.

4.

If .json is not in the list, click Add.

5.

In the Add MIME Type dialog, enter:

File name extension: .json
MIME type: application/json

6.

Click OK to save the new MIME type.

7.

Scroll down the list in the MIME Types dialog and verify whether or not .form has been added. If it has, no further action is required—exit the MIME Types dialog and IIS.

8.

If .form is not in the list, click Add.

9.

In the Add MIME Type dialog, enter:

File name extension: .form
MIME type: text/xml

10.

Click OK to save the new MIME type.

11.

Exit Internet Information Services (IIS) Manager.

IIS does not need to be restarted to recognize new MIME types.

Configuration if Using IIS to Host a .NET Action Processor

The following are configuration functions you must perform if you are using IIS to host a .NET Action Processor.

If you are running the .NET Action Processor in a .NET Framework 4.0 application pool, also see .NET Action Processor Compatibility with .NET 4.0 in the Compatibility section of the TIBCO iProcess Workspace (Browser) Release Notes.

Note that these tasks are required only after an initial installation; if you have upgraded, these configuration changes should have already been made.

•

Give the IIS_IUSRS group modify permission to the Action Processor installation directory — see page 43.

•

Specify the Application Pool Identity and Give that User Full Control to the Action Processor Installation Directory — see page 44.

•

Convert the Action Processor’s virtual directory to an application — see page 46.

•

Change the location of the Action Processor log file — see page 46.

•

Start the web site to start the Action Processor — see page 46.

Give the IIS_IUSRS Group Modify Permission to the Action Processor Installation Directory

Note that this task is required only after an initial installation; if you have upgraded, this configuration change should have already been made.

The IIS_IUSRS group must be given modify permissions to the Action Processor installation directory. To do this:

1.

Right click on the directory that was created by the installer for the Action Processor files (TIBCOActProc in this example) and select Properties.

2.

On the Security tab, check to see if the IIS_IUSRS group account has modify permissions. If necessary, add the "IIS_IUSRS" group account and give it modify permissions:

Specify the Application Pool Identity and Give that User Full Control to the Action Processor

Note that this task needs to be performed only if this is the initial installation (if this is an upgrade, the permissions from the previous installation should still be correct).

This procedure uses the NETWORK SERVICE user as the application identity, as it is a built-in and available user, although you can use another user if desired.

The user that is specified as the application identity must be given full control permissions to the Action Processor installation directory so that it can write to the Action Processor log file. To do this:

1.

In Internet Information Services (IIS) Manager, select Application Pools in the left pane.

2.

Choose the application pool to use from the center pane.

3.

In the right pane, click Advanced Settings.

4.

On the Advanced Settings dialog, select the browse button in the field to the right of the Identity field

5.

On the Application Pool Identity dialog, choose NetworkService (or a different user account if you are using one other than Network Service) from the Built-in Account list, then click OK.

6.

On the Advanced Settings dialog, click OK.

7.

In the left pane of IIS Manager, right click on the Action Processor folder (TIBCOActProc in this example) and select Edit Permissions.

8.

On the Security tab, check to see if the NETWORK SERVICE account has full control permissions. If necessary, add the “NETWORK SERVICE” user account and give it full control permissions:

Convert the Action Processor’s Virtual Directory to an Application

Note that this task is required only after an initial installation; if you have upgraded, this will already have been done.

You must convert the virtual directory being used by the Action Processor to an application. To do this:

1.

From IIS Manager, right click on the virtual directory being used for the Action Processor and select Convert to Application from the drop-down menu:

2.

From the Add Application dialog, leave all default values and click OK.

The icon for the virtual directory changes to indicate it is now an application. For example:

Start the Web Site to Start the Action Processor

Starting the web site on which your .NET Action Processor is hosted starts the Action Processor.

To start the web site, in IIS Manager, right click on the web site hosting your Action Processor, then select Start.

If for some reason, the web site had not been previously stopped, stop it now, then restart it.

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.

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.

Add security filter to enable secure HTTP header

It is now possible to manually add security filter to enable secure HTTP header and reduce security threats in iProcess Workspace (Browser).

To add security filter and enable secure HTTP header, add the below lines in TomcatDir\conf\web.xml after the following tag



<filter>

<filter-name>httpHeaderSecurity</filter-name>

<filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>

<async-supported>true</async-supported>

<init-param>

<param-name>antiClickJackingOption</param-name>

<param-value>SAMEORIGIN</param-value>

</init-param>

<init-param>

<param-name>xssProtectionEnabled</param-name>

<param-value>true</param-value>

</init-param>

</filter>

<filter-mapping>

<filter-name>httpHeaderSecurity</filter-name>

<url-pattern>/*</url-pattern>

</filter-mapping>"

The above steps are same for every operating system that is used.

Start Tomcat to Start the Action Processor

Starting Tomcat causes the Action Processor to start.

The following sections describe how to start Tomcat, depending whether you have installed on Windows or UNIX.

Windows Systems

To start Tomcat on Windows systems:

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 on the Start button.

This starts Tomcat and the Action Processor.

3.

Click OK to close the Tomcat monitoring program.

Tomcat can also be stopped by executing the Tomcat monitoring program as described above, then clicking the Stop button. This also stops the Action Processor.

UNIX Systems

To start Tomcat on UNIX systems:

1.

Run the Tomcat startup script:

   TomcatDir/bin/startup.sh

This starts the Java Action Processor.