Have you gotten much out of the SAP Earlywatch reports lately or has it taken a lot of time to maintain all the Solution Manager tools and plugins for little value?
A pulse check with our SAP subscribers to see if they have implemented SAP Solution Manager 7.1 technical monitoring or are folks still waiting for the promised SAP Solution Manager 7.2? Well if you're waiting, then maybe you shouldn't because according to this SCN blog Whats new in SAP Solution Manager 7.2? it's been delayed until at least Q2 2016, and it doesn't look like there's much in the roadmap that greatly enhances technical monitoring or automation.
Users call and escalate about how bad their performance is and the team scrambles to troubleshoot for the root-cause, but the subject matter experts are showing their various charts from their various tools on the incident call. The incident manager circles the room to prompt the Application team to the Basis team, to the DBA team, to the OS team, to the Storage team, and finally to the Network team, trying to see if someone knows the cause of the issues. Someone thinks they found the culprit because their data has some spikes, but they are not quite sure because they don't know what else was happening on the system from other infrastructure or application components.
It may look something like these from CCMS and Solution Manager, which are just plain hard to analyze because they aren't aligned. The teams are most likely not able to agree with confidence on the root-cause.
This last part we will hook up the 2 components of a SAP BOBJ BI 4.0 environment to the SAP Solution Manager, using Managed System configuration and Technical Monitoring by assigning the products and logical components.
Continuing on after installing the SAP Diagnostics Agent on the BI 4.0 system, we will use the AC (Auto-Configure) tool to step through the setup of SAP BOBJ and its various components to enable their integration and instrumentation for monitoring SAP Business Intelligence including:
- Wily Introscope
- SAPOSCOL (SAP Operating System Collector)
- Tomcat web server
As far back as I can remember, and that's more than 20 years working in SAP Basis, since the days of R/3, there's always been this 2 second average response time per dialog step (or simply 2 second response) benchmark as acceptable performance of an SAP OLTP system. Depending on the customer, some will tweak that to fit their business, and I have seen it range from 0.5 second to as high as 5 seconds. Honestly, it's a misleading indicator of performance because on any given mid-size SAP ECC production system with about 500 concurrent users, that number quickly becomes a useless measure with more transaction mix between SAP and custom code. To put it into perspective, a system may have a 0.5 second response time, but there are constant complaints from users with bad response times. Why? It's the law of averages. The more number of small transactions there are (those who run relatively quick), the more they bring down the system average into an attractive average response time, even though there are transactions that run forever and frustrate the hell out of those users who need to run them as part of their daily business process. It's because dialog steps are not created equal.
This week we finally see the results of all the work we put in to Solution Manager 7.1 from system preparation through to technical monitoring. Although no two SAP environment are exactly the same, even though they maybe based on the same products and installed in identical manners, hopefully you have a good sense of what it takes to get technical monitoring up and running in Solman. Unfortunately, no amount of SAP documentation or guided procedures can give you the same sense as actually doing it or follow along an actual implementation, so we encourage you to try it yourself, or use our example here to gauge and plan for such efforts since it's not trivial.
To recap the other 2 parts leading up to this final setup and demo, we completed:
- Netweaver on HANA Monitoring Setup Part 1 of 3 (Preparation)
- Netweaver on HANA Monitoring Setup Part 2 of 3 (Managed System Configuration)
Over the last week we've been busy updating our SAP Solution Manager 7.1 from SPS11 to SPS12. It doesn't sound like much but as usual, we found so many notes, preparations and post-processing to perform. It's a whole lot more than just running SUM (Software Update Manager), so it will have to be topic of discussion for another time.