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!
Ever want to collectively view many KPI's across multiple SAP systems and infrastructure components, even across many sites or locations? It's always been a challenge to do so, especially to monitor SAP, analyze or trend performance end-to-end and see the big picture at the same time. It's a best practice to use such capability in an application performance management (APM) tool as we discussed in our 10 Ways to Better Application-Centric Service Management Best Practices. Recently in our first IT-Conductor Newsletter February 23, 2017 edition, we announced the availability of a feature to Save Custom Service Charts (KPI's). The ability to see KPI's across multiple monitored services had been there for years, but recently we allowed users to save and view them, and even schedule reports for them as a Saved Service Health Chart.
We have been publishing extensively with more than a dozen articles on How to monitor your SAP environment using SAP Solution Manager, but what happens when Solman itself is suffering from Performance and Availability issues? Solman has widen its footprint at enterprises, some mandatory uses of functionality such as Maintenance Optimizer, and Remote Support, while others include Technical Monitoring and Change Request Management (ChaRM). Given such dependencies of many SAP customers on their Solman, shouldn't it be monitored and managed as a business critical system?
What may seem to be an obvious choice for SAP customers really isn't as obvious!
For more than 21 years in the SAP field and hundreds of SAP projects, from the mainframe R/2 days until now when some things are new again with SAP HANA and many other products, the question of "What SAP monitoring tools do you use?" is still greeted with an unclear and/or lengthy response. Often, the responses will follow with reasons why one tool is used for this and another tool is used for that by various different folks on the IT team. With the myriad of application environments to manage, one can understand the complexity and thus the non-obvious answer to the above question.
So, I thought it may be useful to provide an evaluation list of systems management areas based on my experience working with customers on monitoring, performance testing, and IT service management. It would provide:
- An objective way of assessing features and functionality, costs aside as it money complicates everything
- A central place to list the tools and what they are used for as well as their strengths & weaknesses
- A matrix to assign merit score and weight to each criteria that would help in tools and/or vendor selection
Image courtesy SAP SE