The WebLogic Server 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 temporarily store messages sent using the Store-and-Forward feature. The persistent store supports persistence to a file-based store or to a JDBC-accessible store in a database. See Using the WebLogic Persistent Store in Administering the WebLogic Persistent Store.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following sections:
This section describes how to create new persistent stores. It includes the following tasks:
On the General Settings page, define the general configuration settings for your new JDBC store:
Name: enter a name for the JDBC store.
Scope: specify the scope in which you would like this new persistent store to be created.
Data Source: select a data source or click Create a New Data Source to create a new data source for this JDBC store. For more information on creating data sources, see Create JDBC data sources.
Prefix Name: specify a prefix name to prepend to the table name in this JDBC store for use with multiple instance
For more information on these fields, see Configuration Options.
On the Targets page, select the server instances and clusters on which you want to deploy the JDBC store.
On the High Availability page, define the high availability settings for your new JDBC store:
Distribution Policy: specify if the file store is a singleton or is distributed.
Migration Policy: specify the migration policy to be used by the file store.
For more information on these fields, see Configuration Options.
On the General Settings page, define the general configuration settings for your new file store:
Name: enter a name for the file store.
Scope: specify the scope in which you would like this new persistent store to be created.
Directory: enter the pathname to the directory on the file system where the file store is kept. This directory must exist on your system, so be sure to create it before completing this page.
For more information on these fields, see Configuration Options.
On the Targets page, select the server instances and clusters on which you want to deploy the file store.
On the High Availability page, define the high availability settings for your new file store:
Distribution Policy: specify if the file store is a singleton or is distributed.
Migration Policy: specify the migration policy to be used by the file store.
For more information on these fields, see Configuration Options.
To monitor all persistent stores created for the current domain:
To monitor all persistent stores created for a specific server instance:
A file store is a file-based repository for storing subsystem data, such as persistent JMS messages or durable subscriber information.
This section includes the following tasks:
A JDBC store is a JDBC-accessible database for storing subsystem data, such as persistent JMS messages and durable subscriber information.
This section includes the following tasks:
A replicated store is an in-memory based repository for storing subsystem data, such as persistent JMS messages or durable subscriber information.
This section includes the following tasks:
This section describes how to monitor and configure default stores, both static and dynamic. This section includes the following tasks:
To view monitoring information of a default store for configured server:
To configure a specific default store for configured server:
To view monitoring information of a default store for dynamic server: