[CONF] Apache Qpid > Configuring Qpid JMX Management Console

[confluence]

Configuring Qpid JMX Management Console Page edited by Robbie Gemmell Configuring Qpid JMX Management Console Qpid has a JMX management interface that exposes a number of components of the running broker. You can find out more about the features exposed by the JMX interfaces here. Installing the Qpid JMX Management Console Unzip the archive to a suitable location. SSL encrypted connections Recent versions of the broker can make use of SSL to encrypt their RMI based JMX connections. If a broker being connected to is making use of this ability then additional console configuration may be required, particularly when using self-signed certificates. See Management Console Security for details. JMXMP based connections In previous releases of Qpid (M4 and below) the broker JMX connections could make use of the JMXMPConnector for additional security over its default RMI based JMX configuration. This is no longer the case, with SSL encrypted RMI being the favored approach going forward. However, if you wish to connect to an older broker using JMXMP the console will support this so long as the jmxremote_optional.jar file is provided to it. For details see Management Console Security. Running the Qpid JMX Management Console The console can be started in the following way, depending on platform: Windows: by running the 'qpidmc.exe' executable file. Linux: by running the 'qpidmc' executable. Mac OS X: by launching the consoles application bundle (.app file). Using the Qpid JMX Management Console Please see Qpid JMX Management Console User Guide for details on using this Eclipse RCP application. Using JConsole See JConsole Using HermesJMS HermesJMS also offers integration with the Qpid management interfaces. You can get instructions and more information from http://wiki.apache.org/qpid/HermesJMS. Using MC4J MC4J is an alternative management tool. It provide a richer "dashboard" that can customise the raw MBeans. Installation First download and install MC4J for your platform. Version 1.2 beta 9 is the latest version that has been tested. Copy the directory blaze/java/management/mc4j into the directory <MC4J-Installation>/dashboards Configuration You should create a connection the JVM to be managed. Using the Management->Create Server Connection menu option. The connection URL should be of the form: service:jmx:rmi:///jndi/rmi://localhost:8999/jmxrmi making the appropriate host and post changes. Operation You can view tabular summaries of the queues, exchanges and connections using the Global Dashboards->QPID tree view. To drill down on individual beans you can right click on the bean. This will show any available graphs too. Change Notification Preferences View Online | View Change | Add Comment --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:commits-subscr...@qpid.apache.org