OTN Home > Oracle WebLogic Server 12.2.1.0 Documentation > Administration Console Online Help > Configure a messaging bridge for high availability

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure a messaging bridge for high availability

Before you begin


To configure high availability (HA) settings for this messaging bridge:

  1. In the left pane of the console, expand Services > Messaging and select Bridges.
  2. On the Summary of Messaging Bridges page, select the instance you want to configure.

    If the table is empty, refer to Create messaging bridge instances.

  3. On the Configuration > High Availability tab, update as necessary:
    1. Distribution Policy -- Specifies if the messaging bridge is a singleton or is distributed as one bridge instance for each server instance in a cluster.
      • Message Bridge must be targeted to a cluster. If scoped to a Resource Group or Resource Group Template, the target is inherited from the Virtual Target.
      • Set to Singleton when you need one bridge instance per cluster.
      • Set to Distributed when you need one bridge instance on every cluster member of a cluster.
    2. Migration Policy -- Specifies the migration policy used by a messaging bridge.
      • Message Bridge must be targeted to a cluster. If scoped to a Resource Group or Resource Group Template, the target is inherited from the Virtual Target.
      • Cluster leasing must be configured when not set to Off.
      • Set to On-Failure when Distribution Policy =Singleton.
    3. Restart In Place -- Messaging bridges automatically restart connections as needed.
    4. Seconds Between Restarts -- The amount of time, in seconds, to wait in between attempts to restart a failed messaging bridge connection.

      This setting applies only when Migration Policy is not set to Off.

    5. Number Of Restart Attempts -- Specifies how many restart attempts to make before migrating a failed messaging bridge.

      This setting applies only when Migration Policy is not set to Off.

    6. Initial Boot Delay Secconds -- Specifies the amount of time, in seconds, to delay before starting a messaging bridge after a failure.

      This setting applies only when Migration Policy is not set to Off.

    7. Failback Delay Seconds -- Specifies the amount of time, in seconds, to delay before failing a messaging bridge back to its preferred server after a failure.

      This setting applies only when Migration Policy is not set to Off.

    8. Partial Cluster Stability Delay Seconds -- Specifies the amount of time, in seconds, to delay before a partially started cluster should try to start dynamically configured services.

      This setting applies only when Migration Policy is not set to Off.

    For more information on general destination attributes, see Configuration Options.

  4. Click Save.

After you finish

Changing a messaging bridge HA configuration requires a server or cluster restart.


Back to Top