<p>The disk write policy that determines how the file store writes data
to disk.</p>
<p>This policy also affects the JMS file store's performance,
scalability, and reliability. The valid policy options are:</p>
<ul>
<li>
<code>Direct-Write</code> 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.
</li>
<li>
<code>Disabled</code> 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.
</li>
<li>
<code>Cache-Flush</code> 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.
</li>
</ul>
(Interface=weblogic.management.configuration.JMSFileStoreMBean Attribute=getSynchronousWritePolicy)