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) or to a JDBC-enabled database (JDBC Store). See Using the WebLogic Persistent Store.
In a clustered server environment, a user-defined file store or JDBC store can targeted to a migratable target. A migratable target is a special target that can serve as a grouping of migratable JMS services, such as a JMS server or a SAF agent , and which is active on only server member in a WebLogic cluster. In a cluster, a recommended best practice is to target a persistent store to a migratable target, so that a member server will not be a single point of failure. This way the migratable store, along with the JMS services that use it to store their data, can be manually migrated from an unhealthy server onto a healthy server, either in the event of server crash or for scheduled maintenance.
After you finish
You do not need to restart the Administration Server after creating and initially configuring a store. However, if you modify an existing file store, you must restart the Administration Server.