bpmonitring document

Alert Consumption for Business ProcessMonitoring on MAIwith SAP Solution Manager 7.1 SP12Setup and features of notifications and incidents

BUSINESS PROCESS MONITORING NOTIFICATIONS ST 7.1 SP12

2

TABLE OF CONTENTS

1 INTRODUCTION .......................................................................................................................... 32 FUNCTIONAL OVERVIEW .......................................................................................................... 42.1 General Behavior ........................................................................................................................ 42.2 Additional features ..................................................................................................................... 43 NOTIFICATION SETUP: EMAILS AND SMS ............................................................................... 53.1 Assign a notification variant ...................................................................................................... 53.2 Activate automatic notifications ................................................................................................ 53.3 Set the notification alert level .................................................................................................... 53.4 Set the email sender ................................................................................................................... 63.5 Choose between email and SMS................................................................................................ 63.6 Add recipients and recipient lists .............................................................................................. 63.7 Access personal notification settings in CNM .......................................................................... 63.8 Send notification for closed alerts ............................................................................................. 73.9 Delay the notification sending ................................................................................................... 73.10 Send additional notifications ..................................................................................................... 73.11 Set a customized subject text .................................................................................................... 83.12 Set a customized introductory long text ................................................................................... 83.13 Assign a MAI text BAdI implementation .................................................................................... 84 INCIDENT SETUP ........................................................................................................................ 94.1 Assign an incident variant ......................................................................................................... 94.2 Activate automatic incident creation ......................................................................................... 94.3 Set the incident alert level .......................................................................................................... 94.4 Set incident transaction type ....................................................................................................104.5 Set support component .............................................................................................................104.6 Set incident reporter ..................................................................................................................104.7 Set incident processor ..............................................................................................................104.8 Set incident category.................................................................................................................114.9 Confirmation of incident confirms alert ....................................................................................114.10 Update incident on certain events ............................................................................................114.11 Set a customized subject text ...................................................................................................114.12 Set a customized introductory long text ..................................................................................114.13 Assign a MAI text BAdI implementation ...................................................................................125 CONSUMER VARIANTS .............................................................................................................135.1 Assign and maintain variants ...................................................................................................136 ALERT HANDLING .....................................................................................................................146.1 Create a custom alert description .............................................................................................146.2 Add a guided procedure ............................................................................................................157 THIRD-PARTY CONNECTORS ..................................................................................................167.1 Add a custom BAdI implementation .........................................................................................16


3

1 INTRODUCTIONWith ST 7.1 SP12 Business Process Monitoring (BPMon) can be realized by the Monitoring and AlertingInfrastructure (MAI) and shown in a new alert inbox in work center Business Process Operations (New).To set up automatic notifications and incidents for BPMon on MAI alerts, the MAI notification/incident setuphas been embedded in the BPMon setup for automatic notifications/incidents.This setup guide describes how to set up automatic sending of notifications and SMS, and the auto-creationof SAP Solution Manager Incidents for such BPMon on MAI alerts.

In addition to the standard alert consumption methods, the enhancement options by the use of differentBAdIs are also described in this Guide.

For the general information how to set up Business Process Monitoring on MAI, please see the Setup Guidefor BPMon on MAI.


4

2 FUNCTIONAL OVERVIEW2.1 General BehaviorThe notification (email, SMS, incident or BAdI processing) is triggered by the creation of a new alert groupfor a managed object:A new alert opens a new alert group. This group stays active until the monitor reports a different alert rating(e.g. yellow red; or red green) or the alert processor closes the alert group manually. If the monitordoesnt process collector data anymore, the alert group is also closed (grey alert).Alert groups are usually created per managed object. That means that several key figures (metrics) can begrouped into one alert group.

2.2 Additional features

2.2.1 Notification in case of metric rating deteriorationThe alert rating is determined based on the rating of the defined metrics. If one of the metric ratings getsworse (e.g. yellow red), a notification is triggered even if the overall alert rating s doesnt change (i.e. nonew alert group is created)

2.2.2 Notification after alert group closure (optional)A notification can also be triggered, if the alert group is closed. This may help to stop unnecessary problemsolving activities.

