Comment on page
SAP J2EE Server Monitoring
IT-Conductor can proactively monitor and optimize critical performance metrics of Java applications and servers to easily identify issues before impacting the business. When a system is added to IT-Conductor, all application servers and services related to the system are automatically discovered.
In the Administrator dashboard, navigate to SAP J2EE Systems.
Figure 1: SAP J2EE Systems in Administrator Dashboard
The page will show the list of all SAP Java Servers defined in IT-Conductor.
Figure 2: Sample List of SAP J2EE Servers
Clicking into the <Server Name>, all the previously configured inputs added to IT-Conductor for monitoring will be shown. Host Name and System Number are the basic connectivity requirements to monitor the Java Server and need to be added to the server configuration.
Figure 3: SAP J2EE Server Properties
Clicking on the "Application's Account" icon will display the Java user account that has been given the monitoring role after configuring the parameters for monitoring.
Figure 4: Application's Account Icon
Monitors the Java communications with external systems such as RFC and Web Service IO, response time, and external calls.
Figure 5: SAP J2EE External Communications
Monitors a variety of metrics, including Java heap memory, garbage collection (GC), system problems, etc., for detailed performance monitoring. These metrics are all alert-based and provide data about the system load and memory.
Figure 6: SAP J2EE Java Virtual Machine
Monitors various managers, including the Java thread system composed of Application Thread Manager and Thread Manager, responsible for handling system and client threads.
Application Thread Manager handles client requests coming from the system, while the Thread Manager is responsible for the system activities such as backup of logs, event processing, internal cluster communication, etc.
Figure 7: SAP J2EE Kernel
Monitors all available services that SAP provides, including memory consumption. Services are mapped automatically after configuration, and IT-Conductor tracks the status in real-time.
Figure 8: SAP J2EE Services
Monitors the basic metrics such as CPU usage, free disk space, and the maximum memory utilization of the operating system that requires continuous monitoring.
Figure 9: SAP J2EE System
Automated Health displays all the metrics and graphical charts of the components discovered after configuring the systems/servers in the IT-Conductor. This is a combination of availability, performance, analytics, and alerts to indicate whether the system is healthy or not.
In the IT-Conductor service grid, click on the Health container to show the system’s health history.
Figure 10: System Health