Partilhar via

What are the XPIPELINE_MESSAGETYPE and XPIPELINE_REQUESTMESSAGETYPE properties

  • Artigo

While working with Service Bus EAI and EDI Labs, both as part of the Enterprise Application Integration project as well as the TPM Portal, we come across a couple of properties that are by default promoted on any given message. These two properties are:

  • XPIPELINE_MESSAGETYPE
  • XPIPELINE_REQUESTMESSAGETYPE

 

XPIPELINE_REQUESTMESSAGETYPE

This property contains the message type of the message when the bridge first receives the message.

XPIPELINE_MESSAGETYPE

This property contains the message type of the message at any given point of time while the bridge processes the message. A message goes through some transformations at different stages of the bridge. For example, a message might get transformed during the Transform stage and hence it would message type would change. The XPIPELINE_MESSAGETYPE property contains this most recent message type for the message.

How are these useful?

These properties are used by the stages/activities within the bridge to take actions appropriately. The stages/activities do not need to now look into a message and figure out the message type. Instead they could simply use the value of these properties. For example, depending on the value of the XPIPELINE_REQUESTMESSAGETYPE, the Transform activity decides what transforms should be made available to the user for selection. The Transform stage shows only those transforms that the have the message type of the source message same as the value of the XPIPELINE_REQUESTMESSAGETYPE.

Also, for an end user, these properties can be used while configuring the Route action. You can read more about route actions at the following link:

Comments