WebSphere Message Service Client for C/C++, Version 2.0.2 Operating Systems: AIX, Linux, Solaris, Windows

XMSC_WMQ_MESSAGE_BODY

Data type:
xmsINT
Property of:
Destination

This property determines whether a XMS application processes the MQRFH2 of a WebSphere MQ message as part of the message payload (that is, as part of the message body).

Note: When sending messages to a destination, XMSC_WMQ_MESSAGE_BODY property supersedes existing XMS Destination property XMSC_WMQ_TARGET_CLIENT.

Valid values for this property are:

XMSC_WMQ_MESSAGE_BODY_JMS
Receive: The inbound XMS message type and body are determined by the contents of the MQRFH2 (if present) or the MQMD (if there is no MQRFH2) in the received MQ message.
Send: The outbound XMS message body contains a pre-pended and auto-generated MQRFH2 header based on XMS Message properties and header fields.
XMSC_WMQ_MESSAGE_BODY_MQ
Receive: The inbound XMS message type is always ByteMessage, irrespective of the contents of received WebSphere MQ message or the format field of the received MQMD. The XMS message body is the unaltered message data returned by the underlying messaging provider API call. The character set and encoding of the data in the message body is determined by the CodedCharSetId and Encoding fields of the MQMD. The format of the data in the message body is determined by the Format field of the MQMD.
Send: The outbound XMS message body contains the application payload as-is; and no auto-generated WMQ header is added to the body.
XMSC_WMQ_MESSAGE_BODY_UNSPECIFIED
Receive: The XMS client determines a suitable value for this property. On receive path, this is simply WMQ_MESSAGE_BODY_JMS property value.
Send: The XMS client determines a suitable value for this property. On send path, this is the value of XMSC_WMQ_TARGET_CLIENT property.

By default this property is set to XMSC_WMQ_MESSAGE_BODY_UNSPECIFIED.

Note: This property is not relevant only when an application connects to Service integration bus

Reference topic

Terms of Use | Rate this page

Last updated: 24 May 2011

(C) Copyright IBM Corporation 2005, 2011. All Rights Reserved.