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
More and more SAP customers have been migrating their databases to SAP ASE (formerly Sybase), which raised the need to monitor and manage ASE's availability and performance.
Taking a play-card from our OZSoft HANA Management Pack for SCOM powered by IT-Conductor, we are able to agentlessly monitor ASE combined with SAP HOSTAGENT for outside discovery and availability monitoring. As discussed in the HANA monitoring using Synthetics article, we also offer SAP ASE customers the ability to monitor via native synthetic transactions directly against the database with the release of OZSoft ASE Management Pack for SCOM v1.0.2.
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.
Continuing on after installing the SAP Diagnostics Agent on the BI 4.0 system, we will use the AC (Auto-Configure) tool to step through the setup of SAP BOBJ and its various components to enable their integration and instrumentation for monitoring SAP Business Intelligence including:
- Wily Introscope
- SAPOSCOL (SAP Operating System Collector)
- Tomcat web server
The best way to check the availability and performance of any application or database is to actually login and run something, in this case a transaction. For HANA, the simplest way is to execute a SQL against the database. Automating this would serve both purposes of ensuring the database is accessible as well as being able to provide response time for particular transactions, on a periodic basis. Furthermore, it can be used to automate regular jobs such as health checks or housekeeping, without creating intricate database jobs.