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.

A JMS-related service can be migrated with its hosting migratable
target to another server member within a cluster. This includes both
scheduled migrations as well as manual migrations in response to a
server failure within the cluster. For example, a JMS server, all of its
destinations, and its associated persistent store can migrate 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. You can migrate all migratable targets at
once or on a target-by-target basis.

To manually migrate a JMS-related
service hosted by a migratable target:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

To migrate one or
migratable targets at once, on the Summary of Migratable
Targets page:

Click the Control tab.

Use the check boxes to select one or more migratable targets
to migrate.

Click Migrate.

Use the New hosting server drop-down
to select a new server for the migratable target(s).

Click OK.

Note: The server that you select must have access to the
custom persistent store for the current server. If necessary, the
selected server will perform the transaction recovery process for
the failed server.

A request is submitted to migrate the JMS-related service and the
configuration edit lock is released. In the Migratable
Targets table, the Status of Last
Migration column indicates whether the requested
migration has succeeded or
failed.

To migrate a
specific migratable target, on the Summary of Migratable
Targets page:

Select the migratable target to migrate.

Click the Control tab.

Again, select the migratable target to migrate.

Click Migrate.

Use the New hosting server drop-down
to select a new server for the migratable target.

Click OK.

Note: The server that you select must have access to the
custom persistent store for the current server. If necessary, the
selected server will perform the transaction recovery process for
the failed server.

A request is submitted to migrate the JMS-related service and the
configuration edit lock is released. In the Migratable
Targets table, the Status of Last
Migration column indicates whether the requested
migration has succeeded or
failed.