CCMS-Automatic Alert Notification - Configuration Guide

CCMS- Automatic Alert Notification- Configuration Guide
Table of Contents
1. The Alert Monitor........................................................................................................3 1.1Purpose....................................................................................................................3 2. The Monitoring Architecture Concept: ......................................................................4 2.1 Purpose...................................................................................................................4 3. Operating the Alert Monitor........................................................................................6 3.1Purpose....................................................................................................................6 3.2Process Flow...........................................................................................................6 4. Ele ents o! the Alert Monitor ...................................................................................." 4.1 Purpose..................................................................................................................." 4.2 Operation an# Custo i$ing o! the Ele ents o! the Alert Monitor........................% &. Creating an# E#iting Monitor 'ets..............................................................................( &.1 )se.........................................................................................................................( 6. Transporting Monitor 'ets an# Monitor *e!initions ................................................11 6.1 )se.......................................................................................................................11 6.2 Prere+uisites.........................................................................................................11 ".1 )se.......................................................................................................................12 ".2 Prere+uisites.........................................................................................................12 %. ,ule -o#e: ,ule *escription an# )se ......................................................................1& %.1 *e!inition.............................................................................................................1& (. 'electe# Alert Monitor Metho#s ...............................................................................1( (.1 )se.......................................................................................................................1( (.2 Features................................................................................................................1( 1.. 'tep/01/'tep Auto atic Alert -oti!ication Con!iguration......................................2. 1..1 )se.....................................................................................................................2. 1..2 Prere+uisites.......................................................................................................2. 1..3 Proce#ure...........................................................................................................2. 11. 'AP Connect............................................................................................................23 11.1 Purpose...............................................................................................................23 11.4 'en# 2o0.............................................................................................................26 11.& 3n0oun#..............................................................................................................26 12. Creating *istri0ution 4ists ......................................................................................26 12.1 Proce#ure...........................................................................................................26 12.2 ,esult.................................................................................................................2" 13. A##ress T1pe ..........................................................................................................2" 13.1 *e!inition...........................................................................................................2" 13.2 )se.....................................................................................................................2% 14. Auto/,eaction Metho#: E5ecute Operating '1ste Co an# .............................2( 14.1 )se.....................................................................................................................2( 14.2 Prere+uisites.......................................................................................................2( 14.3 Proce#ure...........................................................................................................3. 14.4 ,esult.................................................................................................................32 1&. 'etting )p Central Auto/,eaction Metho#s ...........................................................32 1&.1 )se.....................................................................................................................32 2
CCMS- Automatic Alert Notification- Configuration Guide 1&.2 Prere+uisites.......................................................................................................32 1&.3 Constraints.........................................................................................................33 1&.4 Proce#ure...........................................................................................................33 1&.& ,esult.................................................................................................................36
1. The Alert Monitor

1.1Purpose
The CCMS provides a variety of monitors to support the SAP environment and its surrounding components. These monitors are critical for understanding and evaluating the behavior of the SAP processing environment. If your SAP System is operating at unacceptable performance levels, they provide the proper tuning insight for making sure your SAP installation is operating at peak efficiency. ith the alert monitor, you can manage and monitor your !"# System efficiently. The monitor offer you$ Complete, detailed monitoring of the !"# System, host systems, and database Status indicators %green, yello&, red' for all components Alerts if a status indicator is not in the green range (asy access to methods for analy)ing alerts Alert tracking and management
2. The Monitoring Architecture Concept:

2.1 Purpose
The !"# alert monitor is based on an innovative ne& monitoring architecture that &as introduced &ith !elease *.+. This section describes the main parts of the monitoring architecture and ho& they &ork together.
The Monitoring Architecture
,ere is ho& the monitoring architecture and the alert monitor &ork$ Data Collection Methods$ These are programs that gather information on different parts of the !"# System and its environment. They then register this information &ith the monitoring infrastructure. The monitoring architecture comes ready to use &ith collection methods for all of the most important components of your !"# System and environment. hen you start the alert monitor, you &ill see that collection methods are already active for reporting on all of the follo&ing$ The host systems on &hich your !"# System is running The !"# database !"# instances %application servers' and their services and components Components outside the !"# System
There is nothing that you have to do to prepare or activate the monitoring architecture. All collection methods in your system are started automatically &hen the system starts or as they are needed.

Monitoring architecture$ -ata Collection methods pass their information to the monitoring architecture. The monitoring architecture provides an infrastructure for gathering and managing system information. The infrastructure concept means that collection methods are independent of the monitoring architecture. -ata Collection methods .plug into. the monitoring architecture and use its services for displaying and managing system information. /ut -ata collection methods are not programmed directly into the monitoring architecture. -ata Collection methods are independent of the monitoring architecture, and so can be easily added or modified. The monitoring architecture offers A/AP and C interfaces &hich any !"# or e0ternal programmer can use to create a collection method. Monitoring objects and attributes: -ata Collection methods report their information &ith respect to one or more monitoring ob1ects %as sho&n by the arro&s in the illustration'. A monitoring ob1ect represents something in the !"# System or its environment that should be monitored. A monitoring attribute represents one type of information that is to be reported on a monitoring ob1ect. (0ample$ Monitoring ob1ects include the CP2 in your host system, the database, and !"# services, such as background processing. Monitoring attributes for a CP2 ob1ect might include the five3minute average CP2 load and the CP2 utili)ation. Monitoring ob1ects and their attributes are displayed to you in the alert monitor. In the alert monitor, ob1ects and their attributes are called nodes or monitoring tree elements %MT(s'. Monitoring ob1ects are created by collection methods. All the ob1ects that you can currently monitor in your !"# System are automatically available &hen you start the alert monitor. Data Consumers$ This is the layer of the monitoring architecture for displaying alerts and status data. -ata consumers are supplied &ith the information that collection methods pass to the monitoring architecture. SAP delivers a standard .data consumer. %the alert monitor' &ith your !"# System. SAP also provides other, more speciali)ed monitors that use the data provided by the monitoring architecture.
The data consumer layer %the alert monitor' is your &orkplace for displaying the current state of your system and responding to alerts that are triggered by &arnings or problems. The alert monitor displays its information and alerts to you in a hierarchical monitoring tree. If a data collection method reports a problem, then the monitoring architecture triggers an alert. This is also visible to you in the alert monitor. 4or e0ample, if the CP25s five3minute load average is too high, then the alert monitor triggers a .yello&. %&arning' or .red. %problem' alert. The color3 coding in the alert monitor lets you see an alert fast. And the alert monitor can then provide you &ith detailed information on the alert as &ell as access to a method for analy)ing the alert. The follo&ing methods e0ist for analy)ing the alerts$ Auto-Reaction Methods These methods start automatically &hen an alert is triggered. Almost no assignments are made in the standard SAP system6 ho&ever, there are several predefined auto3reaction methods in the monitoring architecture that you can assign to any MT( classes$ Send an (3Mail (0ecute an 7perating System Command
&

