Local Monitoring & JMX

Which AS Java monitor branch is configurable by developers, and which are reserved for automatically collected data?

Do you need a central SAP NetWeaver AS ABAP monitoring system to monitor an AS Java instance?

How does an AS Java server component or application make its monitoring data available, and which service provides that infrastructure?

At what point is the AS Java monitoring segment created, and what happens to alerts that are completed?

What does each of the four AS Java monitoring areas contain: Kernel, Services, Performance, Applications?

If the AS Java is struggling under load, why can SAP MC / SAP MMC still show its current status and open alerts?

Your colleague wants to deactivate an unused monitoring attribute using the System Overview. Will that work?

What determines the alert color shown in an AS Java monitor, and where do you tune it for your system?

What can the online (NWA) System Overview do that the offline System Overview cannot?

In the RZ20 SAP J2EE status monitors, how do you get from a colored alert to the actual cause?

Why is it significant that AS Java monitoring is built on the standard JMX rather than a proprietary mechanism?