Synchronous Request-Response Oracle BPEL PM As Server

10-28 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 10–19 Get Message from MQ and Send ReplyReports Page When you click Next in the Get Message from MQ and send ReplyReports page, the Response page shown in Figure 10–20 is displayed. Figure 10–20 Response Page for Synchronous Request-Response You can specify the following properties in the Response page: ■ Message Type : The message type of the message to be dequeued. This option will have an effect on the return message type. ■ Message Format : The format of the message. Oracle JCA Adapter for MQ Series 10-29 ■ Priority : The priority of the message. ■ 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. For more information about these properties, see Section 10.4.2, Message Properties . Click Next in the Response page, the Messages page is displayed, as shown in Figure 10–16 . You can perform the following tasks in this page: ■ Specify if native format translation is not required. ■ Select the XSD schema file for translation. ■ Start the Native Format Builder wizard to create an XSD file from file formats such as CSV, fixed-length, DTD, and COBOL Copybook. For more information about the Messages page, see Section 10.4.1.1, Enqueue Message .

10.4.1.5 Asynchronous Request-Response Oracle BPEL PM As Server

In Oracle BPEL PM initiated request-response interaction, a BPEL process receives a request as an inbound message, processes it, and then sends the response through an invoke activity. For asynchronous request-reply scenario, the Oracle MQ Series Adapter performs the following operations:

1. Dequeues the message from the queue when a message arrives.

2. Reads and translates the message based on the translation logic defined at design

time. 3. Publishes the message as an XML message to Oracle BPEL PM. The Oracle BPEL PM processes the request and sends the response to the Oracle MQ Series Adapter. 4. Receives messages from Oracle BPEL PM. 5. Formats the XML content as specified at design time. 6. Sets the properties of the message, such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard. 7. Sends the message to the queue specified at design time in the Adapter Configuration Wizard. Figure 10–21 shows a sample BPEL process for this scenario. 10-30 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 10–21 Asynchronous Request-Response Oracle BPEL PM As Server Sample Figure 10–22 displays the operation type that you must select in the Adapter Configuration Wizard. Oracle JCA Adapter for MQ Series 10-31 Figure 10–22 Operation Type Page Selection for Request-Response Asynchronous Interaction The page that appears after selecting the Get Message from MQ and send ReplyReports operation type is shown in Figure 10–19 . Specify the queue name from which the Oracle MQ Series Adapter will dequeue the message in this page. When you click Next in the Get Message from MQ and send ReplyReports page, the Response page shown in Figure 10–20 is displayed. You can specify the following properties in the Response page: ■ Message Type : The message type of the message to be dequeued. This option will have an effect on the return message type. ■ Message Format : The format of the message. ■ Priority : The priority of the message. ■ 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. For more information about these properties, see Section 10.4.2, Message Properties . The page that is displayed when you click Next in the Get Message to MQ and Send ReplyReports page is a Response page shown in Figure 10–23 and Figure 10–24 but with two different set of options.