JMS-related services are hosted on individual server instances within a cluster and for these services, the WebLogic Server migration framework supports failure recovery with service migration, as opposed to failover. In a clustered server environment, a recommended best practice is to target the JMS server to a migratable target, so that a member server will not be a single point of failure. Therefore, the following prerequisite instruction is required if configuring The WebLogic Message Queue In A Cluster.
Note: The instruction below assumes the WebLogic domain being configured has managed servers already created and assigned to a cluster parameter.
- Configure the cluster migration Basis to Consensus:
- Log in into the WebLogic Administration console.
- In the Change Center of the Administration Console, click Lock & Edit.
- Navigate to the following location under the Domain Structure:
Environment -> Clusters -> ClusterName -> Migration
- Locate the Migration Basis drop-down list and change its value to Consensus.
- Select Save.
- Select Active Changes.
- Configure a migratable target for one of the managed servers in the cluster:
- In the Change Center of the Administration Console, click Lock & Edit.
- In the Domain Structure tree, expand Environment, then select Migratable Targets.
- On the Summary of Migratable Targets page, select the link for one of the managed servers in the list.
- Select the migration tab:
- In Service Migration Policy, select the Auto-Migrate Exactly-Once Services migration policy.
- In Constrained Candidate Servers, move the user-preferred server and the additional managed servers in the cluster you want to support failure recovery from the Available column to the Chosen column.
- Select Save.
- In the Change Center of the Administration Console, click Active Changes.
- Restart the Admin server and the managed servers in the cluster for changes to take effect.