+

Search Tips   |   Advanced Search

MBeans Generic JMX

The MBeans generic JMX monitor can be used to set monitoring counters on the MBeans attributes available on a JMX server. The supported attribute types are:

There are various types of connection NeoLoad can use to communicate with the server JMX interface. Some Java application servers support two JMX interfaces. For example, the JBoss 4 and 5 servers have the regular interface of the server JVM and a server-specific interface. Both monitoring entry points provide different counters, and require specific types of connection:


Connection using a Java URL


Overview

This option allows NeoLoad to connect to any JMX server through a URL. This URL must be in the form

 service:jmx:rmi:///jndi/rmi://<host>:<port>/jmxrmi

where the <host> and <port> fields are respectively the IP address and port of the machine to be monitored.


Glass Fish connection


Supported versions

NeoLoad supports all GlassFish server versions, but some counters may not be available for versions 2.0.x and earlier.


Connection settings

Defining a monitor on a GlassFish server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 8686). The port is the GlassFish server JMX connection port.

In addition to these settings, a valid user account must be provided if authentication is enabled (same account than the one used to connect to GlassFish Administration Console). The default account is "admin" and the password "adminadmin".

To retrieve all the selected performance counters, NeoLoad requires the GlassFish server monitoring level to be set to "high". To display the server monitoring levels, enter the following command from the server bin directory:

asadmin get server.monitoring-service.module-monitoring-levels.*


server.monitoring-service.module-monitoring-levels.connector-connection-pool = OFF 


server.monitoring-service.module-monitoring-levels.connector-service = OFF


server.monitoring-service.module-monitoring-levels.ejb-Container = OFF


server.monitoring-service.module-monitoring-levels.http-service = OFF 


server.monitoring-service.module-monitoring-levels.jdbc-connection-pool = OFF


server.monitoring-service.module-monitoring-levels.jms-service = OFF 


server.monitoring-service.module-monitoring-levels.jvm = OFF 


server.monitoring-service.module-monitoring-levels.orb = OFF 


server.monitoring-service.module-monitoring-levels.thread-pool = OFF 


server.monitoring-service.module-monitoring-levels.transaction-service = OFF 


server.monitoring-service.module-monitoring-levels.web-Container = OFF



To change monitoring level, enter the following commands from the server bin directory:


asadmin set server.monitoring-service.module-monitoring-levels.connector-connection-pool=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.connector-connection-pool=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.connector-service=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.ejb-Container=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.http-service=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.jdbc-connection-pool=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.jms-service=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.jvm=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.orb=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.thread-pool=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.transaction-service=HIGH 


asadmin set server.monitoring-service.module-monitoring-levels.web-Container=HIGH



JBoss connection



The JBoss version 4 and 5 application servers support two JMX interfaces:






Standard Java JMX interface



No additional library is required. It is only necessary to open the JMX interface with the server start file.


set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"



A connection of URL Java type is required to monitor the interface with a URL like:


service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi



See Connection Using a Java URL.



Server-specific JMX interface



The counters available are listed in the page http://localhost:8080/jmx-console/.











Configuration



Before using a JBoss monitor, several of the JBoss server jars must be installed in NeoLoad jmxlib/jboss directory.

JBoss 4.x


To connect NeoLoad to JBoss 4.x, several of the JBoss server jars must be installed in NeoLoad jmxlib/jboss directory.



Copy to <neoload>/jmxlib/jboss directory the following files from the JBoss directory:





After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

JBoss 5.x 


To connect NeoLoad to JBoss 5.x, several of the JBoss server jars must be installed in NeoLoad jmxlib/jboss directory.



Copy to <neoload>/jmxlib/jboss directory the following files from the JBoss directory:





After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

JBoss 6.X and 7.0


Before creating a JBoss 6.X - 7.0 monitor, the JBoss server must be configured to accept JMX connections. In these versions, JBoss server uses a J2EE 6 -compatible connector. Using this configuration, no libraries need to be added to NeoLoad.







<!-- ... -->


    <interfaces>


        <!-- ... -->


        <interface name="public">


           <any-address/>


        </interface>


    </interfaces>




    <socket-binding-group name="standard-sockets" default-interface="public">


        <!-- ... -->


        <socket-binding name="jmx-connector-registry" interface="public" port="1090"/>


        <socket-binding name="jmx-connector-server" interface="public" port="1091"/>


        <!-- ... -->


    </socket-binding-group>


