| |
Before you begin
Ensure that you have created a machine and have assigned managed servers to it. For more information on configuring a machine, see Create and configure machines. For more information on assigning servers to a machine, see Assign server instances to machines.
Ensure that you have configured Node Manager for Consensus leasing. For Database leasing, Node Manager is required only if pre-migration/post-migration scripts are defined. For more information, see Roadmap for Configuring Automatic Migration of the JTA Transaction Recovery Service.
WebLogic Server provides the ability to migrate the Transaction Recovery Service at both the server level and the service level, either manually or automatically. Automatic service migration of the Transaction Recovery Service migration leverages the Health Monitoring subsystem to monitor the health of the service hosted by a migratable target. When the primary server fails, the migratable service framework automatically migrates the Transaction Recovery Service to a backup server. The migration framework selects a backup server from the configured candidate servers. If a backup server fails before completing the migration actions, then you must attempt to manually re-migrate the Transaction Recovery Service to another backup server.
Note: For instructions on configuring whole server migration, which includes migrating the Transaction Recovery Service, see Configure server migration in a cluster.
The main steps for configuring Transaction Recovery Service migration at the service level are:
After you finish
If you are not using the Automatic Service Migration feature, you will need to manually migrate the Transaction Recovery Service. See Manually migrate the Transaction Recovery Service.
 |