anchor.diff:  
   ==== JmxCollector
   
  -The _JmxCollector_ is used to collect performance data through via _JMX_.
  +The _JmxCollector_ is used to collect performance data via _JMX_.
   Attributes are extracted from the available _MBeans_.
   
   ===== Collector Facts
  
positive.code: | Parameter              | Description                                                                     | Required | Default value
  | `collection`           | The name of the _JMX Collection_ to use                                         | required | (none)
  | `thresholding-enabled` | Whether collected performance data shall be tested against thresholds           | optional | `true`
  | `port`                 | JMX port. Also usedto lookup the MbeanServer configuration in `jmx-config.xml`  | optional | 1099
  | `retry`                | Number of retries                                                               | optional | 3
  | `friendlyName`         | Name of the path in which the metrics should be stored                          | optional | Value of the port, or the 'jsr160' if no port is set.
  | `factory`              | Set this to `PASSWORD-CLEAR` if credentials are required                        | optional | STANDARD
  | `protocol`             | Protocol used in the `JMX` connection string                                    | optional | rmi
  | `urlPath`              | Path used in `JMX` connection string                                            | optional | /jmxrmi
  | `rmiServerPort`        | RMI port.                                                                       | optional | 45444
  | `remoteJMX`            | Use an alternative `JMX` URL scheme                                             | optional | `false`
  |===
  
  ===== JDBC Collection Configuration
  
  _JMX Collections_ are defined in the `etc/jmx-datacollection-config.xml` and `etc/jmx-datacollection-config.d/`.
  
  
negative.code: </jmx-collection>
  ----
  
  ===== 3rd Party JMX Services
  
  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]
  ----
  <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"/>
  ----
  