Create the First Cluster Node

Installation Guides › JBoss Version › Installation on a JBoss Cluster › How to Install CA Identity Manager on a JBoss Cluster › Create the First Cluster Node

Create the First Cluster Node

You begin creating the JBoss cluster by creating the first node. On Windows, IPv6 is not supported for a JBoss cluster with the current release of the JDK. Each node must be an IPv4 system or part of an IPv4/IPv6 stack.

This procedure refers to the admin_tools, which represents the location where the Administrative Toolkit is installed. The default location for this toolkit follows:

Windows: C:\Program Files\CA\Identity Manager\IAM Suite\Identity Manager\tools
UNIX: /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools

To create the first cluster node

Install the Identity Manager server on one of the systems intended to be part of the cluster.
- Windows: From your installation media, run the following program:
```
ca-im-r12.5sp3-win32.exe
```
- UNIX: From your installation media, run the following program:
```
ca-im-r12.5sp3-sol.bin
```
Note: If you install all nodes on one system, each node needs a separate jboss_home. This precaution is necessary to avoid contention over workpoint.log in the jboss_home/bin directory.
For the App Server URL and port, supply the URL and the port number of the web server used for load balancing. The default that appears applies to a standalone installation.
On Windows systems, edit run_idm.bat in the jboss_home\bin directory:
1. Uncomment the cluster-related parts of run_idm.bat.
2. If the multicast address test failed, add a multicast address preceded by the -u argument.
  The format with a multicast-address follows:
```
set ARGS=
set SERVER=default/deploy
	:loop
	if [%1] == [] goto endloop
        	set ARGS=%ARGS% %1
			if [%1] == [-c] set SERVER=%2/farm
        	shift
        goto loop
	:endloop
	ARGS=%ARGS% -g IdmPartition -u multicast-address
```
If you have integrated CA Identity Manager with Siteminder, perform the following steps:
1. Locate this section of the run_idm.bat or run_idm.bat script:
```
Remove anything from the path to prevent DLL conflicts
```
2. On the next line, location this portion of the PATH definition:
```
server\default\deploy\IdentityMinder.ear\
```
  In that portion, replace default\deploy with all\farm. It should now appear as follows:
```
server\all\farm\IdentityMinder.ear\
```
If you are installing on a system that supports IPv6/IPv4, modify the following property in the JAVA_OPTS entry:
```
set IDM_OPTS=%IDM_OPTS% -Djava.net.preferIPv4Stack=true
```
For Solaris systems, edit run_idm.sh in the jboss_home\bin directory:
1. Uncomment cluster-related parts of run_idm.sh.
2. If the multicast address test failed, add a multicast address preceded by the -u argument.
  The format for that line appears at the end of this section:
```
SERVER=default/deploy
ARGS=
	until [ -z "$1" ]
	do
	ARGS="${ARGS} $1"
	if [ $1 = '-c' ]
		then
		SERVER=$2/farm
	fi
	shift
	done
ARGS="${ARGS} -g IdmPartition -u multicast-address"
```
3. If you are installing on a system that supports IPv6, modify one of the following properties in the JAVA_OPTS entry:
  - For IPv6 only systems, uncomment the following entry:
```
	IDM_OPTS="$IDM_OPTS -Djava.net.preferIPv6Addresses=true"
```
  - For IPv6/IPv4 systems, uncomment the following entry:
```
	IDM_OPTS="$IDM_OPTS -Djava.net.preferIPv4Stack=true"
```
Copy the following files of jboss_home\server\default\deploy to jboss_home\server\all\farm:
- imworkflowdb-ds.xml
- reportsnapshot-ds.xml
- imauditdb-ds.xml
- imarchivedb-ds.xml
- imtaskpersistencedb-ds.xml
- objectstore-ds.xml
- castylesr5.1.1.ear
- IdentityMinder.ear
Copy login-config.xml from jboss_home\server\default\conf to jboss_home\server\all\conf.
Copy the following files from jboss_home\server\default\lib to jboss_home\server\all\lib:
- sqljdbc.jar (If MS-SQL is the object store)
- ojdbc14.jar (If Oracle is the object store)
Set up the JMS connection factory, topics, and queues definitions as follows:
1. Copy admin_tools\samples\Cluster\JBoss\deploy-hasingleton\jms\workflow-service.xml to jboss_home\server\all\deploy-hasingleton\jms.
2. Remove jboss_home\server\all\farm\IdentityMinder.ear\META-INF\workflow-service.xml.
3. Locate the jbossmq-destinations-service.xml in jboss_home\server\all\deploy-hasingleton\jms.
4. Add JMS topic and queue definitions to this file by copying in the content of the file:
```
jboss_home\server\all\farm\IdentityMinder.ear\META_INF\jbossmq-destinations-service.xml
```
  Important! Copy the content only in between the server tags.
5. Remove these files:
```
jboss_home\server\all\farm\IdentityMinder.ear\META-INF\jbossmq-destinations-service.xml.
jboss_home\server\all\farm\IdentityMinder.ear\identityminder_ejb.jar\META-INF\jbossmq-destinations-service.xml
```
Copy admin_tools\samples\Cluster\JBoss\IdentityMinder.ear over jboss_home\server\all\farm\IdentityMinder.ear
If Workflow Designer is installed, copy admin_tools\samples\Cluster\JBoss\IdentityMinder.ear\config\workpoint-client.properties to <CA ROOT>\IAM Suite\Identity Manager\tools\Workpoint\conf.
Make these changes for HTTP load balancing with sticky sessions:
- Modify jboss_home/server/all/deploy/jboss-web.deployer/META-INF/jboss-service.xml by changing the UseJK attribute to true.
- Modify jboss_home\server\all\deploy\jboss-web.deployer\server.xml by adding the following to the <Engine> tag in this format:
```
jvmRoute="worker1"
```
If you were referred to this procedure from the Upgrade Guide, return to the original procedure for any post-upgrade steps.

Important! If you are installing a JBoss cluster on an IPv6/IPv4 stack, modify the sample files on each system and replace jnp://localhost with jnp://host-name used in run_idm.bat or run_idm.sh. Modify all jboss.xml files.

If any issues occur during installation, check the installation logs.

Email CA Technologies about this topic