Based on Apache ActiveMQ, Fuse ESB Enterprise's messaging service provides a JMS 1.1-compliant messaging system, consisting of a messaging broker and client-side libraries that enable remote communication among distributed client applications. The service's messaging broker handles:
Message exchanges between messaging clients by managing the transport connections used for communicating with messaging clients and the transports used for communicating with other message brokers.
Connections to database and file system stores for persistent messages.
Monitoring and management of various components of the messaging system, and so on.
In a messaging system, client applications send or receive messages—producers create and send messages, while consumers receive and process them. JMS clients use the JMS API to interact with the messaging service, and non-JMS clients use any of Fuse ESB Enterprise's other client APIs to interact with it.
Messages are the means by which client applications transmit business data and events. Messages can contain either textual or binary content and metadata, which provides additional information about the message. Applications can use message metadata programmatically to modify or fine tune message delivery or administratively to monitor the health of the messaging system.
 |  |  |
 |
