Application Operations: MAI Backbone

A teammate says 'the diagnostics agent is SolMan's root-level eyes on the host — it reads OS log files and runs scripts directly.' What's wrong with that, and what does the diagnostics agent actually give you?

An Application Operations tool refuses to produce any data even though it is 'activated'. A colleague says SOLMAN_SETUP for that tool must be incomplete. Where is the real prerequisite?

You are validating that MAI can actually collect data for a managed system. Which collection components must all be in place, and why is leaving one out a silent monitoring gap rather than a hard error?

If RFC connectivity to a managed ABAP system degrades, you lose two different MAI capabilities at once — not just slow metrics. Which two, and why does that make RFC a single point of failure for ABAP monitoring?

EWA reports for a managed system are coming up empty and RTCCTOOL won't run. Which of the two solution-tool plugins — ST-A/PI or ST-PI — do you check, and what tells the two apart?

After the SolMan host is rebuilt, Java performance data from Wily Introscope disappears even though the Java Byte Code Adapter is still installed on the managed AS Java. What's the dependency that explains this?

A 7.1-era runbook tells you to open 'Technical Monitoring'. In Solution Manager 7.2 that label is gone — what is it now called, and where do you actually go?

SolMan needs to auto-discover exactly what is installed on a host — including kernel, library versions and IP — and read OS log files. Which component provides this, and what's the access-level reason it can't be left out?

Two MAI extractor types deliver data in opposite directions. For diagnostics-agent and Wily data versus RFC/DB-cockpit data, which is pull and which is push — and what is the one property that decides?