Create & Configure Additional Cluster Nodes

Note: Optional step only applicable when setting up a JBoss cluster

Creating more nodes from a cluster configuration already done on the "master" node is easy. This document will guide you through the steps you need to perform.

Please note that you can not run multiple cluster nodes belonging to the same cluster on a single host. You need a separate host for each cluster node!

All cluster nodes will run the JBoss Application Server and the IFS Batch Server. Load balancing capabilities of IFS Connect Server are limited, as described here. If not load balanced, the IFS Connect Server should run on a separate host.

The master node

On the "master" node (where you ran the Installer to create your first server instance), create a zip file containing your entire <ifs_home> folder. Copy this file to all other cluster node hosts.

The other cluster nodes

Unpack the zip file containing the <ifs_home> created earlier to the same folder structure as on the master node. It is vital that you really use the exact same folder structure on all nodes, i.e. if your <ifs_home> on the master node was created in D:\ifs\applications8, you need the same folder structure on all cluster nodes.

The IFS Batch Server configuration will be identical on all cluster nodes. This has some implications on the message processing.

All cluster nodes (including the master node)

1. Locate and run the setup_cluster_node.cmd located in <ifs_home>\instance\<instance>\bin
   You will be prompted for Server Peer ID. Each node must be given a unique identity for the cluster to work. Specify an integer value and press enter. Next you must verify that the JBoss Home directory is correct. Change the default value if it is not. Press enter and verify that the script is executed successfully.
2. Configure your load balancer according to vendor's instructions. If you are using Apache 2 as load balancer you can use the configuration file created by the installer as described here.

The IFS Connect Server host

If not load balanced, the IFS Connect Server agent should run on a separate host and therefore you need to create a separate installation on this host.

Create a <ifs_home> using the zip file you created earlier. Start only the IFS Connect Server agent using the start scripts in <ifs_home>\instance\<instance>\bin. Alternatively install as remote Connect Server.

Verify

	Start JBoss and IFS Batch Server on all cluster nodes. Start IFS Connect Server on the Connect Server host. There should be no errors.
	N/A