SAP Solution Manager 7.2 · Managing Systems: Managed System Config & EWA

Managed System Config's first screen offers Minimum versus Full configuration — when do you pick each?

  • Minimum (without Service Delivery/EWA) — for sandbox/dev/non-prod; lets Test Mgmt and ChaRM use the systems, but no diagnostics agent or EWA.
  • Full (incl. Service Delivery/EWA) — delivers all SAP support services; mandatory for production, recommended for QA.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Managing Systems: Managed System Config & EWA

After deploying support tools, why might an ABAP transport between dev/QA/prod fail, and what setting fixes it?
Why can't SolMan fully manage an old R/3 or ECC 5.0 system, and what can it still do for it?
What RFC types does the 'Maintain RFCs' step generate in Managed System Configuration?
What SAP support tools must be installed to monitor any ABAP stack, and how do you verify the install?
Why must SolMan 'know about' even cloud tenants and peripheral components it doesn't technically manage?
What does a 'technical system' encompass in Solution Manager?