Configuration Options Related Tasks Related Topics
If a clustered server fails, WebLogic Server can automatically restart (migrate) the server and its services on another machine. Alternatively, you can configure options for the JMS and JTA services on this server so that you can manually migrate the services to another server.
Use this page to enable server migration or to configure services-only, migration.
Limits the list of candidate machines that the cluster specifies. (Requires you to enable this server for automatic migration and to configure the cluster with a set of candidate machines.)
If this server fails and if it is enabled for automatic migration, Node Manager automatically restarts it. By default, Node Manager restarts the server on any of the candidate machines that the cluster specifies (in order of preference that you configured in the cluster). To change the default, you use this server's list of candidate machines to create a subset of the cluster-wide candidates. You can also change the order of preference.
|Auto Migration Enabled||
Specifies whether Node Manager can automatically restart this server and its services on another machine if the server fails.
|JMS Candidate Servers||
Select servers in the cluster to use as a backup for this server's JMS services.
|JTA Candidate Servers||
Select servers that can access the JTA log files (in the WebLogic default persistent store) for the current server.
To migrate the Transaction Recovery Service from a failed server in a cluster to another server (backup server) in the same cluster, the backup server must have access to the transaction log files from the failed server. WebLogic Server uses the WebLogic default persistent store to store transaction log files. Therefore, you must configure the default persistent store to store its data files in a file system on persistent storage, such as a Storage Area Network (SAN) device or a dual-ported disk, available to both the primary server and the server that will act as its backup.