Triggering Alerts Based on Events

Use

Applications can trigger events based on BOR or ABAP OO objects. You can use these events to trigger alerts for the Alert Framework. You can do this in the following ways:

?     Trigger alerts directly

You assign the event directly to an alert category of the Alert Framework. When the event occurs, it triggers an alert using the Alert Framework. You can use conditions to filter the events. This allows you to ensure that only relevant events trigger alerts.

?     Trigger alerts using an integration process

An event does not trigger an alert directly, but generates an XML message by using a message proxy. An integration process subscribes to this message. Using rules, the integration process determines whether an alert is triggered for the Alert Framework.

To assign an event to an alert category or a message proxy, you define the relevant event linkage in transaction SWF_BAM.

Prerequisites

To be able to trigger alerts using an integration process, the following prerequisites must be fulfilled:

?     You have a system with the following activated usage types:

0     Process Integration (XI) with the Business Process Engine

0     AS ABAP

?     Exchange Infrastructure (XI) and the Business Process Engine use the same alert server.

Triggering an Alert Directly

       1.      Define the required alert category.

The alert category specifies, for example, the text for the alert and all details relating to its delivery.

See also: Defining Alert Categories

       2.      Call transaction SWF_BAM.

       3.      Define the Application Object to Alert event linkage:

                            a.      Select the required object and the corresponding event.

                            b.      Assign the required alert category.

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

                            d.      In the binding definition, specify which data for the object is to be sent to the Alert Framework.

Triggering Alerts Using an Integration Process

Defining the Alert Category

...

       1.      Define the required alert category.

The alert category specifies, for example, the text for the alert and all details relating to its delivery.

See also: Defining Alert Categories

If you want to define the text for the alert later in the integration process, choose Dynamic Text.

See also: Triggering Alerts

Defining Monitoring Events

To enable an integration process to subscribe to the required application events, these events must be delivered to Exchange Infrastructure. To do this, you define the required message interfaces in the Integration Builder (Design):

       2.      Define the data types that you require for exchanging data with the integration process.

You can reuse these data types in different message types.

See also: Data Types

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

See also: Message Type

       4.      Define an outbound message interface for each event that the integration process is to process.

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

See also: Developing Message Interfaces

       5.      Define an abstract message interface for each event that the integration process is to process.

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

       6.      In the interface determination in the Integration Builder (Configuration), assign the relevant abstract interface to each outbound interface.

An interface mapping is not required.

Proxy Generation

       7.      In the Integration Builder (Configuration), configure the message communication between the application system and the Integration Server.

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

See also: Configuring Message Processing

       8.      Generate the required proxies.

See also: Proxy Generation

Defining Event Linkage

       9.      Call transaction SWF_BAM.

   10.      Define the Application Object to Message Proxy event linkage.

                            a.      Select the required object and the corresponding event.

                            b.      Assign the required proxy.

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

                            d.      In the binding definition, specify which data for the object is to be used to generate the message.