1. Create a file named jmxnames.js in the configuration directory and add the following JavaScript to it:

   /**	
   * Adds a type attribute to the name of a JMX Beans.	
   * 
   * @param beanclass The bean class name	
   * @param domain The domain name	
   * @param names The name strings 
   * 
   * @return The name string	
   */	
   function objectNameFor(beanclass, domain, names) 
   {	
   var type = beanclass == null ? "*" : beanclass.substring(beanclass.lastIndexOf('.') + 1); 
   var out;	
   /*	
   * The names array always has 2 elements.	
   */	
   out = domain + ":" + "component=" + escape(names[0]) + ",name=" + escape(names[1]);	
   for (var i = 2; i < names.length; i++)	
   {	
   var index = i-1	
   out += "," + "name" + index + "=" + escape(names[i]);	
   }	
   return out + ",type=" + type;	
   }	
   

2. Add the following line to the director.properties file:

   management.namemaker.scriptfile = jmxnames.js

3. Restart the EDQ application server.

   The JMX Beans will now include a type qualifier at the end of their names.

Each real-time Web service registers an MBean for its reader and one for its writer in the JMX tree.

Readers are registered at:

Runtime/Data/Buckets/Realtime/Projects/Project Name/readers/Web service name

Writers are registered at:

Runtime/Data/Buckets/Realtime/Projects/Project Name/writers/Web service name

In each case, the path to the MBean includes the name of the Web service that owns it and the project that contains the web service.

Global Web services (those deployed in a .jar file in the oedq_local_home/webservices directory) have a different path name. Simply replace Projects/Project Name in the path above with Global.

The port for the internal JMX server is controlled by the management.port property, defined in the director.properties file.

A general JMX console, such as JConsole, can be used to interact with MBeans. Each MBean exposes:

• Attributes, whose values can be read.

• Operations that can be invoked to perform some action with the MBean.

• An interface that allows clients to subscribe to notifications of events that occur on the MBean.

The EDQ real-time web service MBeans uses the following attributes:

The EDQ real-time web service MBeans exposes the following operation:

An MBean that has a REST interface includes additional attributes in the MBean descriptor. These can be viewed in JConsole. Here's an example for a realtime reader MBean:

The web.path attribute is the path used after http://server/edq to access the MBean. The web.permission attribute displays the permission required to access the MBean.

The following MBeans are web-enabled in 14.1.2.0.0:

The REST API for MBeans allows you to do the following:

• Read MBean attribute(s)
• Set MBean attribute
• Invoke MBean operation

Read MBean attribute(s)

GET http://server:port/edq/mbeanpath[?attributes=attr1,attr2]

The mbeanpath component is the MBean web path mentioned in Web Enabled MBeans. The optional attributes parameter lists the attributes to return. If omitted, all attributes are returned.

The result is a JSON object containing the attribute values.

For example, to get the active and open attributes for a the web service named summer in project rt, the URL would be: http://server:port/edq/management/mbeans/Runtime/Data/Buckets/realtime/Projects/rt/readers/summer?attributes=active,open

And the result might be:

{ "active": 0,
  "open": 0
}

Set MBean attribute

POST http://server:port/edq/mbeanpath/setattribute

The payload is a JSON object containing these attributes:

The result is a JSON object containing the attribute previousvalue set to the previous value of the MBean attribute.

For example, to set the runtime thread count to 4, the URL would be:

http://server:port/edq/management/mbeans/Runtime/Engine

And the payload would be:

{ "attribute": "processThreads",
  "value": 4
}

Invoke MBean operation

POST http://server:port/edq/mbeanpath/invoke

The payload is a JSON object containing these attributes:

The result is a JSON object containing the attribute result set to the result of the call.

For example, to set the log level for case management searches to FINEST, the URL would be:

http://server:port/edq/management/mbeans/Logging/Case%20Management%20Filter%20Execution

And the payload would be:

{ "operation": "setLevel",
  "arguments": ["FINEST"]
}

This corresponds to adding the following to logging.properties.

com.datanomic.director.casemanagement.search.level = finest

Logging MBeans use the "display name" of the logger in the path, while logging.properties uses the internal package names. You can see the MBean package in the MBean module attribute by accessing the MBean JConsole on a running EDQ server edq | Logging | Case Management Filter Execution.