IT-Conductor Blog

How to Monitor SAP Solution Manager

Posted by Linh Nguyen on Feb 8, 2017 12:39:05 PM


Chicken of the Egg Dilema of Monitoring SAP Solution Manager

INTRODUCTION:

We have been publishing extensively with more than a dozen articles on How to monitor your SAP environment using SAP Solution Manager, but what happens when Solman itself is suffering from Performance and Availability issues?  Solman has widen its footprint at enterprises, some mandatory uses of functionality such as Maintenance Optimizer, and Remote Support, while others include Technical Monitoring and Change Request Management (ChaRM).  Given such dependencies of many SAP customers on their Solman, shouldn't it be monitored and managed as a business critical system?

The Brewing Problem

It's not the first time, nor probably the last time that customers asked for help with their Solman.  As recent as a few months ago, one customer's Solman was crippling slow, full of error logs, sometimes inaccessible, and occasionally down.  Yet nobody knew why.  Solman has gotten so complex that there are lots of breaking points, and these are just technical non-business scenarios:

  • the ABAP stack and the JAVA stack - the last SAP dual-stack system left,
  • the numerous remote connections in and out out of it,
  • the outdated credentials for managed systems in technical monitoring,
  • the outdated client software for remote DB connections
  • the outdated CR Content for the System Landscape Directory (SLD)
  • the outdated Landscape Management Database (LMDB)
  • the patches and security updates

To make matters worse, the businesses and other IT teams want to roll out more use cases for Solman, and the Basis team is left wondering if they should hire a full time Solman consultant, update/upgrade Solman, size up infrastructure, or just outsource its management.

The Real Dilemma

If Solman is SAP monitoring all your systems, what's monitoring it?  In most cases, NOTHING!  When it's slow or non-responsive or worse yet failing to monitor your SAP landscape, how do you troubleshoot problems and find root-cause?  Of course you can install or use another Solman, perhaps use your Development/QA Solman and hook it up to monitor your Production Solman. There are a couple potential issues with this approach, we assume customers already lack Solman resources dedicated to the task, and secondly we're not aware that there is a Solman monitoring scenario inside SOLMAN_SETUP besides the Self-monitoring capabilities that can't be used when your system is the problem itself.  Yes you can just set it up as a standard dual-stack SAP Netweaver system, but that's not really monitoring Solman's features - just standard CCMS.

Here's How to Monitor SAP Solution Manager WITHOUT Solman!

Use IT-Conductor and monitor your Solman's Availability, Performance and More, here is a summary list of problems we uncovered in no particular order of importance:

  • SAP Patches Can Fix or Break SAP Performance
  • RFC Processing bottlenecks: significant roll-in wait times for RFC combined with high utilization of Dialog work processes
  • Queue RFC errors coming in from connected systems
  • Missing database metrics due to failing DB data collection jobs
  • Missing database primary indexes, based on standard DB checks
  • Database logs indicating misconfigured parameters affecting performance
  • Invalid/Misconfigured SAP and Database monitoring connections
  • Outdated or non-functional SAP HostAgent and SAPOSCOL causing self and remote monitoring issues
  • E2E (End-to-end) monitoring hogging many dialog processes due to parallel HTTP calls from external SMD agents
  • Java Dispatcher configuration out of threads to handle many remote agents
  • SAP Buffer misconfiguration and related performance issues
  • OS memory and CPU utilization and capacity shortage
  • Availability issues with Solman and connected RFC systems

The Results

Improved uptime and performance of Solman, the simple way!

You can have the best of both worlds:

  • Use Solman for what you have to, and need to
  • Use external solution to keep Solman available and performing

Looking for an integrated solution to help with many of the SAP Performance and Availability management needs?  Try IT-Conductor, engineered as a cloud-based SAP Performance management and monitoring platform.  We also offer SAP Performance management as a Service!

FREE IT-Conductor Trial to Monitor SAP



 

Linh Nguyen

Written by Linh Nguyen

Linh was born in democratic Vietnam, escaped from the communist after the war as a boat-people refugee to Malaysia, subsequently immigrated to Australia where he attended high-school and completed dual-degrees in Computer Science & Computer Engineering in just 5 years. He started SAP career in Melbourne, then came to the US in the mid-1990s as a SAP technical consultant. He built a software and consulting company in Silicon Valley in 1996 named OZSoft and has been an entrepreneur with a passion to automate IT processes. In 2014, he started IT-Conductor, Inc. as CEO and co-founder along with David Stavisski, with the goal to help IT organizations to Stop Guessing and Start Managing by automating IT operations using a cloud-based platform IT-Conductor.

Topics: Performance monitor, SAP Solution Manager Technical Monitoring, SAP Solution Manager, Availability monitoring, SAP Performance

FREE IT-Conductor Trial to Monitor SAP

Posts by Topic

see all

Recent Posts

Subscribe to Email Updates