...
This page assumes you have read Working with Messaging to understand the basics of SMA messaging.
Understanding Message Dispatch
An application's Aep Engine creates and manages the lifecycle of the message buses that an application configures for use. When an application is configured to join one of more bus channels subscriptions will be issued on behalf of the application to attract messages. In this case Message dispatch occurs as follows:
- The message bus binding implementation receives a serialized, message provider specific message
- Using an application supplied message view factory (generated by ADM) and SMA message data also transported with the provider specific message, the bus wraps the serialized message in a view object (also ADM generated).
- Using message metadata transported with the message, the binding looks up the message channel on which to dispatch the received message.
- The message view is then wrapped in a MessageEvent along with its message channel and is then dispatched to the application's AepEngine where it is enqueued for processing.
- The AepEngine picks up the message event and dispatches to each application event handler that has a signature matching the message type.
- Once the AepEngine stabilizes the results of the application's message processing, a message acknowledgement is dispatched back to the binding.
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
Message Acknowledgement
Note |
---|
TODO diagram describing flow |
Expressing Interest
For an application to receive messages, it must:
...