Which three methods does WebLogic provide to implement persistent JMS messaging?
A.
Create a file store and assign it to a JMS server.
B.
Create a JDBC store and assign it to a JMS server.
C.
Configure a file store within a JMS module.
D.
Configure the domain’s default store.
E.
Use the target server’s default store.
Explanation:
A: The main steps for creating a custom file store are as follows:
1.Create a directory where the file store’s data will be persisted.
2.Create a custom file store and specify the directory location that you created.
3.Associate the custom file store with the subsystem(s) or migratable target that will be accessing
it, such as:
*For JMS servers, select the custom file store on the General Configuration page.
*For Store-and-Forward agents, select the custom file store on the General Configuration page.
*For a Path Service, select the custom file store on the General Configuration page.B: The main steps for creating a JDBC store are as follows:
Create a JDBC data source or multi data source to interface with the JDBC store.
Create a JDBC store and associate it with the JDBC data source or multi data source.
It is highly recommended that you configure the Prefix option to a unique value for each configured
JDBC store table.
Associate the JDBC store with the subsystem(s) that will be using it, such as:
For JMS servers, select the JDBC store on the General Configuration page.
For Store-and-Forward agents, select the JDBC store on the General Configuration page.
For a Path Service, select the custom file store on the General Configuration page.
E: Each server instance, including the administration server, has a default persistent store that
requires no configuration.
Note:
When a persistent message is sent, it is stored in the WebLogic Persistent Store.
The 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-enabled database.
Note 2: A persistent message is guaranteed to be delivered once-and-only-once. The message
cannot be lost due to a JMS provider failure and it must not be delivered twice. It is not considered
sent until it has been safely written to a file or database. WebLogic JMS writes persistent
messages to a WebLogic persistent store (disk-base file or JDBC-accessible database) that is
optionally targeted by each JMS server during configuration.
Reference: Using the WebLogic Persistent Store