OTN Home > Oracle WebLogic Server 12.2.1.0 Documentation > Administration Console Online Help > Create Replicated Stores

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create Replicated Stores

Before you begin

Note: Replicated stores are not supported in a domain partition, resource group, or resource group template.

A WebLogic Replicated Store is a high performance storage option for Exalogic hosted Weblogic Messaging Services and is an alternative to WebLogic Server’s File and JDBC persistent storage options. Replicated stores depend on Exalogic replicated memory that is managed by a separately administered Daemon Cluster that must be started before a WebLogic Replicated Store can boot. A Global Directory for the Replicated Store must already exist in your environment, so be sure to create it before completing this page. See Configuration and Tuning Requirements for a Global Directory.

A Replicated Store uses Exalogic replicated memory for storing subsystem data, such as persistent JMS messages or durable subscriber information.

  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 panel of the console, expand Services and select Persistent Stores.
  3. On the Summary of Persistent Stores page, click New > Create Replicated Store.

    Note: Once you create a replicated store, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  4. On the Create a new Replicated Store page, update the following:
    1. Name -- Name for the Replicated Store.
    2. Target -- Server instance, cluster, or migratable target on which to deploy the replicated store.

      Note: When selecting a cluster, the store must be targeted to the same cluster as the JMS server. When selecting a migratable target, the store must the same migratable target as the migratable JMS server or SAF agent.

    3. Directory -- Path of the Global Directory.

      Note: This directory contains the rs_daemons.cfg file and must be an absolute directory path.

    4. Click Finish.

    For more information about these fields, refer to Configuration Options.

  5. On the Summary of Persistent Stores page, select the replicated store created in step 3.
  6. On the Replicated Store > Configuration tab, update any parameters as required.

    For more information about these fields, refer to Configuration Options.

  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

You do not need to restart the Administration Server after creating and initially configuring a replicated store. However, if you modify an existing replicated store, you must restart the Administration Server.


Back to Top