Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
Ulrike_Hormann
Explorer

As of Solution Manager 7.1 SP12, you have the option to use Business Process Monitoring on MAI. This new Business Process Monitoring function uses the monitoring and alerting infrastructure, which is quite different from the infrastructure for classic BPMon.

The most important infrastructure changes are:

  1. Storage of monitoring configuration

    In classic BPMon, the monitoring configuration was stored in the DMD. The generated and activated customizing was stored in cluster tables. For BPMon on MAI, all monitoring configuration (saved, generated and activated) is stored in the MAI infrastructure. Only the link between the business process context and the monitoring object is stored in the DMD.
  2. Triggering of Data Collection

    In classic BPMon, the trigger for the data collection came via the CCMS on SAP Solution Manager, using the BPM_LOCAL RFC destination. For BPMon on MAI, this trigger now comes via the DPC PULL Extractor in the Extractor Framework. The BPM_LOCAL RFC destination is no longer used in BPMon on MAI.
    Since the DPC PULL extractor can only be triggered every 5 minutes, also for BPMon on MAI data cannot be collected more frequent than every 5 minutes (in theory, PUSH metrics could be collected more frequently, but almost all BPMon metrics currently available are PULL metrics).
    In classic BPMon, the scheduling maintained in CCMS or the information stored in table DSWP_BPM_TIMESCH was used for determining which monitoring objects were due for data collection. For BPMon on MAI, the scheduling information is stored in the MAI infrastructure. Table DSWP_BPM_TIMESCH does not contain entries for monitoring objects collected via BPMon on MAI.
  3. RFC destination for data collection

    In classic BPMon, the TMW RFC destination is used for data collection. In case no TMW destination exists, the READ destination is used as a fallback (in earlier releases only the READ RFC destination was used). In BPMon on MAI, the data collection is executed via the TMW RFC destination. If no TMW destination exists for the managed system, no data collection will be possible.
  4. Add-Ons installed on managed systems

    In classic BPMon data collectors on the managed system were called directly (i.e. coding shipped in ST-A/PI was called directly from SAP Solution Manager). In BPMon on MAI, the BPMon data collectors are called via the DPC Extension (which is part of ST-PI) on the managed system. This means that for BPMon on MAI, it is mandatory to have ST-PI SP10 or higher implemented on the managed system, and the managed system has to have a basis release 7.0 or higher.
  5. Alert Storage

    In classic BPMon, alerts were stored in table DSWP_BPM_ALERTS. In BPMon on MAI, alerts are stored in the MAI infrastructure. You will not find entries for BPMon objects collected via MAI in table DSWP_BPM_ALERTS.
    In classic BPMon, alerts could be transfered to cube 0SM_BPM for trend analysis. In BPMon on MAI, this cube is no longer used. The BPMon alerts  are stored in the MAI twin cubes.

The changes in the infrastructure mean that the prerequisites for Business Process Monitoring on MAI have changed compared to classic BPMon. For the prerequisites for Business Process Monitoring on MAI, please see SAP Note 1949245.

For an introduction to Business Process Monitoring on MAI and links to further blogs for BPMon on MAI see Business Process Monitoring on MAI available with Solution Manager 7.1 SP12.

4 Comments