<!-- ... -->






Supported versions



Several JBoss server versions are supported, such as JBoss 4.0.X, JBoss 4.2.X, JBoss 5.X, JBoss 6.X and JBoss 7.X. NeoLoad automatically hides any counters that are not supported by a particular JBoss version.



Connection settings



Defining a connection to a JBoss server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 1099). The port is the JBoss server JNP connection port.



For JBoss 4.0.X and 4.2.X, connection port is the Port attribute in the Mbean referenced by org.jboss.naming.NamingService in the server\<your-jboss-instance>\conf\jboss-service.xml file.


<mbean code="org.jboss.naming.NamingService" 


      name="jboss:service=Naming" 


      xmbean-dd="resource:xmdesc/NamingService-xmbean.xml"> 


... 


      <!-- The listening port for the bootstrap JNP service. Set this to -1 


      to run the NamingService without the JNP invoker listening port. 


      --> 


      <attribute name="Port">1099</attribute> 


...



For JBoss 5.0.X, connection port is the Port attribute of the service named jboss:service=Naming in the server\<your-jboss-instance>\conf\bindings.xml file.


<!-- Naming Service --> 


<bean class="org.jboss.services.binding.ServiceBindingMetadata"> 


    <property name="serviceName">jboss:service=Naming</property> 


    <property name="bindingName">Port</property> 


    <property name="port">1099</property> 


</bean>



For JBoss 5.1.X, connection port is the Port attribute of the service named jboss:service=Naming in the server\<your-jboss-instance>\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml file.


<!-- Naming Service --> 


<bean class="org.jboss.services.binding.ServiceBindingMetadata"> 


    <property name="serviceName">jboss:service=Naming</property> 


    <property name="bindingName">Port</property> 


    <property name="port">1099</property> 


</bean>



If the JBoss server has been configured for secured JNP, a valid user account must be provided with which to connect to the JBoss Administration Console.









Jonas connection



Supported versions



NeoLoad supports all Jonas server versions marked as certified Java Enterprise Edition (J2EE).



Connection settings



Defining a monitor to a Jonas server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 1099). The port is the Jonas server RMI connection port.



In addition to these settings, a valid user account must be provided if authentication is enabled (same account than the one used to connect to Jonas Administration Console). By default authentication is not enabled.



LiveCycle Data Services connection



Supported versions



NeoLoad supports LiveCycle Data Services (LCDS) versions 2.6 and later.



Connection settings



Defining a monitor on a LiveCycle Data Services server requires the name or IP address of the machine to be monitored, as well as the connection port. The port is the JMX port that is configured to the Java Virtual Machine.



If the JMX connection has not been configured, add the following parameters to the application server start-up script:


-Dcom.sun.management.jmxremote=true 


-Dcom.sun.management.jmxremote.port=9004 


-Dcom.sun.management.jmxremote.authenticate=false 


-Dcom.sun.management.jmxremote.ssl=false



To enable authentication, or for more information about configuring the JMX connection, refer to the Sun documentation.



In addition to these settings, a valid user account must be provided if authentication is enabled (see com.sun.management.jmxremote.authenticate property).



SAP Net Weaver 7.0 connection



Supported versions



NeoLoad supports SAP net weaver Web Application Server versions 7.0.x and later.



Configuration



Before the SAP net weaver monitor can be used, several net weaver server jars need to be installed.



Copy the following files from the net weaver installation directory to the <neoload>/jmxlib/netweaver70 directory:





After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.



Connection settings



Defining a monitor on a SAP net weaver server requires the name or IP address of the machine to be monitored, as well as the connection port. The port is the SAP NetWeaver server access point for the P4 protocol. The port number can be retrieved using the SAP Management Console at: Management Console > SAP Systems > <SAP System name> > <SAP Instance name> > Access Points. The access point is named P4.



In addition to these settings, a valid user account must be provided if authentication is enabled (same account as the one used to connect to the SAP net weaver Administration Console).



SAP Net Weaver 7.1 connection



Supported versions



NeoLoad supports SAP NetWeaver Web Application Server versions 7.1.x and later.



Configuration



Before the SAP NetWeaver monitor can be used, several NetWeaver server jars need to be installed.



