Tools 
SAP Management Console
In an SAP NetWeaver Application Server Java environment, the SAP Management Console is the established tool for system monitoring and management. Among a wide range of functionality, it includes several views and menu items that allow the user to perform many tasks related to the management of an SAP JVM. These tasks include:
Enabling and disabling of debugging
Dumping stack traces
Displaying the call stack of a selected thread
GC History with summary information about garbage collections (the last 20 GCs and the last 20 old generation GCs)
Displaying information about heap memory consumption
There are two flavors of the Management Console: the brwoser-based Java Management Console (SAP Management Console) and the Windows-based SAP Microsoft Management Console (SAP MMC), which has an in-built help.
jvmmon
The SAP JVM Monitoring Tool jvmmon is an SAP JVM specific tool for a wide range of monitoring tasks. It is part of the SAP JVM delivery and can be found in the same directory as the VM itself under the bin folder.
There are two flavors of this tool with similar functionality but different user interfaces: the command line based jvmmon (jvmmon.exe) and the graphical user interface jvmmon-gui (jvmmon-gui.exe).
Both can attach to a running SAP JVM – no matter if it is running in an application server environment or stand-alone – and display comprehensive monitoring information or control various aspects of the VM configuration. VMs running on the local host are found and listed without further preparation. To manage SAP JVMs on a remote host, a small daemon program, the jvmmond must be running on the remote host. This daemon will provide a network connection port for the monitoring tool to connect to, specify the used port at the jvmmond command line:
jvmmond [-port num]
Connect to this port by starting jvmmon with the command line options -hostname <hostname> -port <port> or using the Add cluster function of jvmmon-gui and entering the host and port number into the dialog box.
After selecting a running SAP JVM, a lot of information about the current state of this VM can be shown:
VM related information like version, platform, build information etc.
Stack traces, optionally enriched with additional descriptive information
Class statistics in detail or short summary
Information about the VM and the cluster memory consumption
Heap dump, optionally enriched with additional information
Information about the shared libraries loaded by the VM
Garbage Collection history information
Note
Note that while some of the above information can be found in the jvmmon itself, many of the jvmmon commands will trigger the VM to dump reports to the console or to trace files respectively.
Additionally, some actions can be performed on the selected VM, including:
Starting and stopping debugging on the fly
Setting trace flags to enable or disable specific trace output
Forcing a full garbage collection or a maximum compaction GC
Memory Analyzer
The Memory Analyzer (MAT) is a fast and feature-rich Java heap analyzer implemented as an Eclipse (or NWDS) plugin. It can help to find memory leaks and reduce memory consumption.
Memory Analyzer can work with heap dumps written by an SAP JVM. These heap dumps can be triggered on the fly, e.g. with the jvmmon tool, or optionally on specific events like OutOfMemoryErrors (see option -XX:+HeapDumpOnOutOfMemoryErrorin Non-standard Options).
Heap dumps can be manually inspected in detail and also automatically analyzed for problems by executing several reports. For example, use the “Leak Suspects” report to analyze memory leaks.
For more information about the Memory Analyzer, refer to the project home page http://www.eclipse.org/mat/.
Other tools
There are a lot of other valuable tools that can be used to monitor and manage applications running on the SAP JVM. As they are not specific to an SAP JVM, listing them here would go beyond the scope of this document.
The SAP JVM delivery includes a set of other tools known from the Sun JDK package, such as jconsole, jstat and jps. The usefulness of these tools in the Application Server Java environment is most probably limited and they are to be seen as experimental tool, provided “as-is” with no support from SAP.