This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit


This section explains how the Message EIP can be implemented using WSO2 ESB. The following topics are covered:

Introduction to Message

In an enterprise that uses Message Channels to connect between two different applications, you must package information as a data set. Data sets facilitate information transmission from one application to another. The Message EIP is used as the transfer medium in this case. A message has two parts: a header and a body. A header holds information about the data being transmitted, its origin, and its destination. A body holds the actual data.

For more information on the Message EIP, refer to




Figure 1: Message EIP

How WSO2 ESB supports the Message EIP

As described in Messaging Bridge, irrespective of the format of a request you send from the client application, WSO2 ESB transforms the message into a SOAP envelope, which adheres to the Message EIP. The following code segment illustrates the transformed message of a typical request. Notice that it has a header and a body.

<soapenv:Envelope xmlns:soapenv="" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">

  <soapenv:Header />