Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# File Store: Configuration

Configuration Options Related Tasks Related Topics

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

#### Configuration Options

Name | Description
--- | ---
Name | The name of this file store. This name must be unique within the WebLogic Server instance or its cluster.
Synchronous Write Policy | The disk write policy that determines how the file store writes data to disk. This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are: `Direct-Write` File store writes are written directly to disk. This policy is supported on Solaris, HP-UX, and Windows. On Windows systems, this option generally performs faster than the Cache-Flush option writes. `Disabled` Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be more than 100 times faster than the other policies, but power outages or operating system failures can cause lost and/or duplicate messages. `Cache-Flush` Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.
Target | The list of all WebLogic Server instances that have been defined in the current domain and are therefore candidates for hosting this file store. MBean Attribute: `PersistentStoreMBean.Targets`
Directory | The path name to the file system directory where the file store maintains its data files. This attribute is not dynamically configurable. MBean Attribute: `FileStoreMBean.Directory` Changes take effect after you redeploy the module or restart the server.
Logical Name | The name used by subsystems to refer to different stores on different servers using the same name. For example, an EJB that uses the timer service may refer to its store using the logical name, and this name may be valid on multiple servers in the same cluster, even if each server has a store with a different physical name. Multiple stores in the same domain or the same cluster may share the same logical name. However, a given logical name may not be assigned to more than one store on the same server. MBean Attribute: `FileStoreMBean.LogicalName`

Related Tasks

- Create file stores

Related Topics

- Using the WebLogic Persistent Store