BPMon: Monitoring of non-SAP systems.

[Former Member]

Hi all,

Reading the catalog of all available out-of-the-box key figures which will be available as of ST-A/PI plug-in 01M.

There are references to non-SAP Monitoring capabilities - if available could someone please share the pre-requisites for setting this up?

For example, I assume the non-SAP system needs to be connected via RFC to the Solution Manager system? Does the non-SAP system need to have built-in monitoring capabilities, which are used to generate alerts which can then be extracted by BPMon back into the Solution Manager system?

Thanks,

John

[thomas_niemtschak · Accepted solution]

Hi John,

With ST-A/PI release 01M there will be two new methods for monitoring non-SAP systems in BPMon.

One method for application monitoring of a non-ABAP/non-SAP product is a direct database access by SAP Solution Manager. It reads application tables, calculates key figures and creates alerts for Business Process Monitoring. Obviously SAP Solution Manager must be able to establish a database connection, which can be done using the "DBA Cockpit" (transaction DBACOCKPIT) for the typical SAP-supported DBMS (Adabas, DB2, DB4, DB6, MS-SQL, Oracle). You may need to install an additional DB Client and DBSL in case the remote DBMS is not the same as the local DBMS of Solution Manager.

There will be different strategies on how to make use of such a remote database access

u2022 Predefined BPMon monitoring objects for certain non-ABAP/non-SAP products such as software from SAP Partners. The first example is a set of key figures for TriplePoint Commodity SL.

u2022 A generic BPMon monitoring object that you can customize to collect simple key figures from a single table or view. This implies that you know the data model in the remote database.

u2022 For more complex queries and/or legacy application databases, you may use the framework to implement custom-defined monitoring objects within the BPMon customer-exit.

Further methods for application monitoring of a non-SAP product will be provided using web services. There will be two different scenarios:

u2022 A push scenario where the external system is calling a web service provided by the SAP Solution Manager to provide two identifiers and measured values. These identifiers will link the measured value to the corresponding monitoring object where the received measured value is compared against thresholds. This scenario will be applicable if the external system has scheduling capabilities to trigger the call of the web service.

u2022 Within a pull scenario a consumer proxy to a web service provided by the external system has to be implemented in a BADI. The monitoring object will execute the web service call according to the scheduling information in the BPMon setup session which means that the external system does not have to have any scheduling capabilities.

The general web service requirements to connect two systems like a http (or https) connection need to be established.

Regards,

Thomas

Edited by: Thomas Niemtschak on Mar 5, 2010 10:09 AM