Installation Guide › JBoss Version › Installation on a JBoss Cluster › How to Install CA IdentityMinder on a JBoss Cluster › Configure Journal Files for JBoss 6.1

Configure Journal Files for JBoss 6.1

JBoss EAP 6.1 uses a new messaging provider named HornetQ. HornetQ persists messages using journal files without using a database. CA IdentityMinder uses the Shared Store method to achieve high availability. On each node, you configure two HornetQ instances, a live instance and a backup. You configure each instance to store journal files on a Storage Area Network (SAN) Server. The server has a directory for each node. You configure the reference to these directories in the standalone-full-ha.xml file.

For example, consider the situation where you have a cluster of two nodes. First, you configure a SAN Storage with paths of //network-path/node1 and //network/path/node2.

Then, for node1, you configure the XML file as follows:

• A live HornetQ points at network-path/node1
• Backup HornetQ points at network-path/node2

Finally, for node2, you configure the XML file as follows:

• A live HornetQ points at /network/path/node2
• Backup HornetQ points at /network/path/node1

Follow these steps:

1. Navigate to the following location:

   jboss_home/standalone/configuration
   

2. Edit the standalone-full-ha.xml file.
3. Locate the <hornetq-server> section of the file.
4. Uncomment the section and set the paths to point to the the correct directories.

   <!-- un mark this for node 1 and set your path until node1jr
           <paging-directory path="//network/path/node1jr/paging"/>
           <bindings-directory path="//network/path/node1jr/bindings"/>
           <journal-directory path="//network/path/node1jr/journal"/>
           <large-messages-directory path="//network/path/node1jr/large-messages"/>
           -->
   

5. Locate the <hornetq-server name="backup"> section of the file.
6. Uncomment this section and set the paths to point to the correct directories.

   <!-- un mark this for node 1 backup (which is node2jr) and set your path until node2jr
   	<paging-directory path="//network/path/node2jr/paging"/>
   	<bindings-directory path="//network/path/node2jr/bindings"/>
   	<journal-directory path="//network/path/node2jr/journal"/>
   	<large-messages-directory path="//network/path/node2jr/large-messages"/>
   	-->
   

7. Repeat this procedure for the second node in the cluster ensuring to replace node1 with node2 and vice versa.

   For a cluster of three or more nodes, the live and backup references should be linked such as in the following example:

   • Node 1
     • A live HornetQ points at network-path/node1
     • Backup HornetQ points at network-path/node2
   • Node 2
     • A live HornetQ points at /network/path/node2
     • Backup HornetQ points at /network/path/node3
   • Node 3
     • A live HornetQ points at /network/path/node3
     • Backup HornetQ points at /network/path/node1