Before you begin
Before you can configure JMS-related services to be automatically migrated to another server in the cluster, you must configure a migratable target for the service and its associated persistent store. See Configure migratable targets for JMS-related services.
For persistent messaging, you must configure a custom persistent store that is targeted to the same migratable target as the JMS service. Unless you are using pre/post migration scripts to move the store data across migrated servers, the custom store must be configured such that all the candidate servers in the migratable target have access to it. See Configure JMS-related services migration.
You can configure your JMS-related services to be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services. For example, a JMS server, all of its destinations, and its associated persistent store will automatically move with their migratable target to a healthy server if the current hosting server should fail. JMS-related services include JMS servers, SAF agents, path service, and custom stores.
To configure the automatic migration of JMS-related services hosted by a migratable target:
After you finish
You may want to migrate a JMS service back to the original primary server once it is back online. Unlike the JTA Transaction Recovery Service, JMS services do not automatically migrate back to the primary server when it becomes available, so you need to manually migrate these services. See Manually migrate JMS-related services.