Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-8801

Modify the JMX Connection Factory to allow fully customized URLs.

    XMLWordPrintable

    Details

    • Sprint:
      Horizon - April 5, Horizon - April 12th, Horizon - April 19th, Horizon - April 26th, Horizon - May 3rd

      Description

      There is a requirement to connect through JMX to a WAS 8.5.5.5 app server (IBM WebSphere 8.5), in order to monitor and collect data from it.

      According with the following link, the JMX URL has to be built on a certain way:

      http://www.monitis.com/blog/configuring-jmx-in-websphere-8-5/

      The following script works to successfully connect through JMX using JConsole:

      HOST=10.0.0.1 # Change this as needed
      PORT=9100 
      
      CLASSPATH=$JAVA_HOME/lib/jconsole.jar
      CLASSPATH=$CLASSPATH:$WAS_HOME/runtimes/com.ibm.ws.admin.client_8.5.0.jar
      CLASSPATH=$CLASSPATH:$WAS_HOME/runtimes/com.ibm.ws.ejb.thinclient_8.5.0.jar
      CLASSPATH=$CLASSPATH:$WAS_HOME/runtimes/com.ibm.ws.orb_8.5.0.jar
      
      $JAVA_HOME/bin/jconsole \
      -J-Djava.class.path=$CLASSPATH\
      -J$CLIENTSAS\
      -J$CLIENTSSL\
      service:jmx:iiop://$HOST:$PORT/jndi/JMXConnector
      

      As you can see, certain custom JARs are required in order to perform the JMX connection.

      We have to evaluate the impact of adding those JARs to $OPENNMS_HOME/lib, in order to understand the implications and the consequences of this, besides fixing the URL limitation issues.

        Attachments

          Activity

            People

            Assignee:
            mvr Markus von RĂ¼den
            Reporter:
            agalue Alejandro Galue
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: