Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Replicated Store: Configuration

Configuration Options     Advanced Configuration Options     Related Tasks     Related Topics

Use this page to configure a Replicated Store for storing subsystem data, such as persistent JMS messages or Store-and-Forward messages.

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.

Configuration Options

Name Description

The name of this replicated store. This name must be unique within a WebLogic domain.


The server instances, clusters, or migratable targets defined in the current domain that are candidates for hosting a file store, JDBC store, or replicated store. If scoped to a Resource Group or Resource Group Template, the target is inherited from the Virtual Target.

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 be targeted it to the same migratable target as the migratable JMS server or SAF agent. As a best practice, a path service should use its own custom store and share the same target as the store.

MBean Attribute:


Specifies the path of the Replicated Store Global Directory.

This must be the same directory that is used to store the Daemon Cluster rs_daemons.cfg configuration file and requires a specially tuned NFS mount. Oracle recommends using an absolute directory path on a shared NFS mount.

MBean Attribute:

Changes take effect after you redeploy the module or restart the server.

Advanced Configuration Options

Name Description
Local Index

Specifies a local Daemon to attach to when a Daemon Cluster has multiple Daemons configured to run on the current node.

The local Daemon is chosen using the formula: ((localindex) modulo (number-of-local-daemons)). When 0, it always resolves to the first available Daemon entry in the rs_daemons.cfg file that has an address on the current node. The default value is 0.

This setting is not applicable to production environments. To ensure high availability, a Daemon Cluster in a production environment should have multiple nodes with one Daemon on each node.

MBean Attribute:

Minimum value: -1

Maximum value: 65535

Changes take effect after you redeploy the module or restart the server.

Region Size

The region size, in bytes.

Data is stored in one or more uniquely named Regions within a Daemon Cluster where each region is created with this size. Oracle recommends that regions sizes should be tuned to be a small fraction of the available local Daemon memory.

MBean Attribute:

Minimum value: 33554432

Maximum value: 1073741824

Changes take effect after you redeploy the module or restart the server.

IO Buffer Size

The I/O buffer size, in bytes, automatically rounded down to the nearest power of 2.

  • Controls the amount of WebLogic Server JVM off-heap (native) memory that is allocated for a replicated store.

  • For the best runtime performance, Oracle recommends setting IOBufferSize so that it is larger than the largest write (multiple concurrent store requests may be combined into a single write).

  • For the best boot recovery time performance of large stores, Oracle recommends setting IOBufferSize to at least 2 megabytes.

MBean Attribute:

Minimum value: -1

Maximum value: 67108864

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics

Back to Top