LibraryToggle FramesPrintFeedback

Simplified Administration

Fuse ESB Enterprise's messaging service provides many ways to manage and administer a messaging system.

Advisory messages

Act as administrative channels from which you can receive status on events taking place on the broker and on producers, consumers, and destinations in real time. Using the broker's advisory messages, you can monitor the messaging system using regular JMS messages, which are generated on system-defined topics (see Dead letter queue). You can also use advisory messages to modify an application's behavior dynamically.

For details, see ActiveMQ in Action (Snyder, Bosanac, and Davies).

Interceptor plug-ins

Fuse ESB Enterprise's messaging service provides several plug-ins for visualizing broker components and for logging and retrieving statistics collected on a running broker.

  • Authentication—Two plug-ins provide different types of authentication: Simple authentication and JAAS authentication.

  • Central timestamp—Updates the timestamp on messages as they arrive at the broker. Useful when clients' system clocks are out-of-sync with the broker's clock.

  • Enhanced logging—Enables you to log messages sent or acknowledged on the broker.

  • Statistics—Provides statistics about running brokers and about destinations.

  • Visualization—Two plug-ins generate graph files for different broker components. You can display these graphs using several publicly available visualization tools.

For more information, see ActiveMQ in Action (Snyder, Bosanac, and Davies).

JMX

Fuse ESB Enterprise's messaging service provides extensive support for monitoring and controlling the broker's behavior from a JMX console, such as jConsole.

For details, see ActiveMQ in Action (Snyder, Bosanac, and Davies).

Web Console

The Web Console is a web-based administration tool used to monitor the status of the broker. Combined with Fuse ESB Enterprise's JMX support, the Web Console displays details about a broker, such as system usage, queues, topics and advisory messages, subscribers, connections and protocols, scheduled messages, delayed and scheduled deliveries, and so on.

For details, see ActiveMQ in Action (Snyder, Bosanac, and Davies).

Comments powered by Disqus