Upgrade Guide › JBoss Version › Upgrade on a JBoss Cluster › Upgrade or Migration on a JBoss Cluster › Migrate a Cluster to JBoss 6.1 EAP › Configure Journal Files

Configure Journal Files

To implement high availability on JBoss 6.1 EAP, CA IdentityMinder uses the HornetQ messaging provider. HornetQ persists messages using journal files without using a database. CA IdentityMinder stores journal files based on the following installation choice:

• Replication method -- CA IdentityMinder stores journal files on each node.
• Shared Store -- CA IdentityMinder stores journal files on a Storage Area Network (SAN) Server.

Journal Files for Replication

If you chose Replication during the installation, the installation program configured the first node with two HornetQ instances, a live instance and a backup. On each additional node, you configure live and backup HornetQ instances.

Follow these steps:

1. On the second node in the cluster, navigate to the following location:

   jboss_home/standalone/configuration
   

2. Edit the standalone-full-ha.xml file.
3. Replace each occurrence of node1 with node2.
4. Replace each occurrence of node2 with node1.
5. For a cluster of three or more nodes, edit standalone-full-ha.xml in a similar manner.

   For example, make these changes for a three-node cluster:

   • Node 1
     • A live HornetQ is a member of backup group node1
     • Backup HornetQ is a member of backup group node2
   • Node 2
     • A live HornetQ is a member of backup group node2
     • Backup HornetQ is a member of backup group node3
   • Node 3
     • A live HornetQ is a member of backup group node3
     • Backup HornetQ is a member of backup group node1

Journal Files for a Shared Store

If you chose Shared Store during the installation, you configure two HornetQ instances, a live instance and a backup, on each node. You configure each instance to store journal files on a Storage Area Network (SAN) Server.

Follow these steps:

1. Create a SAN Server with paths to each node.

   For example, if you have a two-node cluster, you configure a SAN Server with paths of //network-path/node1 and //network-path/node2.

2. On the first node, navigate to the following location:

   jboss_home/standalone/configuration
   

3. Edit the standalone-full-ha.xml file.
4. Locate the <hornetq-server> section of the file.
5. Uncomment the section and set the paths for 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"/>
   -->
   

6. Locate the <hornetq-server name="backup"> section of the file.
7. Uncomment this section and set the paths for 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"/>
   -->
   

8. Repeat this procedure for the second node in the cluster, replacing node1 with node2 and node2 with node1.
9. For a cluster of three or more nodes, edit the standalone-full-ha.xml file in a similar manner.

   For example, in a three-node cluster, make these changes:

   • 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