Copy the following files from the NetWeaver installation directory to the <neoload>/jmxlib/netweaver71 directory:





After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.



Connection settings



Defining a monitor on a SAP NetWeaver server requires the name or IP address of the machine to be monitored, as well as the connection port. The port is the SAP NetWeaver server access point for the P4 protocol. The port number can be retrieved using the SAP Management Console at: Management Console > SAP Systems > <SAP System name> > <SAP Instance name> > Access Points. The access point is named P4.



In addition to these settings, a valid user account must be provided if authentication is enabled (same account as the one used to connect to the SAP NetWeaver Administration Console).



Oracle Application Server 10.1.3 connection



Configuration



Before using an Oracle Application Server monitor, several of the Oracle Application Server jars must be installed in NeoLoad jmxlib/oas directory.



Copy the following files from the Oracle Application Server directory to <neoload>jmxlib/oas directory:





After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.






Supported versions



This monitor allows NeoLoad to access Oracle Application Server 10g 10.1.3 and higher.



Connection settings



Defining a connection to an Oracle Application Server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 6003). The application server connection port is configured in the file: <Server>/opmn/conf/opmn.xml,


<notification-server> <port local="6100" remote="6200" request="6003" /> ... </notification-server>



A valid user account must be provided in addition to these settings (same as the one used for connecting to the Oracle Application Server Management Console).













    

  1. Connect to the server management interface. The default URL is: http://<server>:8888/em

  2. Select the instance to be monitored.

  3. Click on the Administration tab.

  4. Select the Security > Security Providers task.

  5. Click Instance Level Realm.

  6. Select the Realms tab.

  7. In the Security Provider Attributes section, click on the number of realm users.

  8. Select the user to be used for monitoring.

  9. In the available roles, select "ascontrol_admin" and "oc4j-administrators" and add them to the user.

  10. Click Apply.

  11. Re-start the application server.




Tomcat 5.5/6.0/7.0/8.0 connection



Configuration



Before using a Tomcat monitor, it is required to enable JMX monitoring on the Tomcat server.



The list of options and how to configure JMX Remote in Java 5 can be found on the Sun website.





    

  1. Add the following parameters to the Tomcat startup script:

      

    • On Linux:

      export CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9004 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
      


    • On Windows:

      set CATALINA_OPTS=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9004 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
      


    

  2. To include authentication, add and configure the following parameters:

    -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password -Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access \
    


  3. Edit the access allow file $CATALINA_BASE/conf/jmxremote.access :

    MonitorRole readonly
    


    controlRole readwrite
    


  4. Edit the password file $CATALINA_BASE/conf/jmxremote.password :

    MonitorRole tomcat 
    


    controlRole tomcat
    







Connection settings



Defining a monitor to a Tomcat server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 9004). In addition to these settings, a valid user account must be provided if authentication is enabled.



Web Logic 8 connection



Configuration



Before using the WebLogic monitor, the WebLogic server jar must be installed in NeoLoad jmxlib/weblogic8 directory.



Copy the weblogic.jar file from the WebLogic server/lib directory to jmxlib/weblogic8 directory. After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.



Connection settings



Defining a monitor to a WebLogic server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 7001). In addition to these settings, the domain to be monitored must be provided, together with the valid user account used to connect to the WebLogic Administration Console.



Web Logic 9/10/11 connection



Configuration



Before using the WebLogic monitor, WebLogic server jars must be installed in NeoLoad.



    

  1. From the WebLogic directory, copy the following files:

      

    • <weblogic>/server/lib/wlclient.jar

    • <weblogic>/server/lib/wljmxclient.jar

    

  2. Paste the files in the directory below where XX stands for your WebLogic version:

     <install-dir>/jmxlib/weblogicXX
    


  3. Restart NeoLoad. 

    The files are automatically synchronized with the Monitoring Agent once the changes have been made.
    





Connection settings



