The Standardized Message Bus

Overview

The standardized message bus is analogous to the NMR in JBI. It provides a standard interface by which all services deployed into FUSE ESB interact. It normalizes messages and ensures they are delivered to the proper locations.

The message bus uses a WSDL-based messaging model to mediate the message exchanges between endpoints. Using a WSDL-based model provides the needed level of abstraction to ensure that the endpoints are fully decoupled. The WSDL-based model defines operations as a message exchange between a service provider and a service consumer. The message exchanges are defined from the point of view of the service provider and fit one of four message exchange patterns:

in-out: In this pattern a consumer sends a request message to a provider. The provider responds to the request with a response message. The provider may also respond with a fault message indicating that an error occurred during processing.
in-optional-out: In this pattern a consumer sends a request message to a provider. The provider may send a response message back to the consumer, but the consumer does not require a response. The provider may also respond with a fault message. In addition, the consumer can send a fault message to the provider.
in-only: In this pattern a consumer sends a message to a provider, but the provider does not send a response. The provider does not even send fault messages back to the consumer.
robust-in-only: In this pattern a consumer sends a message to a provider. The provider may send a fault message back to the consumer to signal an error condition, but otherwise does not respond to the consumer.

Normalized messages

In order to fully decouple the entities involved in message exchanges the bus uses normalized messages. A normalized message is a genericized format used to represent all of message data passed through the bus. It consists of three parts:

meta-data, properties: The meta-data holds information about the message. This information can include transaction contexts, security information, or other QoS information. The meta-data can also hold transport headers.
payload: The payload of a message is an XML document that conforms to the XML Schema definition in the WSDL document defining the message exchange. The XML document holds the substance of the message.
attachments: Attachments hold any binary data associated with the message. For example, an attachment could be an image file sent as an attachment to SOAP message.
security Subject: The security Subject holds security information, such as authentication credentials, associated with the message. For more information of the security Subject, see Sun's API documentation.

JBI binding components automatically normalizing all of the messages placed onto the bus. Binding components normalize messages received from external sources before passing them to the NMR, The binding component will also denormalize the message so that it is in the appropriate format for the external source. Non-JBI endpoints are responsible for normalizing and denormalizing messages on their own.