anchor.diff:  </jmx-collection>
   ----
   
  -Once added to `etc/jmx-datacollection-config.xml` you can test it using the `collect` command available in the _Karaf Shell_:
  +===== 3rd Party JMX Services
   
  -[source]
  +Some java applications provide their own JMX implementation and require certain libraries to be present on the classpath, e.g. the java application server Wildfly.
  +In order to successfully collect data the following steps may be required:
  +
  +  * Place the jmx client lib to the $OPENNMS_HOME/lib folder (e.g. jboss-cli-client.jar)
  +  * Configure the JMX-Collector accordingly (see below)
  +  * Configure the collection accordingly (see above)
  +
  +.Example
  +[source, xml]
   ----
  -collection:collect org.opennms.netmgt.collectd.Jsr160Collector 127.0.0.1 collection=opennms-poller port=18980
  +<service name="JMX-WILDFLY" interval="300000" user-defined="false" status="on">
  +    <parameter key="url" value="service:jmx:http-remoting-jmx://${ipaddr}:9990"/>
  +    <parameter key="retry" value="2"/>
  +    <parameter key="timeout" value="3000"/>
  +    <parameter key="factory" value="PASSWORD-CLEAR"/>
  +    <parameter key="username" value="admin"/>
  +    <parameter key="password" value="admin"/>
  +    <parameter key="rrd-base-name" value="java"/>
  +    <parameter key="collection" value="jsr160"/>
  +    <parameter key="thresholding-enabled" value="true"/>
  +    <parameter key="ds-name" value="jmx-wildfly"/>
  +    <parameter key="friendly-name" value="jmx-wildfly"/>
  +</service>
  +<collector service="JMX-WILDFLY" class-name="org.opennms.netmgt.collectd.Jsr160Collector"/>
   ----
  
positive.code: |===
  | Class Name          | `org.opennms.netmgt.collectd.Jsr160Collector`
  | Package             | core
  | Supported on Minion | `Yes`
  |===
  
  ===== Collector Parameters
  
negative.code: 
  ==== JmxCollector
  
  The _JmxCollector_ is used to collect performance data via _JMX_.
  Attributes are extracted from the available _MBeans_.
  
  ===== Collector Facts
  