Oracle Fusion Middleware Directory Structure

16-10 Oracle Fusion Middleware Administrators Guide lost messages are messages that were enqueued before or after the system restore point time, but never processed. Use the following procedure before recovery to drain messages in the JMS queue after persistent-store recovery to avoid processing duplicate messages: 1. Log into the Oracle WebLogic Server Administration Console. 2. Before recovery, configure JMS server to pause Production, Insertion, and consumption operations at boot time to ensure that no new messages are produced or inserted into the destination or consumed from the destination before you drain stale messages. To do this: a. Expand Services, then Messaging, and then click JMS Servers. b. On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing. c. On the Configuration: General page, click Advanced to define the message pausing options. Select Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup. d. Click Save. Use the following procedure after recovery: 1. After recovering the persistent store, start the Managed Servers. 2. Drain the stale messages from JMS destinations, by taking the following steps: a. Expand Services, then Messaging, and then JMS Modules. b. Select a JMS module, then select a target. c. Select Monitoring, then Show Messages. 3. Click Delete All. 4. Resume operations, by taking the following steps: a. Expand Services, then Messaging, and then JMS Servers. b. On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing. c. On the Configuration: General page, click Advanced. Deselect Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup. d. Click Save. If the store is not dedicated to JMS use, use the Oracle WebLogic Server JMS message management administrative tool. This tool can perform import, export, move, and delete operations from the Administration Console, MBeans, and WLST. For applications that use publish and subscribe in addition to queuing, you should manipulate topic subscriptions in addition to queues. Note: Do not drain and discard messages without first being certain that the messages contain no data that must be preserved. The recovered messages may include unprocessed messages with important application data, in addition to duplicate messages that have already been processed.