Before you begin
Before you can migrate the Transaction Recovery Service to another server in the cluster, you must configure the managed servers in the cluster for migration. See Configure the JTA Transaction Recovery Service for migration.
In addition, you must configure the default persistent store so that it stores records in a shared storage system that is accessible to any potential machine to which a failed migratable server might be migrated. See Configure the default persistent store for Transaction Recovery Service migration.
You may also want to restrict the potential servers to which you can migrate the Transaction Recovery Service to only those that have access to the transaction log files. See Configure candidate servers for Transaction Recovery Service migration.
The Transaction Recovery Service is designed to gracefully handle transaction recovery after a crash. BEA recommends that you attempt to restart a crashed server and allow the Transaction Recovery Service to handle incomplete transactions, rather than migrate the Transaction Recovery Service to another server. However, if you anticipate that the server will be unavailable for an unacceptable length of time, you can migrate the Transaction Recovery Service to another service so that the backup server can complete transaction work for the failed server.
For more information about migrating the Transaction Recovery Service, see Transaction Recovery After a Server Fails.
The server that you select must have access to the default persistent store (transaction log files) for the current server. The selected server will perform the transaction recovery process for the failed server.
A request is submitted to migrate the Transaction Recovery Service and the configuration edit lock is released. If the migration fails, an error message is displayed.