Outbound Dequeue Scenario Messaging Scenarios

10-42 Oracle Fusion Middleware Users Guide for Technology Adapters

10.4.2.2 Message Format

You can specify the format for an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10–8 . The following message formats are supported: ■ No format name Default ■ Command server requestreply message ■ Type 1 command reply message ■ Type 2 command reply message ■ Dead letter header ■ Event message ■ User-defined message in programmable command format ■ Message consisting entirely of characters ■ Trigger message ■ Transmission queue header

10.4.2.3 Message Expiry

You can specify the expiry time for an outgoing message by using the Adapter Configuration Wizard, as shown in Figure 10–8 . The queue manager discards the message after the expiry time of a message has elapsed. If a message has expiration notification set, then a notification is generated when the message is discarded. The notification is sent to the queue specified in the replyToQueue parameter. By default, NEVER is set for the expiry field.

10.4.2.4 Message Priority

You can specify the priority of an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10–8 . A priority can be in the range of 0 low to 9 high. You can also specify the priority of the message to be taken from the default priority attribute, as defined by the destination queue. By default, AS_Q_DEF is set as message priority.

10.4.2.5 Message Persistence

You can specify the persistence of an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10–8 . If message persistence is not set, then a message is lost when the queue manager restarts or there is a system failure. If you set persistence for a message to true, then it means that the message will not be lost even if there is system failure or the queue manager is restarted. You can also specify the persistence of the message to be taken from the default priority attribute, as defined by the destination queue. Persistent messages are written to log files and queue data files. If a queue manager is restarted after a failure, it recovers these persistent messages from these files. Note: You can specify all these message properties at run time through message headers. You can use the assign activity to assign values to these properties. Oracle JCA Adapter for MQ Series 10-43

10.4.3 Correlation Schemas

Correlation is required for mapping a response to a request in a request-reply interaction. Each MQ Series request message contains a message ID and a correlation ID. When an application receives a request message from Oracle BPEL PM, it checks for the correlation schema defined for the response message. Based on the correlation schema, the application generates the message ID and correlation ID of the response message. The response page of the Adapter Configuration Wizard shown in Figure 10–15 enables you to specify the correlation schema for the response message. The Message ID box shown in Figure 10–15 provides the following options for the message ID of the response message: ■ Generate a new message ID for the response message. ■ Use the message ID of the request message. Similarly, the Correlation ID box shown in Figure 10–15 provides the following options for the correlation ID of the response message: ■ Use the message ID of the request message ■ Use the correlation ID of the request message

10.4.4 Distribution List Support

The Oracle MQ Series Adapter enables you to enqueue a message to multiple queues. When you select the Put Message Into MQ option in the Operation Type page and more than one queues, then the DistributionList parameter is automatically added to the JCA file.

10.4.5 Report Messages

The Oracle MQ Series Adapter enables you to set various types of acknowledgement messages on an outgoing message. These acknowledgement messages are known as report messages. A report message is generated, only if the criteria for generating that report message is met. When enqueuing a message on a queue, you can request for more than one type of report message. When you request for a report message, you must specify the queue name to which the report message will be sent. This queue is known as replyTo queue. A report message can be generated by a queue manager, a message channel, or an application. The Oracle MQ Series Adapter supports the following message reports: ■ Confirmation on Arrival The Confirmation on Arrival COA message indicates that the message has been delivered to the target queue manager. A COA message is generated by the queue manager. This message report can be selected in the Reports page of the Adapter Configuration page shown in Figure 10–14 . ■ Confirmation on Delivery A Confirmation on Delivery COD message indicates that the message has been retrieved by the receiving application. A COD message is generated by the queue manager. This message report can be selected in the Reports page shown in Figure 10–14 . ■ Exception Report