27.2 Preparing a JBoss Cluster for the User Application

JBoss comes with three different ready-to-use server configurations: minimal, default and all. You can enable clustering in the all configuration only. A cluster-service.xml file in the /deploy folder describes the configuration for the default cluster partition. When you install the User Application and indicate to the installation program that you want to install into a cluster, the installation program makes a copy of the all configuration, names the copy IDM by default, and installs the User Application into this configuration.

27.2.1 Setting JBoss System Properties

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 User Application cache framework.

  1. Open the JBoss startup script, by default located in the directory where you downloaded the User Application files.

    • Linux: start-jboss.sh

    • Windows: start-jboss.bat

  2. Add the following text to the script:

    start run.bat -c IDM -Djboss.partition.name=PartitionName-
Djboss.partition.udpGroup=UDP_Group -Dcom.novell.afw.wf.engine-id=Engine_ID

    where

    • PartitionName represents the name of the partition, such as Example_Partition.

    • UDP_Group represents the User Datagram Protocol (UDP) group for the partition, such as 228.3.2.1.

    • Engine_ID represents the unique ID of the workflow engine, such as Engine1.

  3. Close and save the setup script.

27.2.2 Specifying the Cluster Option

When you install the User Application , you must specify the Identity Manager server name and workflow engine ID. Ensure that you also click all for Single node (Default) or cluster (All)? in the IDM Configuration window. For more information, see Step 25 and Step 27.

27.2.3 Configuring the Cluster for the User Application Database

All nodes in the JBoss cluster must access the same database instance. Each time that you install the User Application to a cluster node, specify the same database name, host name or IP address, and port of the server on which the database for the User Application is installed.

27.2.4 Using the Same Master Key for Each User Application in the Cluster

The Identity Manager User Application encrypts sensitive data using a master key. All User Applications in a cluster must use the same master key. This section helps you ensure that all User Applications in a cluster use the same master key.

For more information about creating the master key, see Step 31. For more information about encrypting sensitive data in the User Application, see “Encryption of Sensitive User Application Data” in the User Application Administration Guide.

  1. Install the User Application on the first node in the cluster.

  2. In the Security - Master Key window of the installation program, note the location of the master-key.txt file that will contain the new master key for the User Application. By default, the file is in the installation directory.

  3. Install the User Application on the other nodes in the cluster.

  4. In the Security - Master Key window, click Yes and then click Next.

  5. In the Import Master Key window, copy the master key from the text file that was created in Step 2.

27.2.5 Starting the User Application in a Cluster Group

After you install the User Applications in your cluster, you must enable the cluster in the User Application cluster configuration.

  1. Ensure that all servers are stopped.

  2. Start the first User Application in the cluster.

  3. Log on as the User Application administrator.

  4. Click Administration.

  5. In the Application Configuration portal, click Caching.

  6. In the Caching Management window, select True for Cluster Enabled.

  7. Click Save.

  8. Restart the server.

  9. (Conditional) To use local settings, repeat this procedure for each server in the cluster.