10.16 JMX console
The Daisy repository server offers a JMX (Java Management Extensions) console through which certain things can be monitored or certain settings can be changed at runtime. In JMX, the components that provide this management access are called MBeans. The MBeans of the embedded ActiveMQ server are also visible through the same JMX console.
To access the JMX console, simply point your browser to
The JMX console listens by default only to requests from localhost. See below for how to change this.
You will be prompted for a password. Daisy automatically generates a password for accessing the JMX console during the Daisy installation. You can find this password in the <daisydata dir>/conf/myconfig.xml file, look for the following element:
<httpAdaptor port="9264" host="localhost" authenticationMethod="basic" username="daisyjmx" password="..."/>
Use the username and password mentioned on this element to log in. You can of course change these settings.
The repository server needs to be restarted for changes to the myconfig.xml to take effect.
If you want to be able to access the JMX console from non-localhost, simply change the value of the host attribute to the host name to which it should listen. To listen to all host names, use the value 0.0.0.0.
As you will see in the myconfig.xml, there's also an xmlHttpAdaptor, listening on port 9265, which is exactly the same as the HTTP adaptor, except that it returns XML responses instead of HTML. This can be useful for programmatic access to JMX.
Daisy reuses the default JMX MBean server of the Java VM, and hence you can also use Java's jconsole tool to browse Daisy's MBeans. This requires passing the following options to the repository server VM: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false