How to open the IBM Cash Drawer Manual

How to Configure Monitoring for Java Applications

  • 5 minutes to read

There are four general steps involved in setting up monitoring of Java applications:

  1. Importing and Configuring the Management Pack for Java Enterprise Edition (JEE)

  2. Import the management pack for performance monitoring for Java applications

  3. Manually deploy the performance monitoring agent for Java applications

  4. Verify the deployment of the Java application performance monitoring agent

Import and configure the Management Pack for Java Enterprise Edition

  1. Import and configure the Management Pack for Java Enterprise Edition (JEE), including installing the BeanSpy application. The performance monitoring for Java applications does not work without the configured JEE management pack and the installed BeanSpy application.

    Important

    The Management Pack for JEE supports various application servers; however, monitoring of Java applications only supports Tomcat.

    Download the Management Pack for JEE and the Management Pack for JEE Guide. This management pack enables monitoring of JEE application servers and is available for IBM WebSphere, Oracle WebLogic, Red Hat JBoss and Apache Tomcat. Go to System Center Management Pack for Java Enterprise Edition (JEE) on the Microsoft Download Center, click Download, and then select the files that you want to download. Example: Select the Management Pack (SC2012OM_JEE_MP.msi) and then select the Management Pack for Tomcat manual (OpsMgr_MP_Tomcat.docx).

    Important

    Make sure to download the appropriate Management Pack Guide (DOCX file) for the application server you are using. The guide contains information on installing the management pack and a description of the items to be monitored.

    For example, the System Center Management Pack for Tomcat enables IT administrators to monitor the health of JEE application server instances in Operations Manager. This management pack also includes the option to deploy BeanSpy. BeanSpy is an open source technology from Microsoft that provides comprehensive monitoring, including memory usage.

  2. After importing the management packs for JEE application servers, the instances of the Tomcat application servers are automatically determined. The discovery interval is set to 4 hours by default. The determination can therefore take up to 4 hours. For Operations Manager to be able to discover an application server the first time, an application server must be running on Tomcat. Once an application server instance is discovered, the configuration is only removed if the application server is uninstalled.

    To monitor the Tomcat application server instances, click in the Operations Console monitoring, expand the options one by one Application monitoring, Java monitoring, JEE application server and Tomcat application server, and then select the watch folder you want. For more information, see the Tomcat Management Pack Guide or the JEE Monitoring Management Pack Guide that you downloaded.

  3. Follow the steps to deploy BeanSpy to an application server. BeanSpy is an open source technology from Microsoft that uses the Java Management Extension (JMX). This provides the monitoring package with detailed information from the application server instances.

  4. Follow the instructions in the Management Pack for JEE Guide to enable full audit mode.

Import the management pack for performance monitoring for Java applications

  1. After the management pack for Java Enterprise Edition has been imported and configured, and BeanSpy has been deployed, import the management pack for Java application performance monitoring. Download the management pack from the Microsoft Download Center.

  2. The Java Application Performance Monitoring Management Pack (JavaAPMManagementPack.msi) contains the following files:

    • Microsoft.JEE.APM.Library.mpb

    • Microsoft.JEE.Tomcat.APM.Library.mp

    • Microsoft.JEE.Tomcat.5.Apm.mp

    • Microsoft.JEE.Tomcat.6.Apm.mp

    • Microsoft.JEE.Tomcat.7.Apm.mp

    Import the following library management packs:

    • Microsoft.JEE.APM.Library.mpb

    • Microsoft.JEE.Tomcat.APM.Library.mp

  3. Import the management packs for the appropriate versions of the Tomcat application servers you want to monitor.

    • Microsoft.JEE.Tomcat.5.Apm.mp

    • Microsoft.JEE.Tomcat.6.Apm.mp

    • Microsoft.JEE.Tomcat.7.Apm.mp

Manually deploy the performance monitoring agent for Java applications and enable performance monitoring for Java applications

  1. After the Management Pack for Java Enterprise Edition (JEE) has been configured through Full Monitoring and the Management Pack for Java Application Performance Monitoring has been imported, you can manually deploy the Java Application Performance Monitoring agent. To view the application servers that you configured for monitoring, click under monitoring on configuration.

  2. To enable performance monitoring for Java applications, click in the area monitoring under Tasks on Comprehensively monitored configurationsand select an application server for comprehensive monitoring.

  3. After you have selected an application server on which to enable performance monitoring for Java applications, click in the area Tasks under Monitored application server instance tasks on Extract APM Jar file. This extracts the Java agent files either to the monitored computer (for a Windows server) or to the gateway or management server (for a Linux server). In the task output you can see on which computer and in which directory the files were extracted. For more information, see the Management Pack for Java Application Performance Monitoring Guide.

  4. Next, you will reconfigure the Java application server. To enable performance monitoring for Java applications, set command line options that use the jar files as a class loader and restart the application. After the agent is installed, a rediscovery enables application performance monitoring.

Verify agent deployment for application performance monitoring and override monitors

  1. To verify that the application performance monitor is monitoring an application, right-click an application. Various performance counters are listed: Requests monitored / sec, average request time, performance events / sec, exception events / sec, and the values ​​for each counter. Five monitors apply to these indicators. For more information about monitors, see the Management Pack for Performance Monitoring for Java Applications Guide.

    Important

    If no values ​​are displayed for the performance counters, application performance monitoring is not enabled for those applications. This means you may have to wait for an application performance monitor to be discovered.

  2. To view the monitors in Health Explorer, right-click an application, click to open and then on Performance view. Some monitors are disabled.

  3. To override monitors, in the Health Explorer, right-click a monitor and click Monitor properties. Click on the side properties of the monitor on the tab Overrides on Overrideand select the rule that you want to override. On the website Override properties you can enable / disable monitors and change the threshold settings for monitors.

View events using application diagnostics

You can use application diagnostics, as well as performance monitoring for .NET applications, to view information about performance monitoring events for Java applications. For information about opening and using Application Diagnostics, see Working with the Application Diagnostics Console and Working with Events Using Application Diagnostics.

Because of the way Java statistics are reported, some of the standard application performance monitoring reports do not apply to Java application performance monitoring. You may see some of the report columns N / A displayed. Application performance monitoring does not apply to these columns. Also, many server-level reports do not contain data because of the way Java application containers are mapped to servers.

Is this page helpful?