Messages Types Message 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 10-44 Oracle Fusion Middleware Users Guide for Technology Adapters An exception report is generated when a message cannot be delivered to the specified destination queue. Exception reports are generated by the message channel. This message report can be selected in the Reports page of the Adapter Configuration page shown in Figure 10–14 . ■ Expiry Report An expiry report indicates that the message was discarded because the expiry time specified for the message elapsed before the message was retrieved. An expiry report is generated by a queue manager. This message report can be selected in the Reports page of the Adapter Configuration page shown in Figure 10–14 . ■ Positive Action Notification A Positive Action Notification PAN indicates that a request has been successfully processed. It means that the action requested in the message has been performed successfully. This type of report is generated by the application. ■ Negative Action Notification A Negative Action Notification NAN indicates that a request has not been successfully serviced. It means that the action requested in the message has not been performed successfully. This type of report is generated by the application. You can specify whether all these report messages except PAN and NAN should contain the complete original message, a part of the original message, or no part of the original message. You can select one of the following options in the Adapter Configuration Wizard: ■ No data from the original message ■ The first 100 bytes of data in the original message ■ The entire original message

10.4.6 Message Delivery Failure Options

The Message Delivery Failure options are supported only for remote queues and not for normal queues. The Oracle MQ Series Adapter enables you to specify the action that should be taken in case a message could not be delivered to the destination queue. You can specify one of the following actions: ■ Place message on a dead letter queue This is the default action. A message is placed on a dead-letter queue if it cannot be delivered to the destination queue. A report message is generated if requested by the sender. ■ Discard message This indicates that the message should be discarded if it cannot be delivered to the destination queue. A report message is generated if requested by the sender. You can specify these options by selecting the Put Message To MQ option in the Adapter Configuration Wizard.

10.4.7 Message Segmentation

The Oracle MQ Series Adapter supports message segmentation for both inbound and outbound interactions. Segmentation is required when the size of a message is greater than the message size allowed for a queue. A physical message is divided into two or more logical messages. All logical messages have the same group ID and a sequence number, and an offset.