Application Performance Management (APM) tools have evolved along with the modernization of applications and IT infrastructures. From simply monitoring the availability and performance of legacy applications to having the ability to discover and analyze distributed systems, we found ourselves in dire need to understand systems and applications on a much deeper level.
SAP has been widely regarded for its software solutions having complex user interfaces. In May 2013, when SAP announced the launch of SAP Fiori as “a collection of apps that are simple, easy-to-use, and provide an intuitive user experience for broadly and frequently used SAP software functions, across a variety of devices — desktop, tablet, smartphone — to help easily get the job done”, the way users access backend data started changing gradually from using transaction codes, or tcodes, to simply navigating around a user interface easily accessible from web browsers.
The following assessment, research and TCO (Total Cost of Ownership) calculations are derived from real customer deployment, upgrades, industry surveys, and monitoring projects for the past 10 years across many size of customers. It is intended to help with budgeting and measuring ROI before investing in Solman as a primary enterprise monitoring platform for SAP environment.
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.
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)