Skip to Content

After going through a number Solution Manager 7.1 installations with SPS3 and 4, I’ve found a number of things to be true in all of the installations to date. These steps will help avoid problems within the configuration or down the line when you decide to activate functionality like Technical Monitoring or Root Cause Analysis.

Always patch your Solman SLD to the latest version after installation

          Delivered content is from ~2010 and you can run into issues connecting systems to your SLD that are of a very recent release.

Do not create a separate BI client for reporting

         I was used to creating a seperate BI client for reporting in CRM for OLTP reports whose guides dictate a seperate client.  Don’t follow suit here!  A seperate BI client will give you headaches in terms of authorizations and user accounts co-existing between your productive Solution Manager and BI clients.

– Always install a minimum two tiered Solution Manager landscape

         Running one single Solution Manager box is a thing of the past if you are doing anything more than Maintenance Optimizer.  With where Solution Manager 7.1 is heading and once your clients see the capabilities available, you’ll have a much harder time stepping back and getting that second system installed down the road.


– Use transaction SM_CONFIG_JOBS to check the status of Solution Manager man specific jobs

          Very handy way to make sure all your standard Solution Manager jobs are active and whether new jobs need to be scheduled.

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Josh Fisher Post author

    Thanks for the feedback thus far!  I’d love to hear others experiences with Solution Manager 7.1 configuration and landmines that can be avoided!

    (0) 

Leave a Reply