2.2.3 Delayed notificationInstead of sending the notification immediately after the alert is raised, you can also wait for a certain timeand send the notification delayed.

2.2.4 Reminder notifications after self-defined latency timeIt is possible to send reminder emails after a certain time if the alert group has still not been closed.

2.2.5 Customizable subject and introductory text of emailAlthough most of the notification text is pre-defined, you can add an introductory text for the notificationrecipient. The default email subject text or incident short text can be overwritten with user-defined texts.

2.2.6 Customer exits for text handling and dynamic recipient determinationWith SP12 we offer the possibility to change the complete long text and to determine the email recipientsand the incident processor depending on the metric data in a pre-delivered BAdI implementation.

2.2.7 Customer exit for third-party connectorIt is possible to use a self-defined BAdI implementation to connect to third-party incident systems or to triggeradditional activities.

2.2.8 Reuse of existing BPMon BAdI implementationsIf the existing BPMon BAdI implementations cannot be replaced by new MAI BAdI implementations, it ispossible to reuse the old coding by implementing SAP notes.

2.2.9 Variants to enable reuse of global settingsVariants can be used to deliver the same settings to multiple monitors. These variants are equivalent to thewell-known notification templates in the classical BPMon.


5

3 NOTIFICATION SETUP: EMAILS AND SMSThe notifications for a monitoring object can be defined in tab Notifications in the BPMon Setup for thismonitoring object.

3.1 Assign a notification variant

You can assign here an existing notification variant. The notification variant comprises notification settingswhich can be used in various monitoring objects. In the classical BPMon this feature was called NotificationTemplates.See chapter 5 Consumer Variants for more information on how to maintain the variants.

3.2 Activate automatic notifications

This field needs to be set to Active to enable automatic email or SMS creation for alerts.

3.3 Set the notification alert level

You can choose for which alerts a notification should be created:x Red and yellow alerts (default)x Red alerts onlyx Yellow alerts only


6

3.4 Set the email sender

A sender of the notification needs to be set here. An SAP user with a valid email address is required.This is a mandatory field and you get a warning message if the field is empty or if the no valid email addressis assigned to the selected user.SOLMAN_BTC is taken by default.

3.5 Choose between email and SMS

An email, an SMS or both (default) can be sent out to the recipient.The recipient data set needs to have a valid email address and mobile number.

3.6 Add recipients and recipient lists

Recipients and/or recipient lists of the Central Notification Management (CNM) need to be added here.Recipients can be created from this screen or in the CNM application of the Solution Manager:Work center Technical Administration Notification Management

3.7 Access personal notification settings in CNM

Access the CNM settings for your personal recipient settings, e.g. presence, absence and off-dutysubstitution rules.


7

3.8 Send notification for closed alerts

If this checkbox is marked an additional notification is created when the alert group is closed.Possible reasons for a closure of the alert group are:x Alert rating changesx Monitor is re-configured and activatedx Alert group is manually closed by alert processor or other personx Work mode of underlying system changes

3.9 Delay the notification sending

Instead of sending the notification immediately after the alert is raised, you can also wait for a certain timeframe and send the notification delayed. If the alert has been closed during this latency time, no notificationwill be sent.This feature can be used to suppress notifications for events which are not critical and disappearautomatically after a certain time.

3.10 Send additional notifications

By default a notification is sent only when an alert is raised for the first time and the yellow or red alert groupis created.


8

You can receive additional (reminder) notificationsx Periodically after a defined time orx For every occurrence of the alert, i.e. whenever the alert receives the same rating again

The reminder notifications show the actual situation after the most recent data collection.Be aware of potential notification flooding!

3.11 Set a customized subject text

The entered subject text overwrites the generic standard subject text. Some text variables in the subject textcan be replaced by using a standard BAdI implementation (see chapter 3.13 Assign a MAI text BAdIimplementation)x $SID$ replaced by the system IDx $MOB$ replaced by the monitoring object namex $BUP$ replaced by the business process (if monitored object is assigned uniquely)x $SOL$ replaced by the solution name

3.12 Set a customized introductory long text

