Before you begin
Note: Oracle recommends configuring high availability using cluster targeted JMS servers that share same cluster target with a custom store. The legacy migratable targets feature is not supported in partitions, resource groups, or resource group templates. See Configure JMS Services for migration and high availability.
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 not defined. For more information, see Roadmap for Configuring Automatic Migration of JMS-Related Services.
In a cluster, a recommended best practice is to target a JMS-related service to a migratable target so that a server member will not be a single point of failure. A migratable target is a special target that serves as a grouping of services and which is active on only server member in a cluster. High availability is achieved by migrating a migratable target from one server member to another when a problem occurs on the original server. You can manually migrate a migratable target or you configure it for automatic migration. JMS-related services include JMS servers, SAF agents, path service, and custom persistent stores.
Note: For instructions on configuring whole server migration, see Configure server migration in a cluster.
After you finish
If you are not using the Automatic Service Migration feature, you will need to manually migrate your JMS-related services. See Manually migrate JMS-related services using migratable targets.