Skip to Content

There had been unanswered questions in the forum regarding CCMS configuration for mail alerts which made me to think about posting this blog. The entire scenario though easy, still involves a lot of configuration steps. So I decided to post them in series. This blog (chapter 1) gives a bird’s view of the steps involved in implementing the scenario and explains the initial step towards the implementation.


I start with the assumption that CCMS is configured in the XI system. If not, first XI : Configuring CCMS Monitoring for XI- Part I by Naveen Pandrangi.

The Scenario:

My case study is mailing the alert message that occurs when the execution time for a particular scenario exceeds a threshold value.  

Steps to achieve this scenario:

The existence of an active scenario (ex: a simple file to file).

Add that specific scenario in CCMS as a monitoring node.

Set the threshold value above or below which alert should be triggered.

Configure the Monitoring Tree Element with an auto reaction method which triggers E-mail when alerts occur.

Configure SAPConnect and configure SMTP.

Create job and schedule it to send all the E-mails which are in the queue

Step 1:

I start with the assumption that there exists a simple file to file scenario in action.

 Step 2:

How to add specific scenario as a monitoring node in CCMS?

Execute the transaction code: SXMB_ADM and click on Integration Engine configuration.

Click on specific configuration

Click New Entries to create two new entries

1) Category: PERF and parameters: MEASUREMENT_LEVEL with current value as 1

2) Category: PERF and parameters: MEASUREMENT_PERSIST with current value as 1

Execute transaction code  sm30

Enter table name: ALXMBPFALERT and chose maintain

Give a node name that should appear as the node in CCMS monitoring.

Give the sender and receiver interface names here. This is the scenario for which we are going to configure performance monitoring.

Save your entries.

Execute Transaction RZ20

(BXI CCMS MONITOR is the monitoring set for XI in this system (BXI).)

Now you can see the node under Message Performance by Sender/Receiver.


In this way we can add our own scenario as a monitoring node

in CCMS, thereby we can monitor the performance of our scenario. Thus this blog with adequate Screenshots I have explained the addition of our own scenario as a monitoring node in CCMS in an easily understandable manner. Hope after reading this blog the readers will be able to understand the steps said in SAP note number: 730193 with ease. Let us see the rest of the steps in executing this scenario in the forthcoming Chapters.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Gourav Khare
    Thanks for wonderful blog, One thing I want to know is can we get message Id using CCMS alert, If it is posible then how? Hope you will answere of this question in next blog.


    1. Aravindh Prasanna Post author
      Hi Gaurav,
              Sorry for the late reply.Using CCMS we can only monitor and handle alerts when triggered.The error entry in SXMB_MONI  will be available for monitoring .The entry will be maintained in a table and if you want to retreive the messageID you can do that by hitting a query to the table directly.
      1. Helge Hofmeister
        Hi Gaurav,

        nice blog!

        The table you are speaking about (the one where the error entry is maintained) – could you please tell me the name of this table?


Leave a Reply