The entered introductory long text will appear in the notification on top of the technical default long textYou can use it to address the alert processor personally. Some text variables can be replaced by using astandard BAdI implementation (see also chapter 3.11 Set a customized subject text):x $SID$ replaced by the system IDx $MOB$ replaced by the monitoring object namex $BUP$ replaced by the business process (if monitored object is assigned uniquely)x $SOL$ replaced by the solution name

3.13 Assign a MAI text BAdI implementation

You can assign here an implementation of the MAI text BAdI BADI_DYN_INCI_NOTIF_MULTIPLE.You can define your own MAI text BAdI implementation to overwrite the default notification text, subject andrecipients.Two standard implementations are available by default:x Replace text variables in subject text and short text

As mentioned in chapter Set customized subject text, this implementation replaces the textvariables $SID$, $MOB$, $BUP$ and $SOL$ with the corresponding names

x Notification routing with BRF+ and text variable replacementThis implementation enables the dynamic determination of notification recipient by using BRF+decision tables. See SAP note 1983091 for further information.

The MAI text BAdI can also be used to reuse your existing implementation of the BPMon text BAdIBADI_BUILD_MESSAGE. See SAP note 1980912 for further information.


9

4 INCIDENT SETUP

4.1 Assign an incident variant

You can assign here an existing incident variantThe incident variant comprises incident settings which can be used in various monitoring objectsIn the classical BPMon this feature was called Notification TemplatesSee chapter Variants for more information

4.2 Activate automatic incident creation

This field needs to be set to Active to enable automatic incident creation for alerts.

4.3 Set the incident alert level

You can choose for which alerts an incident should be created:x Red and yellow alerts (default)x Red alerts only


10

x Yellow alerts only

4.4 Set incident transaction type

The CRM transaction type of the incident can to be set here.The default value is taken from the CRM customizingtransaction SPRO SAP Reference IMG

4.5 Set support component

You need to choose the support component on which the incident is opened (mandatory field)

4.6 Set incident reporter

The incident reporter is a mandatory field. SAP user SOLMAN_BTC is the default value.

4.7 Set incident processor

This is an optional field. You can set a dedicated processor or service team for incident processing.


11

4.8 Set incident category

The category can be chosen out of a four-level hierarchy with different classifications,e.g. Incident SAP application Error message JAVA ExceptionA category hierarchy is called Schema. Different schema can be used. It is possible to define an ownschema or enhance an existing one. The default schema is SAP_SOLUTION_MANAGER_TEMPLATEMore information can be found here:http://wiki.scn.sap.com/wiki/display/SAPITSM/Multilevel+Categorization

4.9 Confirmation of incident confirms alert

If this checkbox is marked, the confirmation of the incident triggers an automatic alert confirmation.

4.10 Update incident on certain events

Update for new alerts: The incident long text will be updated if new alerts occurUpdate on alert closure: The incident long text will be updated when the alert is closed.

4.11 Set a customized subject text

The entered subject text overwrites the generic standard subject (description) text of incident. Some textvariables in the subject text can be replaced by using a standard BAdI implementation (see chapter 4.13Assign a MAI text BAdI implementation)x $SID$ replaced by the system IDx $MOB$ replaced by the monitoring object namex $BUP$ replaced by the business process (if monitored object is assigned uniquely)x $SOL$ replaced by the solution name

4.12 Set a customized introductory long text

The entered introductory long text will appear in the incident on top of the technical default long textYou can use it to address the incident processor personally. Some text variables can be replaced by using astandard BAdI implementation (see also chapter 4.11 Set a customized subject text):x $SID$ replaced by the system IDx $MOB$ replaced by the monitoring object name


12

x $BUP$ replaced by the business process (if monitored object is assigned uniquely)x $SOL$ replaced by the solution name

4.13 Assign a MAI text BAdI implementation

You can assign here an implementation of the MAI text BAdI BADI_DYN_INCI_NOTIF_MULTIPLE.You can define your own MAI text BAdI implementation to overwrite the default incident text, subject andprocessors.Two standard implementations are available by default:x Replace text variables in subject text and short text

As mentioned in chapter 4.11 Set a customized subject text, this implementation replaces the textvariables $SID$, $MOB$, $BUP$ and $SOL$ with the corresponding names

