Administration Console Online Help

    Previous Next  Open TOC in new window 
Content starts here

Configure migratable targets for JMS-related services

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

A migratable target is a special target that can serve as a grouping of JMS 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 manually migrating a migratable target from one server member to another when a problem occurs on the original server. You can also optionally provide pre/post-migration scripts to move a persistent store's data across migrated servers.

To configure the migratable target servers for JMS-related service migration:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Domain Structure tree, expand Environment, then select Migratable Targets.
  3. On the Summary of Migratable Targets page, click New.
  4. On the Create a new Migratable Target page:
    1. In Name, enter a name for the migratable target.
    2. In Cluster, select a configured cluster for the migratable target.
    3. Click Next.
  5. On the Migratable Target Properties page:
    1. In User Preferred Server Name, select the server in the cluster that you want to associate the migratable target with.
    2. Click Finish.
  6. On the Summary of Migratable Targets page, select the migratable target created in steps 3 and 4.
  7. On the Migratable Target > Configuration > Migration page, update any additional parameters as required:
    • Constrained Candidate Servers -- select the servers you want to use as a JMS server backup and move them to the Chosen list. The servers you select must have access to the current service's custom store, which must also be targeted to the same migratable target as the migratable JMS service. Either that, or you must use the following fields to define migration pre/post migration scripts to move the store's data to the target backup server.
    • Pre-Migration Script Path -- the path to the pre-migration script to run before a migratable target is actually activated.
    • Post-Migration Script Path -- the path to the post-migration script to run after a migratable target is fully deactivated.
    • Allow Post-Migration Script To Run On a Different Machine -- specifies whether or not the post-deactivation script is allowed to run on a different machine.

    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.

  8. Click Save to save your changes.
  9. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

  Back to Top