Skip to Content
author's profile photo Former Member
Former Member

XI alerting setup.


In our XI production system, some times there many messages in sxmb_moni fails with the error "HTTP_RESP_STATUS_CODE_NOT_OK", when we restart the message it getting processed . I am not sure what is the cause for this.

however there is job RSXMB_RESTART_MESSAGES scheduled for every two hours to restart the failed messages.many times we are processing the messages manually.

We are planing to setup a alerting for this, when ever there is failed message in sxmb_moni, trfc and qrfc, we need a alerting to be generaeted. can you pls help me how to proceed with the alerting setup.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Dec 04, 2007 at 06:36 AM


    For email alerts, use these blogs:





    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 06:41 AM

    Hi Venkatesh,

    First you will have to configure Alert Category for your interface in transaction AlRTCATDEF on XI system. You'll have to populate container with standard variables for capturing error information and create short & long texts for alert messages. Also, you'll have to mention recipients of alerts. Recipient can be based on specific user(s), role(s) or both.

    Then in RWB, click on ‘Alert Configuration’ tab.

    Scroll to the bottom, and click ‘Update Table’ to retrieve the new Alert Categories.

    ‘Select Alert Category’, enter the specific error(s) to be alerted, and Conditions as necessary and Click ‘Add Rule’.

    In 'Alert Inbox’ in RWB. Click ‘Subscription’.

    I have a small document on alert configuration so please let me know your email id and I'll mail the same to you.


    Prashant Rajani

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 10:04 AM

    Hi vanktesh


    inside this message you will see a error category like this "some service (*) is not available conection request to this service refused etc...." This error occurs when the message request for some service and that service is not available at that time might be the reason --- service is engaged at that time or service may be doen at that request time or it may also that service is up but the port is down at that time.

    So you can check through telnet ang ping your service check at that time whether your port is open.

    adding furher to this error code there are various category like 401 -unauthorised access , 402, 403....

    for full description of these error code you can follow this link

    for alert configuration take the help

    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration

    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config



    PS: if helpful plz reward points

    Message was edited by:

    sandeep sharma

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      For raising these types of errors so what you can in this case is you need to create a alert rule for this kind of errors. Refer the point no 8 for the same.

      Refer the below help for the same.

      For raising an alert you need to first configure the alert please follow the below weblog written by Michal Krawczyk


      Configuration steps are: go to transaction ALRTCATDEF

      1) Define Alert Category

      2) Create container elements which are used for holding an error messages.

      3) Recipient Determination.

      Alert can be triggered in different ways.

      1) Triggering by Calling a Function Module Directly.


      2) Triggering by Calling a Function Module in the Workplace Plug-In.

      3) Triggering with an Event Linkage.

      4) Triggering with the Post Processing Framework (PPF) or Message Control (MC)

      5) Triggering from a Workflow.

      6) Triggering from CCMS with autoreaction.

      7) Triggering from BPM.



      8) Triggering alert by configuring a rule from RWB.

      Hope this will help you.

      Thanks and Regards,

      Chirag Gohil.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.