Defining a monitor to a WebLogic Administration Server domain requires the name or IP address of the machine to be monitored, as well as the connection port of the Weblogic Administration Console (the default port is 7001). In addition to these settings, a valid user account must be provided with which to connect to the WebLogic Administration Console.



  • WebLogic 9/10/11 monitor connects to WebLogic Administration Server, so please make sure that the WebLogic Administration Server is running. If there is only one WebLogic Server, it will automatically act as a WebLogic Administration Server domain. If there are several WebLogic servers (with or without clustering), please start up the WebLogic Administration Server domain.
    


    WebSphere connection
    


    Configuration
    


    Before using the WebSphere monitor, several of the WebSphere server jars must be installed in NeoLoad jmxlib/websphere directory.
    


    WebSphere 6.0
    


    To connect NeoLoad to WebSphere 6.0, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:
    


      

    • <websphere>/AppServer/java/jre/lib/ibmcertpathprovider.jar

    • <websphere>/AppServer/java/jre/lib/ext/ibmjceprovider.jar

    • <websphere>/AppServer/etc/tmx4jTransform.jar

    • <websphere>/AppServer/lib/admin.jar

    • <websphere>/AppServer/lib/bootstrap.jar

    • <websphere>/AppServer/lib/classloader.jar

    • <websphere>/AppServer/lib/client.jar

    • <websphere>/AppServer/lib/emf.jar

    • <websphere>/AppServer/lib/ffdc.jar

    • <websphere>/AppServer/lib/idl.jar

    • <websphere>/AppServer/lib/iwsorb.jar

    • <websphere>/AppServer/lib/j2ee.jar

    • <websphere>/AppServer/lib/mail-impl.jar

    • <websphere>/AppServer/lib/management.jar

    • <websphere>/AppServer/lib/nls.jar

    • <websphere>/AppServer/lib/pmi.jar

    • <websphere>/AppServer/lib/pmij2ee.jar

    • <websphere>/AppServer/lib/ras.jar

    • <websphere>/AppServer/lib/runtime.jar

    • <websphere>/AppServer/lib/sas.jar

    • <websphere>/AppServer/lib/soap.jar

    • <websphere>/AppServer/lib/utils.jar

    • <websphere>/AppServer/lib/wasjmx.jar

    • <websphere>/AppServer/lib/wasproduct.jar

    • <websphere>/AppServer/lib/wsexception.jar

    • <websphere>/AppServer/lib/wsprofile.jar

    • <websphere>/AppServer/lib/wssec.jar

    • <websphere>/AppServer/lib/wssoap.jar

    • <websphere>/AppServer/lib/security.jar

    

    After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.
    


    WebSphere 6.1
    


    To connect NeoLoad to WebSphere 6.1, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:
    


      

    • <websphere>/AppServer/runtimes/com.ibm.ws.admin.client_6.1.0.jar

    • <websphere>/AppServer/runtimes/com.ibm.ws.webservices.thinclient_6.1.0.jar

    • <websphere>/AppServer/plugins/com.ibm.ws.runtime_6.1.0.jar

    • <websphere>/AppServer/lib/webadmin/management.jar

    • <websphere>/AppServer/etc/tmx4jTransform.jar

    

    With the FixPack 11 or later, it is required to copy also the following file:
    


      

    • AppServer\plugins\org.eclipse.osgi_*.jar

    

    After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.
    


    WebSphere 7.0
    


    To connect NeoLoad to WebSphere 7.0, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:
    


      

    • <websphere>/AppServer/runtimes/com.ibm.ws.admin.client_7.0.0.jar

    • <websphere>/AppServer/runtimes/com.ibm.ws.webservices.thinclient_7.0.0.jar

    • <websphere>/AppServer/plugins/com.ibm.ws.runtime.jar

    • <websphere>/AppServer/lib/webadmin/management.jar

    • <websphere>/AppServer/etc/tmx4jTransform.jar

    

    After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.
    


    Supported versions
    


    The WebSphere monitor supports WebSphere 6.0.X, WebSphere 6.1.X, WebSphere 7.0.X, WebSphere 8.0.X and WebSphere 8.5.X.
    


    Connection settings
    


    Defining a monitor for a WebSphere server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 8880). The port is the WebSphere server SOAP connection port (SOAP_CONNECTOR_ADDRESS in the administration console). In addition to these settings, a valid user account must be provided with which to connect to the WebSphere Administration Console.
    


      

    • Warning: NeoLoad requires the PMI interface to be enabled on the monitored WebSphere server. To activate it, click on the Servers > Application servers node in the administration console and select the desired server. Next, click on the Configuration tab and check the Enable Performance monitoring option. Click OK to confirm, and re-start the application server for the changes to take effect.

    




    Home