Database Reference
In-Depth Information
Schema
Description
Monitoring
(BAM)
User Mes-
saging Ser-
vice
<ENV>_ORASDPM
JMS File Stores
Persistent stores host information such as JMS destinations. Though persistent
stores can either be file-based or JDBC-enabled (that is, saved in the database),
most Oracle SOA Suite
11g
high availability installations utilize file-based stores
for performance reasons. File-based stores essentially provide persistence cap-
abilities to Oracle WebLogic Server subsystems and services through the use of
a built-in, high performance storage solution.
Because these file-based persistent stores save JMS messages, durable sub-
scriber information, and temporary messages sent to unavailable destinations
by using the Store-and-Forward features, it is not possible to take consistent
backups of them. Restoring these persistent stores may result in data inconsist-
ency, even if they were backed up offline. These persistent stores often (and
should) reside on redundant fault-tolerant storage that is accessible to all nodes
of the Oracle SOA Suite
11g
cluster. Alternatively, you may have already used
JDBC-enabled stores for your JMS destinations so that they are maintained in
and backed up with the database.
