I’ve been specializing in the niche scenario of supporting SolMan for hosting partners since its introduction. This is a fascinating use of SolMan because it’s the ideal centralized platform for IT automation and streamlining in a hosting environment. Of course, the frustrations that a typical customer faces in SolMan are magnified a hundredfold when you are supporting hundreds of systems in a Solution Manager. As SolMan 7.1 is slowly being adopted we’ve had a chance to get an initial taste of some of the joys and pains of the new architecture. Here are my top 10 ways that SolMan 7.1 is an improvement to SolMan 7.0 in a hosting environment, as of SP4.
- Cleaner support of the LongSID (now the “ExtID”) and ability to autogenerate the LongSid
- Pull instead of push from SLD, and ability to support multiple SLD sources.
- New monitoring infrastructure supports large-scale load-balancing better than CCMS
- End-user experience monitoring is much stronger for web monitoring than GRMG was
- More consistent monitoring of ABAP and Java and other components
- Easier to switch over to use a QA SolMan during Production outages
- Auto-patching of host agents and auto-deploy of diagnostics agent content
- Self-diagnosis and self-monitoring
- Much easier to centrally adjust thresholds and apply to different customers
- Less conflict with customer SolMan due to separate configuration of thresholds, notifications
And of course SolMan 7.1 brings with it some new torments for hosting providers, due to the new architecture. But that’s the subject of another blog.