Solution Manager Upgrade

SAP offers no direct 7.0-to-7.2 upgrade path — what does that mean in practice for a 7.0 customer?

What JVM prerequisite does the 7.2 upgrade impose on Java-stack components and Diagnostics Agents?

Before a Solution Manager upgrade, how and why do you freeze the SLD?

What are the four major phases of a Solution Manager 7.2 upgrade?

Which transactions suspend and later reschedule background jobs around a Solution Manager upgrade?

The SL Toolset bundles SUM and SWPM — how do their jobs differ?

After the dual-stack split, in which situations do you actually need an SAP Web Dispatcher?

What does the DMO (Database Migration Option) inside SUM let you accomplish in a single run?

Standard migration to 7.2 offers in-place versus parallel export/import — what's the trade-off between them?

If the upgrade didn't generate all objects, what post-upgrade step is needed and how long does it run?

Which Solution Manager releases can upgrade directly to 7.2, and which cannot?

When deciding between upgrading Solution Manager and doing a fresh implementation, what's the deciding question?

Why run the Solution Manager upgrade on the development system before upgrading the production system?

How does the 7.2 upgrade classify its impact on a functional area as 'High' versus 'Medium', and which areas are High-impact?

Which tools perform the technical upgrade to 7.2, and when are they enough on their own?

When is a fresh implementation the better choice over upgrading Solution Manager?

After upgrading to 7.2, why might your Diagnostics Agents (DAA) fail to connect, and what's the catch with fixing them?

Before disabling SLD-to-LMDB synchronization for an upgrade, what must you verify first?

DMO gives the least downtime — so why might you still pick the standard upgrade-then-migrate path?

You have 20+ managed systems connected to Solution Manager — how does that tilt the upgrade-vs-fresh-install decision?