THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Unzip the archive to a suitable location.
Info title 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.
| Info | ||
|---|---|---|
| ||
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 (For full details see Management Console Security). This is no longer the case, with SSL encrypted RMI being the favored approach going forward. If you do not However, if you wish to connect to a JMXMP enabled broker then the following step is not required. If you do wish to connect to a broker configured to use JMXMP, then the console requires provision of the Optional sections of the JMX Remote API that are not included within the JavaSE platform, as with the broker. In order to make it available to the console, place the 'an older broker using JMXMP the console will support this so long as the jmxremote_optional.jar' (rename the file if any additional information is present in the file name) jar file within the 'plugins/jmxremote.sasl_1.0.1/' folder of the console release (on Mac OS X you will need to select 'Show package contents' from the context menu whilst selecting the management console bundle in order to reveal the inner file tree)is provided to it. For details see Management Console Security. |
Running the Qpid JMX Management Console
...