How service integration converts messages to and from IBM MQ format

Messages are converted between IBM MQ format and service integration format as they flow between the two systems.

透過服務整合及 IBM MQ

通常,您不需要知道訊息格式之間的轉換,就能夠在服務整合與 IBM MQ 之間交換 JMS 訊息,因為服務整合會自動執行適當的轉換,其中包括字元或數值編碼。 不過,如果您的 JMS 應用程式未依照預期運作,或您的服務整合配置包括 JMS 程式,或包括處理送往或來自非 JMS IBM MQ 程式之訊息的調解,您可能需要瞭解訊息的轉換。

如果您的服務整合應用程式會與 IBM MQ 應用程式交換 MapMessage 物件,您可能需要指定非預設的對映訊息編碼格式。

When service integration converts messages to and from IBM MQ format

Service integration converts a service integration message into a IBM MQ message in the following circumstances:
  • When service integration sends a message to IBM MQ by using a WebSphere® MQ link.
  • When a service integration mediation places the message on a queue point that is a IBM MQ queue.
  • When a service integration application sends the message to a destination where the mediation point (if any) or the queue point (if there is no mediation) is a IBM MQ queue.
Service integration converts a IBM MQ message into a service integration message in the following circumstances:
  • When IBM MQ sends the message to a service integration bus by using a WebSphere MQ link.
  • When a service integration mediation receives the message from a mediation point that is a IBM MQ queue.
  • When a service integration application receives the message from a destination where the queue point is a IBM MQ queue.
When you use the IBM MQ messaging provider, there is no conversion between IBM MQ format and service integration format.

Overview of message conversion

When service integration converts a message to IBM MQ format, it usually constructs a IBM MQ message descriptor (MQMD), a rules and formatting header 2 (MQRFH2), and a message payload:
  • Message descriptor (MQMD): Service integration sets fields in the MQMD based on the service integration message header fields and properties; these include JMS message header fields and properties applicable to the message. Service integration always constructs an MQMD.
  • Rules and formatting header 2 (MQRFH2): Service integration sets fields in the MQRFH2 based on the service integration message header fields and properties. Some IBM MQ applications cannot process messages that contain an MQRFH2. To simplify interoperation, you can configure service integration to omit the MQRFH2 from messages for applications that cannot process the MQRFH2. However, be aware that when service integration omits the MQRFH2, it discards the corresponding service integration header fields and properties.
  • Message payload: Service integration uses the body of the service integration message (if any) as the payload of the IBM MQ message.
When service integration converts a message from IBM MQ format:
  • It sets the service integration message header fields and properties from the MQMD and (if present) the MQRFH2 in the IBM MQ message.
  • It sets the service integration message body to the contents (if any) of the IBM MQ message that immediately follow the MQRFH2.
  • If the message contains other headers, instead of, or as well as, the MQRFH2 header, those headers are treated as part of the JMS message body and the JMS message becomes a bytes message.
Figure 1. Message conversion to and from IBM MQ format
This figure is described in the surrounding text.

For reference information about the mappings for specific message header fields and properties between a service integration bus and IBM MQ, see the topics listed in the related reference. To help you program applications that interoperate with IBM MQ, these topics describe how the message formats are mapped between service integration messages and IBM MQ messages.


指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:10
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cjc0019_
檔名:cjc0019_.html