OTN Home > Oracle WebLogic Server 12.2.1.2.0 Documentation > Administration Console Online Help > Configure a file store for high availability

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure a file store for high availability

Before you begin


To configure high availability (HA) for this store and the JMS services that reference this store, such as JMS Servers, SAF Agents, or Path Service:

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

    If the table is empty, refer to Create file stores.

  3. On the Configuration > High Availability tab, update as necessary:
    1. Distribution Policy -- Specifies if the store is a singleton or is distributed as one store for each server instance in a cluster.
      • The store 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 to allow JMS Servers that use this store to host stand-alone destinations or when referenced by a Path Service .
      • Set to Distributed to allow JMS Servers that use this store to host JMS distributed destinations or when referenced by SAF Agents.
    2. Migration Policy -- Specifies the migration policy used by a store.
      • The store 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 or Always when Distribution Policy =Singleton.
    3. Restart In Place -- The store is automatically restarted as needed.
    4. Seconds Between Restarts -- The amount of time, in seconds, to wait in between attempts to restart a failed store.

      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 store.

      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 store 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 store 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 an HA configuration requires a server or cluster restart. If the resource is in a partition, restart the partition.


Back to Top