> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/sap-application-monitoring/itc-sap-java-server-monitoring.md).
# SAP J2EE Server Monitoring
### Background
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.
### Configured SAP Java Servers in IT-Conductor
{% hint style="info" %}
**Note:** To know more about configuring SAP Java Servers in IT-Conductor, kindly refer to this [article](/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/sap-j2ee-system.md).
{% endhint %}
In the Administrator dashboard, navigate to SAP J2EE Systems.
The page will show the list of all SAP Java Servers defined in IT-Conductor.
Clicking into the **\,** 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.
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.
### Features
#### External Communications
Monitors the Java communications with external systems such as RFC and Web Service IO, response time, and external calls.
#### Java Virtual Machine (JVM)
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.
#### Kernel
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.
#### Services
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.
#### System
Monitors the basic metrics such as CPU usage, free disk space, and the maximum memory utilization of the operating system that requires continuous monitoring.
#### Overall System Health
[Automated Health](/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/sap-application-monitoring/sap-nw-monitoring/itc-monitoring-automation-of-service-health.md) 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.
### Video
{% embed url="" %}
### Related Articles
* [SAP J2EE System](/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/sap-j2ee-system.md)
* [SAP PO Application Monitoring](/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/sap-application-monitoring/itc-sap-java-server-monitoring/sap-j2ee-+po-monitoring.md)
* [IT-Conductor Monitoring Automation of Service Health](/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/sap-application-monitoring/sap-nw-monitoring/itc-monitoring-automation-of-service-health.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/sap-application-monitoring/itc-sap-java-server-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.