Monitor Set SAP J2EE Monitor
Templates
Purpose
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).
Integration
●
Monitors in this
set display data for the systems in the system group J2EE_Systems. These are the Java systems for which a CCMS
agent has been registered with the local system (more information:
Installing an Agent on
a Java Instance (Java Standalone System) and
Installing an Agent on
a Java Instance (Dual-Stack System)). The monitored Java system is entered
in the specified system group during registration.
● In the case of the monitors Adobe Document Services, BI UDC Systems, and Heartbeat, availability data is displayed for the Java systems. This is determined using the GRMG. For this, you also need to activate the GRMG availability monitoring for the monitored components. More information, depending on the monitored component:
Setting Up GRMG Monitoring of the J2EE Engine
Setting Up GRMG Monitoring of the Portal Infrastructure
Setting Up GRMG Monitoring of the Business Warehouse
Configuring GRMG Availability for the Adobe Document Services
TREX: Availability
Monitoring (Heartbeat/GRMG)
Features
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
|
All Systems |
This monitor contains the contents of the following monitors in this set: Engines, Applications, Logfiles, Operating System, and CCMS Selfmonitoring (see below). |
Applications |
This monitor contains monitored data for Java applications. By default, this monitor contains a subtree for monitoring the table buffers (more information: Table Buffers Monitor). |
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:
|
Engine Performance |
This monitor
contains information about the performance of services and applications (more
information:
|
Engine Services |
This monitor
contains precise information about monitored Java Engine Services (more
information:
|
Engine System |
This monitor
contains all important system parameters (more information:
|
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
|
|
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:
...
1. Start the Alert Monitor using transaction RZ20 or choose CCMS → Control/Monitoring → Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP J2EE Monitor Templates set.
3. Start the desired monitor from the list by double-clicking it.
Restrictions
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.
Deactivated Monitors
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 (more information: Active and Inactive Monitors). 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:
● The nodes are displayed in gray with the information Value is obsolete in the alert monitoring tree.
● The nodes continue to require space in the shared memory of the monitoring segment.
To delete the inactive nodes in the monitors of the set SAP J2EE Monitor Templates, proceed as follows:
...
1. Activate maintenance functions by choosing Extras → Activate Maintenance Functions.
2. Start the All Systems monitor from the SAP J2EE Monitor Templates monitor set.
3. Expand any system and the subtrees J2EE Engines and J2EE Applications. Then select a subtree with the following naming convention:
○ <SysID> <System Number> Disp <ID> <host name>
○ <SysID> <System Number> Serv <ID> <host name>
○ <SysID> <System Number> Appl <ID> <host name>
4. Delete these subtrees by choosing Edit → Node (MTE) → Delete.. Use Option 4.
The deleted subtrees are automatically recreated without the deactivated nodes.