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.
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.
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)
In Netweaver on HANA Monitoring Setup Part 1 of 3 (Preparation) steps were performed to allow the Solution Manager and the Managed System to communicate with each other. As a recap, the landscape consists of Solution Manager 7.1 that was previously upgraded to SPS12 including Landscape Management DB, on Windows/MSSQLServer. The systems to be managed includes SAP BW 7.31 (HNA) on HANA database SPS07 (HDB), both running on SUSE Linux 11.3.
In this Part 2, the majority of the work is to configure the managed systems with these high-level steps:
- Assign Product
- Check Prerequisites
- Maintain RFCs (for ABAP managed system)
- Assign Diagnostics Agent
- Enter System Parameters
- Enter Landscape Parameters
- Maintain Users (for monitoring ABAP managed system)
- Finalize Configuration
- Check Configuration
- Complete Configuration