Page History

Configuring Qpid Management Console

QPID has Qpid has a JMX management interface that exposes . By default the management interface is enabled but it can also be disabled by modifying the management element in config.xml.

When starting the broker, the following system properties need to be set by setting the environment variable QPID_OPTS:

Note that you should only use these settings for non-production systems. For production deployments you should use authentication !

a number of components of the running broker.
You can find out more about the features exposed by the Qpid JMS interfaces here.JMX interfaces here.

Connection Configuration

The JMX connection can have an additional security enabled using additional Sun BCL classes. For full details see Management Console Security.

Note: If the additional security is enabled then the standard JConsole will be unable to connect to the Qpid Broker.

Using Eclipse RCP

Installing the Qpid Management Console

...

1. Unzip the

...

1. archive to a suitable location.
2. Set the environment variable QPIDMC_HOME to installation dir

...

1. .

...

Running the Qpid Management Console

...

For running on windows there are two options:To run this application on windows, run any of these scripts-

• qpidmc.bat (

...

• CMD)
• qpidmc.

...

• sh (

...

• Cygwin)

...

For running on unix, use the scritps for particular windowing system:
qpidmc_<windowing system>.sh (eg. qpidmc_motif.sh)

Using the Qpid Management Console

...

Please see attachment  for User Guide for using this Eclipse RCP.   Attchment The guide contains some of the screenshots of Qpid Management Console (Eclipse RCP) and an description of what the features are.

Using JConsole

JConsole is a management tool that comes with the Java Runtime Environment and provides a very simple view of managed beans. It requires no special configuration to be used with QPID.

...