Checklist for Implementation 

The CCMS monitoring infrastructure was designed as an open infrastructure. If a new component is to be monitored, the developers design a new data supplier, which is integrated into the CCMS monitoring infrastructure. From then on, the new data supplier delivers the most important monitoring data about the component.

In addition to the data supplier, developers define an analysis method that provides additional information about the component if a problem occurs. If necessary, an auto-reaction can also be defined, which is automatically started if an alert occurs.

The CCMS monitoring infrastructure provides the periodic start of the data supplier and the display and alert administration services. The quality and usefulness of the monitoring data for your component depend entirely on the developer of the component.

Points to Consider Before Installation

...

       1.      What information does a user require to monitor and administer your component? You also need to implicitly decide what monitoring and administering your component means:

○     Does the monitoring include one or more performance values?

○     Does it include the operator waiting for particular messages to appear?

○     Does it include a combination of these two possibilities?

Report only the most important information. Nothing is worse than an Alert Monitor overloaded with data, which is always red, and with which no customer can work. If errors occur, the analysis method can collect detailed information and display it centrally.

       2.      How can the information be collected reliably and precisely? Do you have a function module or a report that collects the required information? Can you build this function module or report into your data supplier? Does your component contain the necessary instrument to collect the required data?

       3.      How can the user react to problems (alerts)? Do you have an “analysis method” – a transaction, a report, or an external operating system command – with which the user can obtain additionally required information or take the required action to correct the problem?

       4.      Do you have a tool that can automatically react to an alert (auto-reaction method)? Or is there a standard action that is to be taken when an alert occurs (such as the informing of an administrator or the sending of a mail to a call center)?

Process Flow

...

To instrument your component for the CCMS monitoring infrastructure, proceed as follows:

       1.      Design monitoring of the component

Consider how you want to monitor your component.

       2.      Design the monitor in the CCMS monitoring infrastructure

Decide how you want to add your component to the CCMS monitoring infrastructure. This is essentially about the structure of the tree in the Alert Monitor (transaction RZ20).

       3.      Attribute design

Consider whether you require particular functions of the CCMS monitoring infrastructure to implement your design. The attribute types to be used depend on this.

       4.      Preparation for programming

Produce the prerequisites for the programming, such as preparing messages (short and long texts) for display in the Alert Monitor, preparing data collection and analysis methods, and so on.

       5.      Implementation

Perform the programming of the data supplier and the definition of the methods

       6.      Test

For detailed information about the above steps, see the following sections:

●     Decision Table: Organizational Decisions

●     Decision Table: Monitoring Attributes for the Attribute Types

If you do not have time for detailed design decisions, or simply want to create a prototype, you can copy one of the following examples reports and change them to meet your requirements:

●      Rsdssmpl_performancecreates a monitoring object and a performance attribute that displays numbers, such as:

Dialog Response Time = 1000ms

●      Rsdssmpl_singlemsgcreates a monitoring object and a status attribute that displays individual messages, such as an ABAP short dump:

Short dump: [Error SYSTEM_CORE_DUMPED occured. P1=0] (Client 000) (User SAPSYS)

●      Rsdssmpl_log creates a monitoring object and a log attribute that displays multiple messages, such as an SAP system log.

●      Productive data supplier RSDSUSER for collecting the users currently logged on to the instance (see also Data Supplier for the Users Currently Logged On).

For more information about this, see SAP Note 429381.

 Start Page Creating a Data Supplier for the CCMS Alert Monitor