(0ecute an Auto3!eaction in the Central Monitoring System
Analysis Method This method allo&s a detailed analysis of error situations &ithout leaving the Alert Monitor. 8ou start an analysis method manually &hen you &ant to display information or investigate an alert. An analysis method is, for e0ample, an A/AP program for displaying information about a node in the monitoring tree and for collecting information about the problem that triggered an alert in this node.
. !perating the Alert Monitor

3.1Purpose
The follo&ing section contains a short overvie& of the operation of the Alert Monitor.
3.2Process Flow
To perform a a periodic check of your monitored systems, follo& the procedure belo&$ 9. Start the alert monitor by calling transaction !:;+.The system displays the CCMS Monitor Sets screen. (very monitor set contains monitors that deliver information for a particular system management topic. (0pand a monitor set and choose the re<uired monitor by double clicking it. 8ou can copy, change, and create ne& monitor sets and monitor. The icons after the monitor sets display &hether a monitor set &as delivered by SAP % ' or created by the customer % ', and &hether you are authori)ed to change the set % ' or not % '. ;. The system displays the tree structure of the desired monitor. The system is displaying the Current Status vie& in &hich you can monitor the current values of your monitoring attributes. If you &ant to analy)e an alert, choose the corresponding monitoring tree element %MT(' by double clicking it. #. 8ou can then check &hat has happened since the last check in the system. 2se the Open Alerts monitoring vie& to see if there have been yello& or red alerts %&arnings or problems'. If you choose an alert in this vie& by double clicking it, the system displays the Alert bro&ser. This displays all alerts that have not yet been analy)ed in a flat hierarchy. *. After you have analy)ed an alert and taken the necessary action, set it to Completed to remove it from the display of open alerts.
". #lements o$ the Alert Monitor

The follo&ing section describes the most important elements of the Alert Monitor and their relationships to each other.
4.1 Purpose
hen you start transaction !:;+, the system first displays the These monitor sets group the monitors.
onitor sets available to you.
"

