Supportability for Developments Under SAP
NetWeaver
If you want to create an application under SAP NetWeaver yourself, you need to ensure that the application can be monitored, that is, that you instrument the application for the standard SAP NetWeaver monitoring tools. Ensure that you have dealt with the following points, depending on whether your application is to run under AS ABP or AS Java:
The CCMS
monitoring infrastructure is the basis for monitoring across systems and
components. It collects values using data suppliers and sends them to a
central monitoring system using CCMS agents. If errors occur, alerts are
triggered, to which you can assign auto-reaction methods. You can display the
collected data in the
alert monitor
(transaction RZ20) or in
SAP NetWeaver
Administrator. This data also forms the basis for monitoring in the SAP
Solution Manager. You can also include analysis methods in the monitoring
infrastructure, with which you can perform a detailed investigation of the
corresponding component directly from the alert monitor.
To be able to meaningfully monitor an application with the monitoring infrastructure, at least the following information is required:
· Status of the application (such as active, configured, stopped, and so on)
· Availability or information about the current function of the application (Health Check); this should certainly include information about critical workload-dependent resources (such as available threads)
· Response time behavior or throughput for the application’s requests
· Number of requests that the application has processed per time unit, if a corresponding value is meaningful for this application
· Important events of the application as text messages (note, however, that you only have limited storage space available in the monitoring segment)
· Status of the communication interfaces of the application (if they exist)
· Information about caches (such as hits, quality) that the application uses
· Information that should be written when the application is started:
¡ Date and time of the start
¡ Version (or Release, Build, or Patch Level) of the component
¡ All configuration parameters of the application (such as configuration files, and, under Microsoft Windows, the entries in the registry)
¡ Operating system environment variables used
To instrument the application for the monitoring infrastructure, you need to perform the following steps:
· Write a data supplier that collected the above data for the application and transfers it to the monitoring infrastructure. For more information, see the document Writing a Data Supplier.
To download the document, start the SAP Developer Network (http://sdn.sap.com), and go to the SAP NetWeaver Developers' Guide Quick Link. Choose Application Development ® System Management ® System Management Development, and in the ABAP System Management area, select the specified document.
·
This
information should be displayed in a separate Alert Monitor monitor. In the
case of components with multiple instances, the instance-dependent information
should form a separate subtree in each case. For information about creating
corresponding monitor definitions, see
Editing Monitors and
Monitor Sets.
· You should connect Java applications to the monitoring framework of SAP NetWeaver using JMX, that is, the application should deliver the most important data about its current status, in the same way as above (see Developing and Enhancing the Java Monitoring Framework with JMX).
·
You should
monitor the availability of the application using the Generic Request and
Message Generator (GRMG). For more information, see
GRMG: Instrumenting an
Application.
·
The
application must use the logging infrastructure of the J2EE Engine. For more
information, see
How to Write Useful
Log and Trace Messages.
All of this monitoring data is automatically transferred to the CCMS and is therefore also available centrally in the Alert Monitor or in the SAP NetWeaver Administrator.
