-
Request for existing cases, user IDs, Portal navigation support and more
Non-SAP Monitoring
Why do this?
In an ideal world the customer has a homogeneous SAP landscape and monitors everything with SAP Solution Manager. Unfortunately, the real world is different and most customers have SAP systems and non-SAP systems. Let's take the following banking scenario example to illustrate this.
The front-end applications are partially from SAP and most of the back-end systems are from SAP. To exchange data between the front-end applications and the back-end systems, there is a central non-SAP integration layer system in between. From a business process point of view, a process might start and end in an SAP system, but the non-SAP integration layer system is crucial for the whole process, so it definitely needs to be monitored.
You might monitor this non-SAP system with third-party monitoring but do you really want to:
- operate several monitoring solutions?
- maintain and train employees in several tools?
In the end, this is always an individual decision. If SAP Solution Manager is already established as a monitoring tool, and if the footprint of non-SAP applications is rather small, non-SAP monitoring in SAP Solution Manager may be a good solution.
Benefits
Non-SAP systems can also be monitored with SAP Solution Manager. This provides you several benefits:
- You have a single point of truth for the overall system health
- You need to operate only one monitoring solution
- The operation team only needs to learn one monitoring tool
- There are no license costs when using SAP Solution Manager for non-SAP monitoring (except for CA Introscope in case this is needed)
- Seamless integration into SAP Solution Manager System Monitoring with same look and feel as well as functionality (metric history drill down, notifications and incidents)