Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure the JTA transaction recovery service for migration

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 and post-migration scripts are not 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 transaction recovery 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:

  1. For manual or automatic service migration, 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. For highest reliability, use a shared storage solution that is itself highly available—for example, a storage area network (SAN) or a dual-ported disk. See Configure the default persistent store for transaction recovery service migration.
  2. When using the automatic service migration Feature, you must configure the "Migration Basis" for the cluster, enable automatic migration, and optionally specify whether you will be using any pre/post migration scripts, as described in Configure automatic migration of the JTA transaction recovery service.
  3. 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.

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.

Back to Top