In a cluster, a recommended
best practice is to target a JMS-related service to a migratable target
so that a server member will not be a single point of failure. A
migratable target is a special target that serves as a grouping of
services and which is active on only server member in a cluster. High
availability is achieved by migrating a migratable target from one
server member to another when a problem occurs on the original server.
You can manually migrate a migratable target or you configure it for
automatic migration. JMS-related services include JMS servers, SAF
agents, path service, and custom persistent stores.

Configure
migratable targets for your JMS-related services, including specifying
a preferred host server in the cluster, selecting candidate servers to
use as a backup for services on the migratable target, and specifying
a migration policy. When using a migratable target, configure the
migratable target before deploying or activating the service in the
cluster. See Configure migratable targets
for JMS-related services.

For persistent
messaging, 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 store must be configured such that all the candidate
servers in the migratable target have access to it. See Configure custom
persistent stores.

Target the JMS
services to the same migratable target used by the custom persistent
store. See the following topics: