Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure JMS-related services 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/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.

The main steps for configuring JMS-related service migration are:

  1. When using the Automatic Service Migration Feature, you must configure the "Leasing Basis" for the cluster, as described in Configure automatic migration of JMS services.
  2. Configure migratable targets for your JMS-related services, including specifying a preferred host server in the cluster, selecting candidate servers to use as a backup for services on the migratable target, and specifying a migration policy. When using a migratable target, configure the migratable target before deploying or activating the service in the cluster. See Configure migratable targets for JMS-related services.
  3. For persistent messaging, configure a custom persistent store that is targeted to the same migratable target as the JMS service. Unless you are using pre/post migration scripts to move the store data across migrated servers, the store must be configured such that all the candidate servers in the migratable target have access to it. See Configure custom persistent stores.
  4. Target the JMS services to the same migratable target used by the custom persistent store. See the following topics:

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.

Back to Top