In the Alert Monitor, you can find a number of monitor sets delivered by SAP. These contain the most important monitors that allow you to easily monitor your IT landscape. The monitor set SAP J2EE Monitor Templates contains the most important monitors for monitoring AS Java. This is done from the local system. You can either use the monitors from this set directly or as templates for your own monitors (more information: Copying, Renaming, and Deleting Monitors ).
Setting Up GRMG Monitoring of the J2EE Engine
Setting Up GRMG Monitoring of the Portal Infrastructure
Setting Up GRMG Monitoring of the SAP NetWeaver Business Warehouse
The SAP J2EE Monitor Templates monitor set contains the following monitors:
Monitor |
Topic |
Adobe Document Services |
This monitor contains availability and configuration data for the Adobe Document Services . |
All Systems |
This monitor contains the contents of the following monitors in this set: Engines,Applications,Logfiles,Operating System, andCCMS Selfmonitoring (see below). |
Applications |
This monitor contains monitored data for Java applications. By default, this monitor contains a subtree for monitoring the table buffer. |
BI UDC Systems |
This monitor contains availability data for various BI components that is collected using GRMG. |
CCMS Selfmonitoring |
The content of this monitor corresponds to the monitor with the same name in the SAP CCMS Technical Expert Monitors monitor set, but contains data not for the local system, but for all systems in the system group J2EE_Systems. More information: CCMS Selfmonitoring Monitor . |
Engine Kernel |
This monitor contains precise information about monitored Java Engine Managers (more information: Kernel ). |
Engine Performance |
This monitor contains information about the performance of services and applications (more information: Performance ). |
Engine Services |
This monitor contains precise information about monitored Java Engine Services (more information: Services ). |
Engine System |
This monitor contains important system parameters. |
Engines |
This monitor contains the contents of the following monitors in this set: Engine Kernel,Engine Performance,Engine Services, and Engine System (see above). |
Engines: OS processes |
This monitor displays monitored Java processes at operating system level: those of the running dispatcher, server, and the Software Deployment Manager (SDM). The process monitoring of the operating system collector SAPOSCOL is used to do this (more information: Monitoring Selected Processes with SAPOSCOL ). |
Heartbeat |
This monitor contains availability data for various components that is collected using GRMG. Note that you must first activate availability monitoring of these components. |
Use this monitor to display the most important information about all monitored Java instances. The information is taken from the Java Startup Framework; you can also display it in the SAP Management Console . |
|
Logfiles |
Use this monitor to monitor AS Java log files using CCMS agents. |
Operating System |
The content of this monitor corresponds to the monitor with the same name in the SAP CCMS Monitor Templates monitor set, but contains data not for the local system, but for all systems in the system group J2EE_Systems. More information: Operating System Monitor . |
To start one of these monitors, follow the procedure below:
You cannot change monitors delivered by SAP. However, to use one of the monitors in this set as a template for your own monitor, first copy the desired monitor.
With SAP NetWeaver 7.0 SPS 07, various Java monitors were deactivated by default, meaning that only the most important nodes are provided with values. Values of inactive monitors are not transferred to the alert monitor by CCMS agents. If you already monitored a Java system centrally before this Support Package status, the relevant nodes of these Java monitors are no longer updated. For these nodes:
To delete the inactive nodes in the monitors of the set SAP J2EE Monitor Templates, proceed as follows:
The deleted subtrees are automatically recreated without the deactivated nodes.