AppManager for JAVA on UNIX and Linux Servers 8.0 Release Notes

Date Published: June 2015

AppManager for JAVA on UNIX and Linux Servers (AppManager for JAVA) allows you to monitor and diagnose potential problems with Java resources running on local or remote UNIX, Linux, and Windows servers.

This release includes features implemented in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this module, log into the AppManager Module Upgrades & Trials page.

1.0 What’s New?

This release of AppManager for JAVA provides the following Knowledge Scripts:

  • Discovery_JAVA discovers Java resources running on local or remote UNIX, Linux, and Windows servers.

  • JAVA_ClassLoadingStats monitors the loading and unloading of classes on a Java Virtual Machine (JVM) by collecting data for loaded and unloaded class counts.

  • JAVA_ConnectorStats monitors connector request and error statistics for Apache Tomcat and JBoss servers. This script raises an event when the request rate or error rate exceeds the threshold you set.

  • JAVA_CPUUtil monitors JVM process CPU utilization and system CPU utilization. This script raises an event when JVM process CPU utilization or system CPU utilization exceeds the threshold you set.

  • JAVA_GarbageCollectorStats monitors JVM garbage collector statistics. This script raises an event when the time taken for a garbage collector run or the number of garbage collector runs that occur during a Knowledge Script interval exceed the thresholds you set.

  • JAVA_HeapUtil monitors memory heap utilization for a JVM. This script raises an event when the used heap as a percentage of committed heap exceeds the threshold you set.

  • JAVA_JBossTransactionStats monitors transaction rates for JBoss servers. This script raises an event when any of the transaction rate counters exceeds the threshold you set.

  • JAVA_JettyQueuedThreadPool monitors the queued thread count for a Jetty server. This script raises an event when the queued thread count exceeds the threshold you set.

  • JAVA_ManagedBeanUtil queries individual Java managed bean counters. This script raises an event when a Java bean query result contains or does not contain strings you specify, or when numeric data in the query result exceeds the thresholds you set.

  • JAVA_MemoryPools monitors memory pool usage for a JVM. This script raises an event when the memory pool usage exceeds the threshold you set.

  • JAVA_ThreadUtil monitors Java process thread pool utilization. This script collects data for JVM thread count, daemon thread count, and peak thread count.

  • JAVA_TomcatAppSessions monitors application session statistics for Apache Tomcat servers. This script raises an event when session creations or session expirations exceed the thresholds you set.

  • JAVA_TomcatThreadPoolStats monitors thread pool statistics for Apache Tomcat servers. This script raises an event when the current or busy thread counts exceed the thresholds you set.

To get the features provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.

2.0 System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AppManager for JAVA has the following system requirements:

  • Requires AppManager version 7.0 or later installed on the AppManager repository (QDB) computer and on all console computers.

  • One of the following versions of NetIQ UNIX agent installed the computers that will monitor remote JVM deployments (agent computers):

    • UNIX agent 8.0 with patch 8.0.0.1

    • UNIX agent 7.5 with patch 7.5.0.4

    • UNIX agent 7.2 with patch 7.2.0.13

    • UNIX agent 7.1 with patch 7.1.0.54

  • The download package contains a Jolokia WAR agent file. You must deploy this agent to each JVM that you wish to monitor. Each JVM product has its own procedure for deploying WAR files. Consult the documentation for your JVM as you deploy the Jolokia WAR agent.

For more information, see the AppManager for JAVA on UNIX and Linux Servers Management Guide, included in the download package.

3.0 Contents of the Download Package

AppManager for JAVA includes Knowledge Scripts to discover and monitor your Java resources. The download package includes these release notes, a management guide, help for Knowledge Scripts, and several files that are used during installation:

  • p71p54.zip, the patch file you install on any computers you want to monitor that have UNIX agent 7.1 installed.

  • p72p13.zip, the patch file you install on any computers you want to monitor that have UNIX agent 7.2 installed.

  • p75p4.zip, the patch file you install on any computers you want to monitor that have UNIX agent 7.5 installed.

  • p80p1.zip, the patch file you install on any computers you want to monitor that have UNIX agent 8.0 installed.

  • AM70-JAVA-8.0.81.0.msi, the module installer

  • AM70-JAVA-8.0.81.0.ini, a configuration file used with the AppManager setup program

When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.

4.0 Installing This Module

Run the module installer on all console computers to install the Help and console extensions. Run the module installer only once on each of these computers.

You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

IMPORTANT:Run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.

Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.

Deploy the Jolokia WAR agent to each JVM that you wish to monitor. Each JVM product has a different procedure for deploying WAR files. Consult the documentation for your JVM when deploying the Jolokia WAR agent. After deployment, configure the Jolokia URL in the Discovery_JAVA Knowledge Script to begin the discovery process.

For more information about installing this module, see the AppManager for JAVA on UNIX and Linux Servers Management Guide, included in the download package.

5.0 Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. If you need assistance with an issue, please contact Technical Support.

  • JAVA module agent patches do not support Linux on IBM Power Systems. The UNIX agent patches included with this release are not applicable to an AppManager UNIX agent running under Linux on IBM Power Systems.

  • Solaris x86 agent communications issues with deployed Jolokia WAR agent. The UNIX agent patch included in this release for a UNIX agent under Solaris x86 can experience communication issues with a deployed Jolokia WAR agent. There is no workaround.

6.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information website.

For general corporate and product information, see the NetIQ Corporate website.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.