OTN Home > Oracle WebLogic Server 12.2.1.0 Documentation > Administration Console Online Help > Configure custom persistent stores

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure custom persistent stores

Before you begin

Review the following information to help you select the type of persistent store for your environment:
  • Administering the WebLogic Persistent Store
  • Using the Replicated Store

    Note: A WebLogic Replicated Store is a high performance storage option only for Exalogic hosted Weblogic Messaging Services. 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. Replicated Stores are not supported in domain partitions, resource groups, and resource group templates.


A persistent store provides a built-in, high-performance storage solution for WebLogic Server subsystems and services that require persistence. For example, it can store persistent JMS messages or durable subscriber information, as well as temporarily store messages sent to an unavailable destination using the Store-and-Forward feature. The persistent store supports persistence to a file-based store (File Store), a JDBC-enabled database (JDBC Store), or replicated memory (Replicated Store).

The main steps for configuring a persistent store are:

  1. In the left pane of the console, expand Services and select Persistent Stores.
  2. On the Summary of Persistent Stores page, click New.
  3. Select the store type from the drop-down box:

After you finish

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


Back to Top