The identity applications supports HTTP session replication and session failover. If a session is in process on a node and that node fails, the session can be resumed on another server in the cluster without intervention. Before installing the identity applications in a cluster, you should prepare the environment.
The User Application cluster group uses a UUID name to minimize the risk of conflicts with other cluster groups that users might add to their servers. You can modify the configuration settings for User Application cluster group using the User Application administration features. Changes to the cluster configuration take effect for a server node only when you restart that node.
Each server that hosts the identity applications in the cluster can run a workflow engine. To ensure performance of the cluster and the workflow engine, every server in the cluster should use the same partition name and partition UDP group. Also, each server in the cluster must be started with a unique ID for the workflow engine, because clustering for the workflow engine works independently of the cache framework for the identity applications.
To ensure that your workflow engines run appropriately, you must set system properties for Tomcat.
Create a new JVM system property for each identity applications server in the cluster.
Navigate to the /opt/netiq/idm/apps/tomcat/bin/setenv.sh file.
Name the system property com.novell.afw.wf.engine-id where the engine ID is a unique value.