x Notification routing with BRF+ and text variable replacementThis implementation enables the dynamic determination of the incident processor by using BRF+decision tables. See SAP note 1983091 for further information.

The MAI text BAdI can also be used to reuse your existing implementation of the BPMon text BAdIBADI_BUILD_MESSAGE. See SAP note 1980912 for further information.


13

5 CONSUMER VARIANTS

5.1 Assign and maintain variants

BPMon on Mai uses three types of variants: notification, incident and third-party variants (A fourth varianttype auto-reaction variant is similar to type third-party variant and not explicitly used here)The three variant types can be found on the corresponding tab of monitoring object setup.Variants can be assigned to various monitoring objects by selecting an existing variant from the drop-downlist.Enter the Consumer Variant Maintenance by selecting the Maintain xxx Variants text on the right:

On the maintenance screen you can choose an existing variant or create a new one. The screen containsthe same fields as in the individual monitoring object setup. There is a maintenance screen for every varianttype.


14

6 ALERT HANDLING

6.1 Create a custom alert description

The custom description will appear in the notification text. It can be edited using html tags. Different objectscan be added: symbols, images, MIME links and URLs.The URLs can be selected from the pre-defined list of the URL framework which can be accessed bypressing the Insert URL button Select Dynamic URL.The correct URL can be found by filtering on the application id or name. Useful URLs arex ALERT_DETAILS_ST Alert Details in Satellite Systemx GENERIC_TRANS_ST Generic Transaction on Satellite Systemx GENERIC_TRANS_SM Generic Transaction on Solution Manager

Example: You want to include the link to transaction SLG1 on the managed system:Choose Insert URL application ID GENERIC_TRANS_ST add the transaction (SLG1) as Static Valuefor Parameter Key ~transaction press OK.


15

6.2 Add a guided procedure

A guided procedure can be assigned to this monitoring object by selecting it from the value list. If you want tocreate a new guided procedure for this monitoring object or edit an existing one, the guided procedurebrowser can be accessed from the link Open Guided Procedure Browser.


16

7 THIRD-PARTY CONNECTORS

7.1 Add a custom BAdI implementation

You can assign an implementation of the MAI custom BAdI BADI_ALERT_REACTION.This MAI BAdI can be used to e.g. connect to external systems.It is also used to reuse your existing implementation of the BPMon custom BAdIsBADI_CUSTOM_MESSAGE and BADI_CUSTOM_SUPNOTIF (See SAP note 1897251 - BPMon:Safeguarding BPMon BAdI Implementations in MAI for further information)More Information on the MAI alert consumer BAdI interface and how you can create a new BAdIimplementation can be found here:http://wiki.scn.sap.com/wiki/display/TechOps/Alert+Consumer+BAdI+Interface

www.sap.com

2014 SAP AG or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or forany purpose without the express permission of SAP AG or an SAP affiliatecompany.

SAP and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG (or anSAP affiliate company) in Germany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark foradditional trademark information and notices. Some software productsmarketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company forinformational purposes only, without representation or warranty of any kind,and SAP AG or its affiliated companies shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP AG orSAP affiliate company products and services are those that are set forth in theexpress warranty statements accompanying such products and services, ifany. Nothing herein should be construed as constituting an additional warranty.In particular, SAP AG or its affiliated companies have no obligation to pursueany course of business outlined in this document or any related presentation,or to develop or release any functionality mentioned therein. This document, orany related presentation, and SAP AGs or its affiliated companies strategyand possible future developments, products, and/or platform directions andfunctionality are all subject to change and may be changed by SAP AG or itsaffiliated companies at any time for any reason without notice. The informationin this document is not a commitment, promise, or legal obligation to deliverany material, code, or functionality. All forward-looking statements are subjectto various risks and uncertainties that could cause actual results to differmaterially from expectations. Readers are cautioned not to place unduereliance on these forward-looking statements, which speak only as of theirdates, and they should not be relied upon in making purchasing decisions.

bpmonitring document

Documents

notification setup

notification variant

set incident t

notification alert level

incident setup

incident variant

incident alert level

features of notifications