Monitoring Milestones 

Function

You can define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems. The monitoring process can filter the events and then process them further.

 

A monitoring process is a special type of integration process. Therefore, the rules for using integration processes efficiently and optimizing performance also apply to monitoring processes.

More information: Checklist: Making Correct Use of Integration Processes

Procedure

Create events

       1.      Identify the events that you want the monitoring process to monitor.

In SAP applications, you can use all events that are based on BOR or ABAP OO objects:

○       Events that are generated in a standard SAP application

○       Customer events that you generate yourself, for example by calling a function module, by making entries in the control tables of status management, or by connecting to message control.

More information: Using Events

If you want to monitor events from non-SAP applications in the monitoring process, you must convert the events to event messages that can be processed by the monitoring process. To do this, you use the Adapter Framework of the technical usage type Process Integration (PI).

More information: Connectivity

Define monitoring events

       2.      Define the required objects for creating the event message in the Enterprise Services Repository.

                            a.      Define the data types that you require for exchanging data with the monitoring process.

You can reuse these data types in different message types.

More information: Data Types

                            b.      From the relevant data types, assemble the message types that you require for exchanging data with the monitoring process.

More information: Message Type

                            c.      Define an outbound service interface for each event that the monitoring process is to process.

You will use these outbound service interfaces later to generate the message proxies in the application systems.

More information: Service Interface

Define an abstract service interface for each event that the monitoring process is to process.

For each abstract service interface, use the same message types as those used in the corresponding outbound interface.

       3.      In the interface determination in the Integration Directory, assign the relevant abstract interface to each outbound interface.

An interface mapping is not required.

Generate proxies (only for events from SAP applications)

       4.      In the Integration Directory, configure the message communication between the SAP application system and the Integration Server.

We recommend that you define a PI scenario and use the configuration wizard.

More information: Configuring Individual Connections

       5.      Generate the required proxies in the SAP application system.

More information: Proxy Generation

Define event linkage (only for events from SAP applications)

       6.      In the SAP application system, choose the transaction SWF_BAM.

       7.      Define the Application Object to Message Proxyevent linkage:

                            a.      Create a new event linkage.

                            b.      Select the required business object and the corresponding event.

                            c.      Select message proxy as the receiver.

                            d.      Select the message proxy and the corresponding operation of the corresponding service interface.

                            e.      Use the binding definition to define which data from the business object is to be supplied with the event.

                              f.      Define a condition to filter the events, if required.

Define monitoring process

       8.      Define the monitoring process that subscribes to the event message.

In the monitoring process, define the conditions for generating an alert as well.

More information: Defining a Monitoring Process