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 custom persistent store can targeted to a migratable target, then it can be manually migrated from an unhealthy server onto a healthy server, in the event of server crash or for scheduled maintenance. Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host a pinned service, such as a JMS server or a SAF agent that rely on the custom store to store their data. A user-defined store can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services. See Custom Store Availability for JMS Services.
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.