Before you begin
Before you can migrate the JTA Transaction Recovery Service (TRS) to another server in the cluster, you must configure the managed servers in the cluster for migration, including assigning managed servers to a machine and configuring Node Manager. See Configure server migration in a cluster.
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.
A migratable target is a list of servers in the cluster that can potentially host a pinned service, such as the JTA Transaction Recovery Service. Migratable targets control the servers to which you can migrate a service, either manually or automatically. For the TRS, you must specify the list of candidate servers that have access to the current server's transaction log files (stored in the default WebLogic store). For automatic migration, you must select the appropriate migration policy. You can also define the appropriate pre-migration and post-migration scripts to perform any unmounting and mounting of shared storage, as needed.
To configure the migratable target servers for JTA Transaction Recovery Service migration:
Note: For JTA, you must specify the list of candidate servers that have access to the current server's transaction log files (stored in the default WebLogic file store).
For more information about these fields, refer to Migratable Target: Configuration: Migration.