With this monitor, you can perform availability monitoring for selected ABAP and Java systems and their instances. For ABAP systems, you can also monitor the availability of logon groups, and the most important performance attributes for the status of the dialog system are also displayed for the monitored ABAP instances.
For more information about selecting systems and application servers for monitoring, see Configuring Availability Monitoring.
Description of the Tree Structure of the Monitor
Prerequisites
Availability monitoring uses the standalone agent CCMSPING, you must therefore have performed the installation of the availability agent CCMSPING.
Features
Availability of Systems
For availability monitoring, CCMSPING checks the availability of the message server of the corresponding system. A system is regarded as available if the responsible message server responds to the availability agent’s query and at least one application server is registered as active with the message server. The system availability is monitored by one or more CCMSPING agents, depending on the configuration of your availability monitoring.
MTE Name | Meaning |
ABAP: Checked by | Availability of the system according to information from the responsible ABAP message server; checked by specified CCMSPING |
Java: Checked by | Availability of the system according to information from the responsible Java message server; checked by specified CCMSPING |
Release/Description | Additional information about the monitored system |
System Configuration |
In the case of ABAP+Java systems, if you have specified both message servers in the configuration of the availability monitoring, both availability values are displayed here.
Availability of ABAP Instances
The monitor displays the following MTEs for the monitored ABAP instances:
MTE Name | Meaning |
Instance Availability | Percentage value of the availability (reported active to the message server), by default averaged over the last 15 minutes |
Logon-Check Availability | Percentage value of the availability (server responds to RFC call), by default averaged over the last 15 minutes |
Logon-Check: RFC Error Message | Details for the Logon-Check Availability message |
Server Type | Type of the server; in this case: ABAP Application Server |
Dialog Response Time | Average response time for processing a dialog step |
Standardized Response Time | As Dialog Response Time, but for a predefined standard transaction |
Users Logged On | Number of users that are logged on to an application server |
For more information about the performance values for the dialog system, see Dialog Overview Monitor.
Availability of Java Instances
Java instances are displayed under different names, depending on which message server (ABAP or Java) is used for the availability monitoring of the system:
· In the case of monitoring purely using the ABAP message server, Java instances are displayed under the name of the assigned ABAP instance with the suffix :Java (such as: Host1_C11_00:Java). This is only possible if the relevant system is a double-stack system).
· In the case of monitoring using the Java message server, Java instances of the relevant system are displayed under their server ID with the prefix J2EE (such as J2EE7305550). This is also the case, if the monitoring is performed using both message servers.
The monitor displays the following MTEs for the monitored Java instances:
MTE Name | Meaning |
Instance Availability | Percentage value of the availability (reported active to the message server), by default averaged over the last 15 minutes |
Server Type | Type of the server; in this case: J2EE Application Server |
Host | Additional information about the Java instance |
HTTP Port | |
Available J2EE Server Nodes |
Availability of Logon Groups
In the case of ABAP systems, you can monitor logon groups for their availability. A logon group is regarded as available, if it is possible to log on to the application server with the best dialog system quality in this group. In addition to the availability of the logon groups in the last 15 minutes, the system also displays the application server of the group with the best dialog system quality in the monitor.
Analysis Method
If you double-click a node in this monitor, you start the analysis method Configure Availability and Performance Overview. (see Configuring Availability Monitoring).
Activities
To start the monitor, 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 CCMS Monitor Templates set.
3. Start the Availability and Performance Overview monitor from the list by double-clicking it.
No comments:
Post a Comment