Introduction to JMX Programming for Message Queue Clients

While Oracle GlassFish Server Message Queue’s Administration Console and command line administration utilities allow an administrator to interactively configure and monitor Message Queue resources (such as brokers, connections, and destinations), these tools are not accessible from within a running client application.

To provide programmatic access to such administrative functions, Message Queue also incorporates an application programming interface based on the Java Management Extensions (JMX). Client applications can use this JMX API to programmatically perform the configuration and monitoring operations that are available interactively through the Administration Console and command line utilities.

You can use Message Queue’s JMX API in your client applications for a variety of purposes:

• To optimize performance by monitoring the usage of brokers and other Message Queue resources and reconfiguring their parameters based on the results

• To automate regular maintenance tasks, rolling upgrades, and so forth

• To write your own utility applications to replace or enhance standard Message Queue tools such as the Broker utility (imqbrokerd) and Command utility (imqcmd)

In addition, since JMX is the Java standard for building management applications and is widely used for managing J2EE infrastructure, you can use it to incorporate your Message Queue client as part of a larger J2EE deployment using a standard management framework throughout.