[KIEKER-951] JMX MBean Access in the user guide

[rju]

JIRA Issue: KIEKER-951 JMX MBean Access in the user guide Original Reporter: Nils Christian Ehmke

---

The necessary properties to enable the access to the MBean has to be updated in the user guide (due to KIEKER-70 Done ). Currently it says

# Whether the MonitoringController will be available as an MBean.
kieker.monitoring.MBean=true

The property doesn't exist currently.

It also looks like more than one property has to be enabled (kieker.monitoring.jmx e.g.).

@jwa: Can you take a look at this and add/update the necessary property/properties?

Checklist:

[rju]

author Jan Waller -- Thu, 28 Mar 2013 17:15:09 +0100

Form kieker.monitoring.default.properties

## Whether any JMX functionality is available
kieker.monitoring.jmx=false
kieker.monitoring.jmx.domain=kieker.monitoring

## Enable/Disable the MonitoringController MBean
kieker.monitoring.jmx.MonitoringController=true
kieker.monitoring.jmx.MonitoringController.name=MonitoringController

## Controls JMX remote access
kieker.monitoring.jmx.remote=false
kieker.monitoring.jmx.remote.port=59999
kieker.monitoring.jmx.remote.name=JMXServer
## If the SUN-JMX Bootstrap class is not available, a fallback to the 
## default implementation can be used. The fallback solution prevents 
## the VM from terminating.
## A graceful shutdown is done by connecting to the JMXServer, there to
## kieker.monitoring.JMXServer and using the operation stop()
kieker.monitoring.jmx.remote.fallback=true
## These properties will be forwarded to configure the JMX server
com.sun.management.jmxremote.local.only=false
com.sun.management.jmxremote.authenticate=false
com.sun.management.jmxremote.ssl=false

So, yes, kieker.monitoring.jmx=true to enable and kieker.monitoring.jmx.remote=true if you want to access the server from remote.

[rju]

author Jan Waller -- Thu, 28 Mar 2013 17:21:23 +0100

Replying to [jwa|comment:1]:
> ... and kieker.monitoring.jmx.remote=true if you want to access the server from remote.

In this case you should strongly consider com.sun.management.jmxremote.authenticate=true. Refer to the sun documentation for details.

I think it is currently not possible to specify authentification for jmx remote other than sun jdk implementations.

[rju]

author nils-christian -- Thu, 28 Mar 2013 23:14:51 +0100

I modified the description in 094f5e5dd8f9f4c19c1e06b7dcb1b3063585f7a9. Any suggestion for an actual reference for the JMX remote access?

[rju]

author Jan Waller -- Fri, 29 Mar 2013 00:08:01 +0100

Replying to [nie|comment:3]:
> Any suggestion for an actual reference for the JMX remote access?

• http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html
• http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html

[rju]

author nils-christian -- Fri, 29 Mar 2013 11:10:51 +0100

I used the existing JMX reference instead of adding new ones now. Therefore: Done in 58eb2b0e7d2e8e88a46c6c6885a01b5aba5fe0bc.