With contributions from Danica Esteban
Traditionally, most Enterprise Monitoring Teams (EMT) took the top down approach of consolidating company wide monitoring in as few central platforms as possible. The EMT sometimes often referred to as the NOC (Network Operations Center) focused primarily in the availability monitoring of network and infrastructures. Application teams were mostly expected to monitor their own applications, being the subject matter expert (SME), and only relied on the EMT for infrastructure monitoring. However with the rise of Apps (everything from back-office to customer facing eCommerce) coupled with multi-tier and multi-vendor environments extending to virtualization and cloud frameworks, the lines have blurred between Apps and Infrastructure. SAP customers are in the thick of this change. EMTs need to evolve to meet the new demands of enterprise apps in the "Age of agile" as referred to in a 2017 BigPanda annual State of Monitoring report. While SAP teams are focused on delivering IT business values to internal and external customers, they continue to look for opportunities to offload application monitoring to EMTs. EMTs risk losing the battle to monitor their critical IT operations when they don't equip themselves with the ability to monitor SAP effectively today and for the future.
- Solution Manager 7.2 Monitoring Setup and Configuration eBook
- HANA and SAP Monitoring Comparison Matrix - in 9 capability areas
- Still on Solman 7.1? See Solution Manager Technical Monitoring
IT-Conductor customers went to Teched with one less worry since we are actively monitoring the availability and performance of their SAP applications WITHOUT Solman, so they are free to focus on other projects.
For the common SAP Basis checklist, there are critical SAP monitoring tasks which should be automated for continuous health check.
- Batch jobs
- RFC destinations availability
- Security alerts - failed login attempts/lockouts
- Filesystems utilization
- System availability
- Database space utilization
- Blocked or errors with tRFC/qRFCs
- SAP service queue utilization
- SAP service process status
- Program dumps
According to SAP, Process Orchestration (SAP PO) is a tool to model and design business processes, primarily used to integrate SAP systems and external systems. There can easily be confusion with interchanging terms used, XI (Exchange Infrastructure), PI (Process Integration) and PO (Process Orchestration), but really they are all the same thing, just SAP evolution over time with increased functionality. In this publication we will summarize the main difference and how to simplify the SAP monitoring of this increasingly important glue that holds together a SAP-based ecosystem.
It's time for the SAP Monitoring challenge! How to monitor ANY and ALL of the following in minutes, WITHOUT knowing anything about SAP Solution Manager, CCMS or any vendor tools? Simple, IT-Conductor does all the work using cloud-based automation, so you don't have to, YES, we'll even manage the monitoring services so all you have to do is relax and use it!
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.
A common SAP technology stack for Business Intelligence that we've come across in the field has been SAP Business Warehouse (BW) backend as the enterprise data warehouse platform, with a BusinessObjects (SAP BOBJ) Business Intelligence (BI) reporting application. Performance testing, monitoring and tuning in such environment requires the setup of tools that will monitor the BOBJ as well as the BW system. This has to be part of any performance and availability management project involving the environment described above. We previously covered the technical monitoring setup using SAP Solution Manager in SAP NW on HANA Monitoring Setup (Preparation, Managed System Configuration and Technical Monitoring). The next series of 3-parts blog we will detail the setup for SAP BOBJ Monitoring in Solman 7.1