SAP Solution Manager 7.2 · Landscape Data: SLD, LMDB & Maintenance Planner

What's the trade-off between having SolMan read a central/remote SLD versus using an SLD bridge?

  • Read a central SLD — creates a dependency on the dev/production SLD; updating SLD content needs other teams to cooperate.
  • SLD bridge — SolMan's SLD content can be updated independently, with no impact on other teams, and shields SolMan from dev/production upgrades.

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 Landscape Data: SLD, LMDB & Maintenance Planner

How does each type of system register with the SLD?
How often should SLD content be updated, and what's notable about applying an update?
What replaced the Maintenance Optimizer, and when are customers required to use it?
What is the key output of the Maintenance Planner, and what tool consumes it to execute the planned upgrade?
What role does the System Landscape Directory (SLD) play in an SAP landscape?
When deciding where to run the SLD, what makes putting it on SolMan's own Java stack the preferred choice — and when is the decision trivial?