Oracle MQ Series Adapter Integration with Mediator

10-8 Oracle Fusion Middleware Users Guide for Technology Adapters CodedCharSetId MQLONG Coded character set identifier. Representation of any character data in the portion of the message following MQRFH2 the next header, or the message data following this header. Format MQCHAR8 Format name. Format name for the portion of the message following MQRFH2. Flags MQLONG Flags. MQRFH_NO_FLAGS =0. No flags set. NameValueCCSID MQLONG The coded character set identifier CCSID for the NameValueData character strings contained in this header. The NameValueData may be coded in a character set that differs from the other character strings that are contained in the header StrucID and Format. If the NameValueCCSID field is a 2-byte Unicode CCSID 1200, 13488, or 17584, then the byte order of the Unicode CCSID is the same as the byte ordering of the numeric fields in MQRFH2. For example, Version, StrucLength, and NameValueCCSID itself. The NameValueCCSID field may take only values from Table 10–3 :

10.3.1.2 Variable Portion

The variable portion follows the fixed portion. The variable portion contains a variable number of MQRFH2 folders. Each folder contains a variable number of elements or properties. The related properties are grouped together. The MQRFH2 header can contain the following message service folders: The mcd folder This contains properties that describe the shape or format of the message. For example, the Msd property identifies the message as being Text, Bytes, Stream. Map, Object, or Null. This folder is always present in JMS MQRFH2. The jms folder This is used to transport JMS header fields, and JMSX properties that cannot be fully expressed in the MQMD. This folder is always present in a JMS MQRFH2. Table 10–3 Possible Values for NameValueCCSID Field Value Meaning 1200 UCS2 open-ended 1208 UTF8 13488 UCS2 2.0 subset 17584 UCS2 2.1 subset includes the Euro symbol Oracle JCA Adapter for MQ Series 10-9 The usr folder This is used to transport any application-defined properties associated with the message. This folder is only present if the application has set some application-defined properties. The psc folder This is used to convey publishsubscribe command messages to the broker. Only one psc folder is allowed in the NameValueData field. The pscr folder This is used to contain information from the broker, in response to publishsubscribe command messages. Only one pscr folder is present in a response message. Table 10–4 shows a full list of property names. The syntax used to express the properties in the variable portion is as follows: NameValueLength MQLONG Length, in bytes, of the NameValueData string that immediately follows this length field. It does not include its own length. The value set into NameValueLength is always a multiple of 4. The NameValueData field is padded with space characters to achieve this. NameValueData MQCHARn A single character string, whose length in bytes is given by the preceding NameValueLength field. It contains a folder holding a sequence of properties. Each Table 10–4 MQRFH2 Folders and Properties Used by JMS JMS Field Name Java Type MQRFH2 Folder name Property Name Typevalues JMSDestination Destination jms Dst string JMSExpiration long jms Exp i8 JMSPriority int jms Pri i4 JMSDeliveryMode int jms Dlv i4 JMSCorrelationID String jms Cid string JMSReplyTo Destination jms Rto string JMSTimestamp long jms Tms i8 JMSType String mcd Type, Set, Fmt string JMSXGroupID String jms Gid string JMSXGroupSeq int jms Seq i4 xxx User Defined Any usr xxx any mcd Msd jms_none jms_text jms_bytes jms_map jms_stream jms_object