Fusion Middleware Control Help for WebLogic Server

Server Template: Configuration: Migration

Configuration Options     

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-related services (such as JMS servers, SAF agents, path services, and custom persistent stores) and the JTA Transaction Recovery Service on this server so that they can be manually migrated to another server. You can also specify to have the JTA Transaction Recovery Service automatically migrated to another server.

Use this page to enable server migration or to configure services-only migration.

Configuration Options

Name	Description
Automatic Server Migration Enabled	Specifies whether Node Manager can automatically restart this server and its services on another machine if the server fails. MBean Attribute: ServerMBean.AutoMigrationEnabled Changes take effect after you redeploy the module or restart the server.

Configuration Options

Name	Description
JTA Migration Policy	Defines the type of migration policy to use for the services hosted by this migratable target. Valid options are: Manual Service Migration Only Indicates that no automatic migration of services hosted by this migratable target will occur. Auto-Migrate Exactly-Once Services Indicates that if at least one Managed Server in the candidate server list is running, the services hosted by this migratable target will be active somewhere in the cluster if servers should fail or are administratively shut down (either gracefully or forcibly). For example, it is a recommended best practice to use this policy when a migratable target hosts a path service, so if its preferred server fails or is shut down, the path service will automatically migrate to another candidate server, and so will always be active in the cluster. Notes This value can lead to target grouping on a server member. For example, if you have five exactly-once migratable targets and only one Managed Server is started in the cluster, then all five targets will be activated on that server. This policy does not apply for JTA service migration. Auto-Migrate Failure-Recovery Services Indicates that the services hosted by this migratable target will only start if the migratable target's User Preferred Server (UPS) is started. If an administrator manually shuts down the UPS, either gracefully or forcibly, then a failure-recovery service will not migrate. However, if the UPS fails due to an internal error, then the service will be migrated to another candidate server. If such a candidate server is unavailable (due to either a manual shutdown or an internal failure), then the migration framework will first attempt to reactivate the service on its UPS server. If the UPS server is not available at that time, then the service will be migrated to another candidate server. Auto-Migrate Shutdown-Recovery Services Indicates that the services hosted by this migratable target will migrate to one of the candidate servers, if server is administratively shut down (either gracefully or forcibly). Once recovery is done, service is migrated back to failed server. MBean Attribute: MigratableTargetMBean.MigrationPolicy Changes take effect after you redeploy the module or restart the server.
Enable Strict Ownership Check	Whether continue to boot if cannot find the current owner of TRS to do failback. This attribute is only meaningful for servers in cluster. If true: server will fail to boot under this situation. If false: server will continue to boot without trying to do failback. MBean Attribute: JTAMigratableTargetMBean.StrictOwnershipCheck