Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Change path service targets

After you create a path service, you can retarget it to another cluster member or migratable target server. A migratable target is a logical target that serves as a grouping of services, such as a path service, 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. A recommended best practice is to target the path service to a migratable target, so that a member server will not be a single point of failure. You can manually migrate a migratable target or you configure it for automatic migration.

To retarget your path service instance to a different cluster member or migratable target:

  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 left pane of the console, expand Services > Messaging and select Path Services.
  3. On the Summary of Path Services page, select the instance you want to configure.

    If the table is empty, refer to Create path services.

  4. Click the Targets tab.
  5. Clear the currently selected cluster member or migratable target server check box.
  6. Select the cluster member or migratable target server where you want to target the path service.

    Note: When a path service is targeted to a migratable target, it cannot use the default store, so a store must be configured and targeted to the same migratable target. As an additional best practice, the Path Service and its store should be the only users of that migratable target.

    For more information on configuring a migratable target for a path service, see Configure migratable targets for JMS-related services.

  7. Click Save.
  8. 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).

After you finish

If you change the cluster member or migratable target server, you must stop and restart WebLogic Server.

Back to Top