Dequeue Message Messaging Scenarios

Oracle JCA Adapter for MQ Series 10-21 1. Receives message from Oracle BPEL PM. 2. Formats the XML content as specified at design time in the Adapter Configuration Wizard. 3. Sets properties and a correlation schema on the request message. 4. Sends the message to the queue specified at design time. The third-party application receives the message, processes it, generates the response, and then enqueues the response message to the replyTo queue specified in the request message. The Correlation ID and Message ID of the response message are generated on the basis of the correlation schema specified in the request message. 5. The Oracle MQ Series Adapter dequeues the message from the replyTo queue. 6. Sends the response to the non-initiating receive activity of Mediator. To ensure that response is sent to the correct BPEL instance, correlation schemas are used. Figure 10–12 displays the operation type that you must select in the Adapter Configuration Wizard. Figure 10–12 Selecting an Operation Type The page that appears after selecting the Send Message to MQ and Get ReplyReports operation type is shown in Figure 10–13 . 10-22 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 10–13 Send Message to MQ and Get ReplyReports Page You can specify the following properties in this page: ■ Message Type : The type of the message. You can either send a normal message or a request message. ■ Get Reports : Select this option if you want any kind of report. You can specify the type of report in the next page, as shown in Figure 10–14 . ■ Queue Name : The name of the queue to which the Oracle MQ Series Adapter enqueues the message. This is a mandatory field. ■ Queue Manager : The name of the queue manager to which the queue belongs. This field is optional. ■ Message Format : The format of the message. ■ Priority : The priority of the message ranging from 0 low to 9 high. ■ Persistence : The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue. ■ Delivery Failure : If the delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded. ■ Allow Messages to Be Segmented When Necessary : This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in more than one message. ■ Expiry : The expiry time of the message. The message is discarded after the expiry time has elapsed. For more information about these properties, see Section 10.4.2, Message Properties and Section 10.4.5, Report Messages .