Before you begin
Before you can configure JMS-related services to automatically migrate to another server in the cluster, you must configure the managed servers in the cluster for migration, including assigning managed servers to a machine and configuring Node Manager. See Configure JMS-related services migration.
A migratable target is a special target that serves as a grouping of services, such as such as JMS servers, SAF agents, path service, or custom stores, 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, either manually or automatically, based on server health monitoring capabilities. For automatic migration, you need to select the appropriate automatic migration policy. You can also optionally provide pre/post-migration scripts to move a persistent store's data across migrated servers. There are also options to have a migratable target with a failed service deactivated and reactivated in place, instead of being migrated.
To configure the migratable target servers for JMS-related service migration:
a. In User Preferred Server Name, select the server in the cluster that you want to associate the migratable target with.
b. In Service Migration Policy, select the automatic migration policy that you want to use:
c. Click Finish.
For more information on auto-migrating JMS services, see Configure automatic migration of JMS services.
Note: The pre/post-migration scripts must be located in the BEA_HOME/user_projects/domains/mydomain/bin/service_migration directory, where mydomain is a domain-specific directory, with the same name as the domain. For your convenience, sample pre/post-migrations scripts are provided in this directory.
For more information about these fields, refer to Configuration Options.