38.2.2. Dedicated JCA Backup Server

For the backup server, the hornetq-configuration.xml is unchanged. Because there is no live server, you must ensure the hornetq-jboss-beans.xml instantiates all the beans needed. You configure this using the same configuration as in the live server, with the exception of changing the location of the hornetq-configuration.xml parameter for the Configuration bean.

Procedure 38.11. Configure Dedicated Backup Server

Follow this procedure to configure a dedicated HornetQ backup instance, located on a separate JBoss Enterprise Application Platform server.
Prerequisites

  • A HornetQ Live Server, configured according to the procedures contained within Section 38.2.1, “Dedicated JCA Live Server”
  • A correctly configured JBoss Enterprise Application Platform instance, installed on a separate server instance to the live server.
  • HornetQ installed on the platform instance.

  1. On the backup server, navigate using the command line to /extras/hornetq/.
  2. Execute sh ./switch.sh -Dbackup=true.
    The script executes and creates a production-backup server profile in $JBOSS_HOME/server/
  3. Copy the production-backup server profile, and rename it to HornetQ_Dedicated_Backup.
  4. Open $JBOSS_HOME/server/HornetQ_Dedicated_Backup/hornetq/hornetq-configuration.xml
  5. Add the <shared-store>true</shared-store> element as a child element to the <configuration> element.
  6. Change the data directory locations to match the following values:
    • <large-messages-directory>/media/shared/data/large-messages</large-messages-directory>
    • <bindings-directory>/media/shared/data/bindings</bindings-directory>
    • <journal-directory>/media/shared/data/journal</journal-directory>
    • <paging-directory>/media/shared/data/paging</paging-directory>
  7. Save and close all updated files.