This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Service Message Objects

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The Service Message Object (SMO) provides an abstraction layer for processing and manipulating messages exchanged between services.
Data passing through mediation flows is represented by the SMO. The SMO is considered to be an envelope containing the following groups of data:
  • Context information (data other than the message payload and headers).
  • Header information associated with the message. For example, Java™ Message Service (JMS) headers if a message has been conveyed using the JMS API, or MQ headers if the messages has come from WebSphere® MQ.
  • The body of the message: the message payload, is the application data exchanged between service endpoints.
  • Message attachments

The SMO is a DataObject and its content can be accessed via the Service Data Object API (SDO API). SDO is a standard for representing structured business data. The body of the SMO contains a business object representing the application payload.