A monitor set usually consists of different monitors. A monitor is a collection of monitoring tree elements %MT(s' in a hierarchical structure that deliver information for a particular aspect of system management. The hierarchical structure of a monitor is the alert monitoring tree. In this tree, you can check the status of your IT system landscape. The MT(s are nodes of this tree, &here the root node also has the name of the monitor. -ifferent MT(s are (lements of the Alert Monitoring Tree$ monitoring summary nodes, monitoring ob1ects, and monitoring attributes. Monitoring summary nodes %summary MT(s' provide a better overvie& in the tree, &ithout performing a monitoring function themselves. A monitoring ob1ect represents a component of your IT environment that you &ant to monitor %such as the CP2 of a server or background processing', &hile a monitoring attribute displays a value, status, or te0t that is reported for this ob1ect %for e0ample, the CP2 utili)ation during the last 9= minutes'. If a value that deviates from the norm is reported for a monitoring attribute, the Alert Monitor generates an alert. The conditions under &hich an alert is generated, the criticality of the alert, or &hich message is assigned to an MT( > all of these are properties of an MT(. In addition to its properties, an MT( has methods$ the data collection method allo&s the collection of information about the MT(, the auto3reaction method and analysis method are e0ecuted as a reaction to an alert. To simplify Customi)ing, the properties and methods do not need to be edited for each MT( individually$ There are attribute groups for attributes, and MT( classes for ob1ects.
4.2 Operation and Customizing of the Elements of the Alert
onitor
#lement
!peration
Customi%ing Creating an# E#iting Monitor 'ets
Monitor set Transporting Monitor 'ets an# Monitor *e!initions Cop1ing an# *eleting Monitors Monitor 'tarting an# Changing Monitors Creating an# Changing Monitors Actions in the Alert Monitoring Tree Alert Tree Monitoring 'electing -o#es in the Alert Monitoring Tree *e!ining6 ,eleasing6 an# Transporting Metho#s
Metho#s
'tarting Metho#s
'electe# Alert Monitor Metho#s Properties o! Per!or ance Attri0utes Properties Properties o! 'tatus Attri0utes
Alerts
7an#ling Alerts
MTE Classes an# Attri0ute 8roups
,ule -o#e: ,ule *escription an# )se
&. Creating and #diting Monitor 'ets

!.1 "se
Monitor sets simplify system administration, as they combine monitors. (very SAP !"# system already contains the standard monitor sets delivered by SAP. These sets can only be changed by SAP. 8ou can also create, edit, copy, and delete your o&n monitor sets. To be able to edit standard monitor sets, you must first copy them to your o&n monitor sets. ith your o&n monitor sets, you can use the attributes of the set to determine &ho may edit the set and &hether the set is to be visible to all users. 8ou can also transport your o&n monitor sets and monitor definitions.
!.2 Prere#uisites
To be able to edit a monitor set or a monitor definition, you must first activate the maintenance functions.
!.3 Procedure
To call the individual functions in the table, choose CCMS Control/Monitoring Alert Monitor, or call transaction !:;+. Choose Extras Activate Maintenance Functions.
(unction
Menu )ath
Create Monitor Set
Choose Monitor (set) Create % '6 choose Create Monitor Set; define the name and the attributes of the set on the Create Monitor Set screen.
Change Monitor Set
Select the desired monitor set6 choose Monitor (set' Change % '6 on the Edit Attributes o a Monitor Set screen, change the desired attributes.
Copy Monitor Set
Select the desired monitor set6 choose Monitor (set) Cop! % '6 on the Cop! Monitor Set screen, enter the name of the copy of the set.
-elete Monitor Set
Select the desired monitor set6 choose Monitor (set) "elete % '6 confirm the command.
1.
*. Transporting Monitor 'ets and Monitor De$initions

$.1 "se
8ou can transport monitor sets to other systems in your transport landscape. This is only necessary for the monitor sets that you create yourself, as the monitor sets provided by SAP are already available in all SAP systems. If you &ant to use the definitions of individual monitors in other SAP systems, &e recommend that you e0port them as an ?M@ file and then import them. To do this, you must store the monitor definition in a file in ?M@ format in the source system6 this is then imported into the target system. This e0change is faster, as no SAP transports must be created. 8ou can also distribute e0isting monitor definitions <uickly over the Internet or a file server in ?M@ format.
$.2 Prere#uisites
To transport a monitor set or a monitor definition, you must first activate the maintenance functions.
$.3 Procedure
The transport o$ monitor sets uses the SAP transport mechanism. To do this, choose CCMS Control/Monitoring Alert Monitor, or call transaction !:;+. The system displays the CCMS Monitor Sets screen. 2. Choose Extras Activate Maintenance Functions. #. Choose the monitor set that you &ant to transport, and choose #ransport Monitor Set % *. (nter a orkbench re<uest &ith the desired target system. 1. The transport o$ a monitor de$inition uses the e0port and import of the definition in ?M@ format. To do this, choose CCMS Control/Monitoring Alert Monitor, or call transaction !:;+. The system displays the CCMS Monitor Sets screen. 2. Choose Extras Activate Maintenance Functions. 3. Choose the monitor for &hich you &ant to e0port the definition and then choose Monitor "ispla! Monitor "e inition. 4. The system displays the "ispla! Monitor "e inition screen. Choose Monitor "e inition Export. (nter a file name and path to &hich you have access from the target system. &. S&itch to the target system, and choose CCMS Control/Monitoring Alert Monitor, or call transaction !:;+. The system displays the CCMS Monitor Sets screen. 6. Choose Extras Activate Maintenance Functions. A. Create a ne& monitor. To do this, select the desired monitor set and choose Create % '. 1.
11
CCMS- Automatic Alert Notification- Configuration Guide %. Choose Monitor Definition Import and specify the file name and path entered
above.
NOTE: If the monitor definition already e0ists, this is over&ritten by the import of a definition
+. Creating and Changing Monitors

%.1 "se
8ou can <uickly and easily create your o&n monitors that meet your o&n special re<uirements. If, for e0ample, you &ant to monitor the interaction bet&een your CP2s, the operating system paging, and the dialog response time of your SAP !"# Systems, you can create an Alert Monitor that contains only these monitoring tree elements %MT(s'. 8ou can decide &hether this monitor covers one or more SAP !"# Systems. To be able to create a monitor, you must first create a tree structure. 8ou have the follo&ing options for the individual nodes$ 'tatic MT# 'election 8ou can e0plicitly select MT(s for your monitor. 7nly the selected MT(s are added to the monitor, and the selection of the MT(s is not updated. Rule-,ased MT# 'election 8ou can use the rule3based MT( selection %dynamic selection' to create your o&n monitor. In this case, the Alert Monitor inserts all MT(s that meet a certain rule into your monitor. If the MT(s that meet the rule change, the system automatically updates the monitor. In this &ay, your monitor is automatically updated if a ne& SAP !"# System is added to the Alert Monitor. &ip$ 8ou can combine static and rule3based MT( selection in the same monitor. -irtual MT#s 8ou can define virtual MT(s to structure your monitor. Birtual nodes are used as titles or headings in the Alert Monitor. They have no function other than to group monitoring tree elements visually. 4or e0ample, you can create virtual MT(s as titles for different groups of actual MT(s in your monitor.
%.2 Prere#uisites
To be able to create or change a monitor, you must first activate the maintenance functions.
%.3 Procedure
1. Choose CCMS Control/Monitoring Alert Monitor, or call transaction !:;+.
12

2. Choose Extras Activate Maintenance Function. #. Choose one of the functions from the table$
(unction
Menu )ath
Create monitor
Choose the monitor set in &hich you &ant to create the monitor6 ensure that it is a monitor set that you can modify % '6 choose Monitor (set) Create % '. (0pand the monitor set and choose the monitor that you &ant to change6 choose Monitor (set) Change % '. 8ou can also change a monitor that has already been started by choosing Monitor Change % '.
Change monitor
*. The Alert Monitor displays the complete monitoring tree. In the uppermost line of the tree, the system displays the name of the monitor. 8ou can no& either add MT(s to your monitor or display or change the properties of e0isting MT(s. To do this, choose one of the functions from the table$
(unction
)rocedure
Insert static selection
MT(
Choose the re<uired MT(s from the list of Selectable M#Es . 7nly the selected MT(s are visible in the final monitor. The system displays the list at every point in the monitoring tree &here you can insert statically created MT(s.
Insert rule3based MT( selection
Choose the node under &hich you &ant to insert a rule3based node6 choose Edit Create $ode % ', and in the Create $ode screen, choose the %ule $ode radio button
Insert a virtual MT(
Choose the node under &hich you &ant to insert a virtual node6 choose Edit Create $ode % ', and in the Create $ode screen, choose the &irtual $ode radio button. (nter a name for the node.
Change node
Select the relevant node6 choose Edit Change $ode % '. 8ou can change different properties depending on the type of node.
13
-isplay node
Select the relevant node6 choose Edit "ispla! $ode % '. The system displays different properties depending on the type of node.
-elete node
Select the relevant node6 choose Edit "elete $ode % node is deleted, along &ith its subnodes.
'. The
&ip' The follo&ing rules apply to the se<uence of nodes in the monitoring tree$ &. The root node %uppermost node' of a monitor is al&ays a virtual node. Its name is the name of the monitor. 8ou can create as many levels of virtual MT(s as you &ant. A virtual node can only be placed under a rule node or another virtual node in the tree hierarchy. A rule node can only be placed under a virtual node or another rule node in the tree hierarchy. A static node can only be placed under a virtual node. To save your monitor, choose Monitor de inition Save or 'enerate Monitor % '. If you are creating a ne& monitor, the system prompts you to enter a name for your monitor.
14
.. Rule /ode: Rule Description and 0se

(.1 )efinition
A rule node or rule monitoring tree element specifies a rule that defines &hich nodes should be included in a monitor. The monitoring architecture interprets the rule and includes monitoring tree elements in the monitor that match the selection criteria specified in the rule. The rules are regularly reinterpreted, meaning that a monitor of your o&n automatically matches the current system landscape. A monitor defined &ith rules &ill, for e0ample, automatically include a ne&ly started SAP application server. In this &ay, a monitor that consists of rule MT(s has the follo&ing properties$ The monitor automatically contains different MT(s
1&

The monitor automatically ad1usts to the current status &hen changes are made to your system landscape
!ules allo& the dynamic selection of MT(s using selection criteria. 7n the other hand, &ith static selection, you e0plicitly select individual MT(s. These are not update if changes are made to the system landscape.
(.2 "se
hen creating a rule MT(, select a predefined rule for the selection of MT(s for your ne& monitor. The Alert Monitor interprets this rule and selects the MT(s that match the specified selection criteria. The available rules are$ CCM'1D#(2/#1R 1'3'T#M' This rule creates virtual MT(s for SAP !"# Systems that are included in the monitor. 2se this rule to set up rule3based monitoring of one or more SAP !"# Systems. !ule MT(s that you add under this MT( are created for every selected system. 8ou can add monitoring functions by creating virtual and rule3MT(s under this MT(. The parameter %(S!stem is the name of the SAP !"# System that is to be monitored in the corresponding monitor. Additional selection options are )A**+ %all available SAP !"# Systems', CC2!!(DTE %SAP !"# System of the Alert Monitor', and all system groups that you have defined in your system landscape. CCM'14#T1MT#1,31C5A'' This rule inserts MT( classes as real nodes in the monitor. As all monitoring ob1ects and attributes are assigned MT( classes, you can use this rule to monitor certain types of monitoring ob1ects and attributes. 4or e0ample, the monitoring attribute %esponse#ime is assigned the MT( class %("ialog%esponse#ime. Aborted,obs is assigned the MT( class %(-.ServerSpecAborted,obs. As all instances of a particular MT( share the same MT( class, even beyond system boundaries, you can select monitoring ob1ects in all SAP instances and systems using the rule. *O&E' Adding MT(s by class also adds all subordinate MT(s %for e0ample, the subordinate MT(s C./0/tili1ation and 2min*oadAverage are inserted &ith the MT( class C./, although these MT(s have other MT( classes'. &+P' 8ou can display the available MT( classes using the possible entry help. As the help does not display &here an MT( class appears in the monitoring tree, it can be difficult to find the desired MT( class. To find the re<uired MT( class, open a standard monitor for the MT( in &hich you &ant to insert the monitor. Then display the MT( class of the MT( by choosing .roperties. CCM'14#T1MT#1,31C5A''1A'1-2RT0A5 CCM'14#T1MT#1,31C5A''10/D#R1C5A'' and
16

2se these t&o rules together. /y doing so, you obtain the same results as &ith the rule CCMSFG(TFMT(F/8FC@ASS6 ho&ever, the information that you re<uire is displayed in a more clearly structured format. If you choose the rule CCMSFG(TFMT(F/8FC@ASSFASFBI!T2A@, use the parameter M#EClass, to include the MT( class as a virtual node in the tree. Then choose the rule CCMSFG(TFMT(F/8FC@ASSF2D-(!FC@ASS. 8ou then specify the MT( class that you &ant to monitor as the real node in your monitor in the parameter ChildM#EClass. The rule uses the parameters M#EClass and %(S!stem from the superordinate rule %CCMSFG(TFMT(F/8FC@ASSFASFBI!T2A@'. CCM'14#T1MT#1,31C5A'' 1A/D1C52#/T This rule is largely the same as CCMSFG(TFMT(F/8FC@ASS6 ho&ever, you can also restrict the monitoring to particular clients.
CCMS_GET_MONITORING_SEGMENT_NAMES CCMS_GET_MONITORING_CONTEXT_NAMES
an#
These rules are for SAP3internal use only. Although you can e0periment &ith them, &e recommend that you do not use them in your o&n monitor definitions . CCM'14#T1A-A25A,252T31(!R1'3'T#M This rule is reserved by SAP for later use. o&n monitor definitions. e recommend that you do not use it in your
1"
Rule /ode
1%
6. 'elected Alert Monitor Methods

,.1 "se
8ou can assign methods to monitoring attributes, and access the method definitions using the Customi)ing transaction for the Alert Monitor, !:;9. A method can be a report, a function module, an SAP transaction, or a 2!@ that is to e0ecuted as a reaction to an alert. Most methods %especially data collection methods' are already assigned to their MT(s in the standard SAP system and a change to this assignment is not useful. ,o&ever, there are a number of additional methods available to you that you can assign to certain MT( classes yourself %see Assigning Methods to MT( Classes'.
,.2 Features
Analysis Methods Auto-Reaction Methods -efine Automatic Alert Dotification 8ou can assign the method CCMSF7nAlertF(mail to MT( classes in your system. If an alert occurs in this MT( class, you are informed by e3mail, fa0, or pager, even if you are not &orking in the Alert Monitor. Auto3!eaction Method$ (0ecute 7perating System Command 8ou can e0ecute any operating system command as an auto3reaction to a monitoring architecture alert. 4or security reasons, this does, ho&ever, apply only for those commands that have previously been defined in the (0ternal 7perating System Commands transaction. Setting 2p Central Auto3!eaction Methods 8ou can define central auto3reaction methods in the monitoring architecture in the conte0t of central monitoring. The auto3reaction methods are no longer started in the system, in &hich the alert occurs, but rather in the central monitoring system. In this &ay, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location.
1(
17. 'tep-by-'tep Automatic Alert /oti$ication Con$iguration

1-.1 "se
ith the monitoring architecture, you can define auto3reaction methods that are automatically e0ecuted &hen alerts occur. As of SAP /asis *.HA, you can assign the method CCMS0OnAlert0Email to MT( classes in your system. If an alert occurs in this MT( class, you are informed by e3mail, fa0, or pager, even if you are not &orking in the Alert Monitor. CCMS0OnAlert0Email can automatically dial a pager or send an e3mail or a fa0 to the follo&ing addressees$ A /usiness orkplace user in client +++
A distribution list or an e0ternal e3mail address The auto3reaction method for sending the e3mail is started at most five minutes after the alert occurs. ,o&ever, there can be a delay before the e3mail is sent to e0ternal e3mail addresses %that is, addresses of users that are not defined in client +++ of the same SAP !"# System', depending on the settings in SAP connect. 8ou should therefore set the period for the SAP connect send process to less than an hour. The message te0t of the e3mail contains the same information that is displayed in the Alert Monitor$ hat is the problemI here and &hen did it occurI hat severity and &hat color does the alert haveI
1-.2 Prere#uisites
To dial multiple pagers or to send an e3mail or a fa0 to multiple users %e0ternal recipients or recipients in client +++', you must first create a distribution list that contains the re<uired data for the recipients %pager number, name, e3mail address, fa0 number'. &+P' SAP connect must be configured in client +++, if the message is to be sent to an e0ternal address. In order to use the alert configuration you need to have the follo&ing prere<uisites 4or using the Alert Inbo0 %/SP based display program of A@M', the corresponding service has to be activated in the service maintenance transaction SIC4. Choose "e ault0host sap bc bsp sap alert inbox, and Activate in the conte0t menu. 8ou also have to activate SAP Connect. Choose SAPConnect3Eactivate
1-.3 Procedure 10.3.1Tailoring the Auto-Reaction Method

;. Call transaction !:;9.
2.
CCMS- Automatic Alert Notification- Configuration Guide 3. 3n the Methods group 0o56 select Method Definitions an# choose Display overview.
*. Select the method CCMS0OnAlert0Email and choose Edit "ata. &. Choose change mode &ith the "ispla! Change % ' pushbutton, and choose the .arameters tab page. H. 4ill out the fields as follo&s$
)arameter S(D-(! !(CIPI(DT
Description SAP username of the person in &hose name the e3mail is sent SAP user name of the e3mail recipient, distribution list, or e0ternal e3mail address6 to automatically send an e3mail to multiple e0ternal e3mail addresses, you must create a distribution list in client +++ that contains these e0ternal addresses. If the user is not defined in client +++ you must also specify the system and the client in &hich the user e0ists %such as C99$++#$PA!J(!K'. Indicator for the address type
!(CIPI(DT3 T8P( I-
&+P$ 2sers that are defined in the SAP !"# System in clients other than +++ cannot be specified in the /usiness orkplace directly as sender or recipient6 they are regarded as e0ternal recipients. 8ou should therefore specify the address type ! %remote address' for client3specific senders and recipients in the Parameters tab page. If you &ant to define different recipients for different alerts, copy the method definition of CCMSF7nAlertF(mail. To do this, select the method in the list and choose Copy % '. Dote
that you must release the copied method as a data collection method again ". Save your entries.
10.3.2 Assigning the Method to the Desired Node

Start the Alert Monitor using transaction !:;+ or choose CCMS Control/Monitoring Alert Monitor. ;. Start the desired monitor from the list by double clicking it. 3. Select the desired node and choose Properties. 4. The Monitoring$ Properties and Methods screen appears. Choose the Methods tab page and then choose the Method Assignment pushbutton . &. The Monitoring$ Methods screen appears. The rest of the procedure depends on &hether you &ant to assign the analysis method only to this node or to the entire MT( class . 1.
10.3.3 Assign Analysis Method to Only this MTE

Choose change mode &ith the "ispla! Change % ' pushbutton, and choose the Analysis tab page. ;. In the Method Assignment group bo0, choose the Method Dame radio button and enter CCM'1!nAlert1#mail in the associated field. 3. Save your entries. 1.
21
10.3.4 Assign Analysis Method to the elected MTE !lass

1. Choose the name of the MT( class in the header data of the screen by double
clicking it, and then choose the change mode &ith the "ispla! Change % ' pushbutton. ;. In the Analysis Method group bo0, choose the Method Dame radio button and enter CCMSF7nAlertF(mail in the associated field. Save your entries
22
11. 'A) Connect

11.1 Purpose
SAPconnect provides a standard interface for e0ternal communication, &hich supports sending &ith telecommunication services, such as 4A?, te0t message %pager"SMS', Internet mail, and ?.*++, as &ell as sending to printers and bet&een different SAP systems. It enables e0ternal communication components to be connected to the SAP system. SAPconnect provides a direct connection to the Internet using the SMTP plug3in of the SAP eb Application Server. This enables you to send and receive Internet mails &ithout the need for an additional e0ternal communication system, as &ell as fa0es and te0t messages %pager"SMS'. The SMTP plug3in is available for Internet mail as of SAP eb AS H.9+, and for fa0 and te0t messages %pager"SMS' as of SAP eb AS H.;+
11.2 Features
SAPconnect can be used to connect to various communication components and communication systems, such as$ SMTP plug3in ,TTP plug3in 4a0 servers, te0t message %pager"SMS' servers, SMTP gate&ays, or ?.*++ gate&ays, &hich support the SAPconnect !4C interface %provided by SAP soft&are partners' 7ther SAP systems Printers
23
11.3 Procedure to Configure . &P

To configure the node for sending Internet mail, you$ -ouble click on SMTP using transaction code SC7T. Give description . Specify the mail server to &hich outbound mails are to be passed in Mail 3ost and Mail .ort. Choose Set ad1acent to 4nternet. Specify the address areas of recipient addresses that are to be reached via this node. This is usually * if all e3mails are to be sent using SMTP. (nter output formats for SAP documents. The follo&ing settings are recommended here$ SA.script/Smart Forms PDF
A-A. *ist
HTM
-usiness Ob5ect/*in6
HTM
%A7 #ext Confirm.
TXT
24
If you &ant to configure the node for sending fa0es as &ell, you$ Choose Set ad1acent to Fax. Specify the address areas of recipient addresses that are to be reached via this node. This is usually * if all fa0es are to be sent using SMTP.
SA.script/Smart Forms
PDF
A-A. *ist
PDF
-usiness Ob5ect/*in6
TXT
%A7 #ext
TXT
(nter output formats for SAP documents. The follo&ing settings are recommended here$
2&

(nter the domain of the fa0 server or fa0 provider under Conversion into 4nternet Address. The system generates the local part of the Internet address automatically. The address then has the format FAX=+RecipientNumber@Domain. Confirm.
If you &ant to configure the node for sending te0t messages %pager"SMS' as &ell, you$ Choose Set ad1acent to .ager (SMS). Specify the address areas of recipient addresses that are to be reached via this node. This is usually * if all te0t messages %pager"SMS' are to be sent using SMTP. (nter the domain of the te0t message %pager"SMS' server or provider under Conversion into 4nternet Address. The system generates the local part of the Internet address automatically. The address then has the format SMS=+RecipientNumber@Domain. Confirm.
11.4 .end /o0

(3mails sent from an SAP application are merely put into a <ueue. A periodic background process, kno&n as the SAPconnect send 1ob, takes the e3mails from this <ueue and sends them via the Internet. To schedule this 1ob from SAPconnect administration, you$ Choose &ie8 ,obs. If there is not already a 1ob scheduled, choose ,ob Create. (nter a 1ob name and confirm. Select the variant SAP&CONNECTA by placing the cursor on it. Choose Schedule ,ob. Choose Schedule .eriodicall!. (nter an appropriate time period, such as !" minutes. Choose Create.
11.! +n0ound
If you &ant inbound e3mails to a specific address or &ith a specific content to automatically start a program that processes these e3mails, you can configure this under Settings 4nbound .rocessing9 If you &ant inbound e3mails to a specific address or from a specific sender to be automatically redirected to another recipient or distribution list, you can configure this under Settings 4nbound "istribution9
12. Creating Distribution 5ists

12.1 Procedure 12.1.1 !reating a Distri"ution #ist in the Distri"ution #ist earch
9. Go to /usiness orkplace using transaction S/ P, choose ;. The distribution list search screen is displayed. "istribution lists9
26

In the frame Find distribution lists: select &hether you &ant to create a private or a shared distribution list.
#. Choose
The distribution list maintenance screen appears on the tab page Attributes9 *. Specify the attributes of the distribution list. =. S&itch to the tab page "istribution list content. H. Specify the recipient addresses and for each one the corresponding recipient type. A. In addition, you can assign the send attributes Express: Cop! and -lind cop! to each recipient. hen sending to an e0ternal address, you can also specify that documents are to be sent to another address from the address management rather than to the standard address. L. Choose .
12.2 1esult
The distribution list is created and can be used on the send screen, for e0ample, or in other places in the !"# System &here a specific user group has to be specified.
1 . Address Type
13.1 )efinition
Type of recipient address or sender address. An address type can be one unit %for e0ample, address name' or several units %for e0ample, shared distribution list'. Some address types
2"

determine the communication method by &hich the document is sent %for e0ample, an Internet address or a fa0 number'.
13.2 "se
hen an address is specified, for e0ample on the send screen, the corresponding address type must be assigned. The address type can be entered automatically. The follo&ing recipient types are available in the /usiness orkplace$
Recipient Type
#8ample
2ndicator
Address name
Anna
ilson
SAP user name
ilsona
(0ternal address
(d&ard Miller
Private distribution list
4avorite colleagues
Shared distribution list
Archiving pro1ect
4a0 number
2SA 9;# *=H ALM+ %
#countr$%co&e%'%(a)%number*)
Internet address
anna.&ilsonNour.company.com
7rgani)ational ob1ect
Purchasing %7rgani)ational unit'
/usiness ob1ect
7ffice folder
!emote SAP name$
C99$+++$&ilson %
#S$+tem%name,C-ient,Name*)
?.*++ address
gOanna6sO&ilson6oOc996ou9Om+++6pOcompany6aOdbp6cOus
@-AP address
COusa"oOc99"ouOm+++"cnOP
2%
1".
Auto-Reaction Command
Method:
#8ecute
!perating
'ystem
14.1 "se
8ou can e0ecute any operating system command as an auto3reaction to a monitoring architecture alert. 4or security reasons, this does, ho&ever, apply only for those co an#s that ha9e previously been defined in the External Operating S!stem Commands %SMHM' transaction.
14.2 Prere#uisites
If an auto3reaction method calls the operating system command, the follo&ing parameters are transferred to the command6 ensure that the command can process these parameters in the follo&ing se<uence: )arameter ).A%AM;+ ).A%AM<+ )S=S4"+ )"A#E+ )#4ME+ )SE&E%4#=+ )CO*O%+ )S3O%#$AME+ )O-,EC#+ )MESSA'E+ Short name of the monitoring attribute and the name of the monitoring ob1ect in &hich the alert &as triggered Message that is assigned to the alert Severity and color of the alert that triggered the auto3reaction. Description 4i0ed parameter that is defined in transaction SMHM in the .arameter or Operating S!stem Command field %optional' Additional parameter, that is defined in the definition of the auto3 reaction method under .A%AME#E%S %see belo&' %optional' System I- of the system in &hich the alert occurred -ate and time of the alert
8ou must no& define the desired operating system command in the (0ternal 7perating System Commands transaction. To do this, follo& the procedure belo&$
1. Choose CCMS Configuration External Commands6 or call transaction SMHM.
2(
CCMS- Automatic Alert Notification- Configuration Guide 2. Choose change mode &ith the Display Change % ' pushbutton, and choose Create : ;. 3. Do& enter the details for the desired operating system command and save your entries.
&+P' Dote that during the definition of the auto3reaction method, you must no longer enter the name of the operating system command, but rather the name of the %logical' command. In the .arameter or Operating S!stem Command , enter the fi0ed parameter ).A%AM;+ that is to be transferred to the command %optional'. (nsure that the Additional parameters allo&ed indicator is activated.
14.3 Procedure 14.3.1 !o$y Method

e recommend that you leave the original method CCMSFA2T7F!(ACTF7PFC7MMADunchanged and use it only as a template for your methods. In this &ay, you can set up as many logical commands as you &ish as auto3reactions.
1. Choose CCMS Configuration Alert Monitor6 or call transaction ,<21. 2. 3n the Methods group 0o56 select Method Definitions an# choose Display Overview. 3. Select the method CCM'=A)TO=,EACT=OP=COMMA-* and choose Copy : ;. 4. (nter the desired name and save your entries.
14.3.2 Ad%ust Method &ara'eters and Release Method

8ou must no& specify the desired logical command in the method that you have created and release the method as an auto3reaction method.
1. Select the copy of the method that you have 1ust created and choose Edit Data : ;. 2. The Monitoring: Methods screen appears. Choose change mode &ith the Display Change % ' pushbutton. 3. Choose the .arameters tab page. 8ou can set the follo&ing parameters here:
)arameter COMMA$" .A%AME#E%S %EAC#0O$0A*E%#S Description @ogical command that is to be e0ecuted in the case of an alert Additional parameter ).A%AM<+ that you &ant to transfer to the command %see above' Color of the alert at &hich the auto3reaction method is to be started$ for red and yello& alerts % .E O/' or only for red alerts %RED' RED De$ault
3.
&+P' The COMMA$" parameter is re<uired, all other parameters are optional.
4. Choose the %elease tab page and in the Execute Method as group bo0, select Auto> %eaction Method. =. Save your entries. &+P' /y default, the operating system command is e0ecuted on the local server of the MT( that generated the alert. If the command is to be e0ecuted on a different server, change the e0ecution location on the Execution tab page in the Execute Method On group bo0.
14.3.3 Assign Method to Desired MTE !lasses

8ou must no& assign the method to the desired MT(s or MT( classes. 8ou can use either transaction !:;+ %only for the active properties variant' or transaction. Assignment using transaction !:;+ is described belo&$
1. Start the Alert Monitor using transaction !:;+ or choose CCMS Control"Monitoring Alert Monitor.
;. Start the desired monitor from the list by double clicking it. #. Select the desired node and choose .roperties. *. The Monitoring$ Properties and Methods screen appears. Choose the Methods tab page and then choose the Method Assignment pushbutton. =. The Monitoring$ Methods screen appears. The rest of the procedure depends on &hether you &ant to assign the analysis method only to this node or to the entire MT( class.
14.3.4 Assign Analysis Method to Only this MTE

1. Choose change mode &ith the "ispla! Change % ' pushbutton, and choose the Auto3!eaction tab page. ;. In the Method Assignment group bo0, choose Method Dame and, in the associated field, enter the method that you created as described above. #. Save your entries.
14.3.( Assign Analysis Method to the elected MTE !lass

1. Choose the name of the MT( class in the header data of the screen by double clicking it, and then choose the change mode &ith the "ispla! Change % ' pushbutton.
;. In the Auto3!eaction Method group bo0, choose Method Dame and, in the associated field, enter the method that you created as described above. #. Save your entries.
31
14.4 1esult
If an alert is triggered for one of the MT(s to &hich you have assigned this auto3reaction method, the monitoring architecture automatically calls the logical command &ith the parameters ?).A%AM;+@ ?).A%AM<+@ )S=S4"+ )"A#E+ )#4ME+ )SE&E%4#=+ )CO*O%+ )S3O%#$AME+ )O-,EC#+ )MESSA'E+.
1&. 'etting 0p Central Auto-Reaction Methods

1!.1 "se
In the monitoring architecture, you can react automatically to an alert using auto3reaction methods. These methods are automatically started in the case of an alert and by default are e0ecuted in the system in &hich the alert occurs. As of SAP eb Application Server H.9+, you can define central auto3reaction methods in the monitoring architecture in the conte0t of the central monitoring of mySAP.com components. The auto3reaction methods are not started in the system, in &hich the alert occurs, but rather in the central monitoring system. In this &ay, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location.
1!.2 Prere#uisites
The central monitoring system %abbreviated to C(D in the follo&ing' has a release status of at least SAP eb Application Server H.9+. The monitored mySAP.com components &ith SAP /asis have at least SAP /asis *.H/ &ith a kernel as of *.H- AJJ patch level HM;.
The monitored mySAP.com components &ith SAP /asis are linked &ith C(D using the CCMS agent SAPCCM*?. The agent must have a release status of at least version H.9+. 8ou can determine the version of the CCMS agent by calling it &ith the option -9 %such as$ sapccm"8 -9'. The version is the number after the term kernel %Such as$ ;++9+99+, compiled at Aug 9M ;++9, kernel *177F+F9+* platform ++;#+F#;bit'. &+P' Monitored mySAP.com components &ith SAP /asis #.9 and systems and components that are centrally linked using the SAPCCMS! agent %such as values in the 7perating System Monitor' formally belong to C(D %see Monitoring SAP !"# #.0 Systems'. Therefore, auto3reaction methods
32

can al&ays be started centrally here. 8ou can therefore find the relevant MT( classes in the list of the MT( classes of C(D.
1!.3 Constraints
8ou cannot assign any central auto3reaction methods to the MT( classes that belong to the application servers of C(D as described belo&. In this case, use the conventional assignment using a local auto3reaction method.
1!.4 Procedure 1(.4.1 &er)or' all con)iguration ste$s )or the central auto-reaction 'ethod only in !EN.
1. Choose CCMS Con iguration Alert Monitor, or call transaction !:;9. 2. The MonitoringA .roperties and Methods screen appears. Choose #echnical
4n rastructure Assign Central Auto>%eactions. #. The system displays the Maintain Central Auto>%eactions screen. 7n this screen, you can perform all &ork steps to define, assign, and edit central auto3reaction methods. A normal first step is to create a central auto3reaction method from an e0isting %local' auto3 reaction method and to then assign this to the desired MT( class in the desired system. 8ou can make the follo&ing settings$
1(.4.2 !reating* Editing* or Deleting a !entral Auto-Reaction Method

8ou can e0ecute any auto3reaction method centrally that is defined as an auto3reaction method in the central system. The method does not need to be kno&n in the monitored system. 8ou can also use the predefined auto3reaction methods of the monitoring architecture for this. These are, for e0ample: Automatic Alert Dotification Automatic (0ecution of 7perating System Commands
To a!e an e"isting auto-reaction met od e"ecuted centrall#$ follo% t e &rocedure belo%' 1 In the sub&indo& "e ined Central Auto>%eactions, choose Create % '. 7n the follo&ing dialog screen, enter the desired auto3reaction method in the input field ne0t to the Create 8ith #emplate pushbutton, or use the input help, &hich provides a list of all released auto3reaction methods. Choose Create 8ith #emplate.
&+P' 8ou can also use an e0isting central auto3reaction method as a template for a ne& auto3 reaction method. To do this, select the desired method in the "e ined Central Auto>%eaction subscreen and choose Cop! % '.
2. The MonitoringA Methods screen appears. The settings are copied from the template, &ith the e0ception that the indicator Onl! in central s!stem: triggered b! CCMS agent is activated in the Execute Method group bo0 of the Control tab page.Therefore, you do not 33

usually need to change the settings, other than to enter a name for the central auto3reaction method. #. Save your entries. The system then displays the method immediately in the "e ined Central Auto>%eactions subscreen.
To create a ne% central auto-reaction met od$ follo% t e &rocedure belo%: 1. In the sub&indo& "e ined Central Auto>%eactions, choose Create % '. In the follo&ing dialog screen, enter the desired name for the method in the input field ne0t to the Create pushbutton and choose Create. ;. The MonitoringA Methods screen appears. (nter the desired settings for the method %for more information about creating auto3reaction methods, see -efining, !eleasing, and Transporting Methods', and ensure that you activate the radio button Onl! in central s!stem: triggered b! CCMS agent. #. Save your entries. The system then displays the method immediately in the "e ined Central Auto>%eactions subscreen.
To edit a central auto-reaction met od$ follo% t e &rocedure belo%' 1. In the "e ined Central Auto>%eaction Methods subscreen, select the desired method and choose Edit. ;. The MonitoringA Methods screen appears. Make the desired changes to the method definition and ensure that the selection field Onl! in central s!stem: triggered b! CCMS agent is activated. #. Save your changes. To delete a central auto-reaction met od$ follo% t e &rocedure belo% 1. In the "e ined Central Auto>%eaction Methods subscreen, select the desired method and choose "elete % '. ;. Confirm that you &ant to delete the method. If the method is used in an assignment, the system &ill also inform you of this, and ask &hether you &ant to delete the method and all of its assignments.
1(.4.3 Assigning a !entral Auto-Reaction Method

(nter the MT( classes and system to &hich you &ant to assign a central auto3reaction method. The system checks the assignment regularly. 9. In the S!stem 4" subscreen, select the desired systems, and the desired MT( classes in the M#E Class subscreen, to &hich you &ant to assign a central auto3reaction method. 8ou can al&ays select multiple systems and MT( classes.
34

&+P' -ifferent systems usually have different MT( classes. After calling the function, the MT( classes of the local system are displayed first. To include the MT( classes of other systems in the list, select the desired systems and choose M#E Classes o S!stem % '. The system then displays the MT( classes of the selected system in the list of MT( classes. ;. In the "e ined Central Auto>%eactions subscreen, select the desired method that you &ant to assign to the selected MT( classes of the selected systems. #. Choose Assign Central Auto>%eaction Method % '. The system then immediately displays the corresponding assignments in the lo&er subscreen. Perform these steps for all desired central auto3reaction methods.
1(.4.4 Assigning a !entral Auto-Reaction Method )ro' the Alert Monitor

In practice, of the procedures described here, you &ill use the assignment of MT( classes to a central auto3reaction method most fre<uently. To make this procedure simpler, you can also call it directly from the Alert Monitor %transaction !:;+'.
1. 'tart the Alert Monitor 01 calling transaction ,<2.. 2. Acti9ate aintenance !unctions 01 choosing Extras Activate Maintenance Functions. 3. E5pan# the onitor set that contains the onitor that 1ou re+uire6 an# choose *oad Monitor6 or #ou0le clic> the #esire# onitor.
*. Select the MT(s to &hose MT( classes you &ant to assign a central auto3reaction method, and choose Edit $ode(M#E) Assignment Central Auto>%eaction Method. &+P' In this &ay, you can also very <uickly assign a central auto3reaction to all MT( classes of performance attributes in a monitor. To do this, select all nodes by choosing Edit Selections Select All nodes (M#E), before s&itching to the administration of central auto3reactions. =. The Central Auto>%eactions screen appears. The desired systems and MT( classes are selected, meaning that you no& only need to select the desired method. H. Choose Assign Central Auto>%eaction Method % '. The system then immediately displays the corresponding assignments in the lo&er subscreen.
1(.4.( Deleting an Assign'ent o) a !entral Auto-Reaction Method

In the lo&er subscreen, the system displays the e0isting assignments of central auto3reaction methods. To delete assignments, select one or more ro&s of this table and choose "elete Assignment %'. *O&E' The central auto3reaction methods are al&ays started under the user in the client that activated the central method dispatcher %to do this, choose #echnical 4n rastructure Method Execution Activate Central S!stem "ispatching in transaction !:;9'. As the client is also of great importance for automatic alert notification, ensure that you are in the client from &hich the mails are to be sent &hen you activate the central system dispatching.
3&

If you have activated the central system dispatching using the &rong user or in the &rong client, first deactivate it by deleting the 1ob SAPFCCMSFC(DS8SF-ISPATC,(! in transaction SM#A. The 1ob is controlled by the event SAPFCSMFT!IGG(!FC(DS8SF-ISPATC,. Then reactivate the central system dispatching using the correct user in the desired client.
1!.! 1esult
Alerts in the assigned MT( classes of the monitored systems no& trigger an auto3reaction in the central monitoring system.
36

CCMS-Automatic Alert Notification - Configuration Guide

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

CCMS-Automatic Alert Notification - Configuration Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

CCMS- Automatic Alert Notification- Configuration Guide