Monitoring on "holding", "Delivering", "To be Delivered" status in AE

Hi Experts,
We are using CCMS alert configuration to receive alerts for errors in integration engine and System errors in Adapter engine and communication channel errors.
But, we are not able to set up alert configuration on holding, Delivering and To be Delivered status of the messages in Adapter engine of XI(PI 7.0).
Please suggest a solution where we can receive alerts on holding, Delivering and To be Delivered messages.
Regards,
Subbalaxmi

where we can receive alerts on holding, Delivering and To be Delivered messages
http://<Host>:<PORT>/rwb Message Monitoring
The AE receives the message, processes it, and forwards it to the receiver (that is, the file adapter). While the AE processes the message, it passes several statuses:
 TO_BE_DELIVERED:
The status of the message when it is initially handed over to the AE.
 DELIVERING:
The status of the message when it has left the AE queuing system and is in the process of being transmitted across the wire or delivered to an application.
 DELIVERED:
The status of the message when it has successfully reached its intended receiver.
 HOLDING:
The status of an EOIO
Regards
Pothana

Similar Messages

  • Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

    Hi,
    I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
    2014-03-26 08:39:10
    Information
    The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
    2014-03-26 08:39:10
    Information
    Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2014-03-26 08:39:10
    Information
    Message successfully put into the queue.
    2014-03-26 08:52:48
    Information
    Admin action: Trying to redeliver message.
    The connection between the receiver is ok, does this have something to do with the Communication Channels?
    Please help.
    thank you.

    Hi Eng Swee,
    there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
    this is what is indicated in the Audit Logs
    2014-03-26 02:38:47
    Information
    Admin action: Trying to fail message.
    2014-03-26 02:38:47
    Error
    The message status was set to FAIL.
    2014-03-26 02:38:47
    Information
    Admin action: The message was successfully set to status failed.
    2014-03-26 02:38:47
    Error
    Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
    2014-03-26 02:38:47
    Error
    Asynchronous error reported.
    Is this the reason why the messages are stuck?
    thank you!

  • To Be delivered status in Message monitoring

    Hi,
    There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
    any input reg. this will be appreciated.
    I didn't see any messages with TO BE delivered status in adapater engine.
    I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
    I have seen this thread  & link also.
    To Be Delivered
    Re: "To be delivered" status in RWB -- Any solution?
    http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
    I could not see any entry in SMQ1, SMQ2, SM58 also
    Thanks
    Praba
    Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
    Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

    Hi,
    You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
    Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
    I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
    Hope it will helps you
    Cheers
    Veera

  • Messages stuck in TO BE DELIVERED status

    Hi !
    Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
    These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
    This occurs no mather which adapter is the sender (RFC, File, etc.)
    The audit log is:
    2008-04-10 16:59:34
    Success
    Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2008-04-10 16:59:34
    Success
    Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2008-04-10 16:59:34
    Success
    Message successfully put into the queue.
    If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
    "Success | Admin action: Trying to redeliver message".
    We already refreshed the cache and restarted the Java stack.
    Any clues?
    Thanks !
    Regards,
    Matias.

    Hi,
    Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
    The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
    The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
    Regards,
    Srini

  • PI RWB-Messages stuck in Delivering Status

    Hi Experts,
    PI 7.1
    Scenario: Proxy to Mail (Outbound)
    QOs: Exactly Once in Order
    We are facing problem while sending messages to receiver.
    Messages are stuck in Delivering status and the messages followed by them are going into holding status.
    Messages in Delivering status has no audit logs.
    Issue has started couple of months back. We took restart initially to rectify the barrier but it is happening again. This is repetitive issue and we are looking for permanent fix. Restart is not preferred resolution as it is a production system.  Please suggest how can we overcome it? It would be a great help.

    Hi Hardik
    I've blogged about this issue recently. Please check out the blog:-
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/handling-and-preventing-messages-stuck-in-to-be-delivered-status
    Rgds
    Eng Swee

  • Messages are in to be delivered status

    Many messages are in to be delivered status in the adapter engine message monitoring
    Can any body help regarding this

    Hi Sandeep,
         Would you explain a little bit more your issue?
         i.e:
         This kind of messages are Sync Messages?
         Do you have more than one message in Interfaces Determination object?
         If multiple inbound interfaces are assigned by the interface determination, the messages are forwarded according to the quality of service Exactly Once in Order (EOIO) at runtime. This means that the order in which the inbound interfaces are entered in the interface determination determines the order in which the messages are received.
         You can change this default by deselecting the Maintain Order at Runtime checkbox. In this case, the quality of service Exactly Once (EO) is used to forward the message to the inbound interfaces.
    Regards,
    Luis Diego

  • Sender File channel in "To be Delivered" status always- PI 7.4- ICO interface

    Hello All,
    We are testing one Integrated Configuration Object (ICO) which is developed on PI 7.4 system (dual stack). Scenario is simple file to file and it doesnt have any ESR part (pass thru interface).
    Sender channel (File adapter NFS based) is picking the file from IN directory and after which it is always in "To be Delivered" status and it never passed to Receiver file channel (NFS based).
    We tried stop and starting the channel, deleted and recreated the channel, reactivated the channel, cancelled and restar the message from Message monitoring page, Cache refresh from ID and CPA cache refresh which didn't help us.
    Below is audit log of sender File channnel:
    Please help us in solving this problem.
    Thanks,

    Hi Naresh,
    Have you tried Eng Swee Yeoh advices in this blog Handling and preventing messages stuck in To Be Delivered status?, like to set timeout and the mode Per file transfer.
    Regards

  • Urgent - Messages in "To Be delivered" status

    Hi XI ers,
    We have around 150 messages in "To Be delivered" status. Tried resending a couple of them but no sucess.
    When tried to resend a message, it gives message 2 Audit log entries in MDT (Message Display Tool). The first entry is "Try to fail the message" and "Trying to resend the message"
    After that in RWB, message monitoring, the status of the message is "To Be delivered" forever.
    >>there are no queue entries (smq1 and smq2)
    >> tried cancelling the first message in the list of "To Be delivered" status.. and that did not work.
    The error being in Receiver end, there are no error entries in sxmb_moni also.
    Can any help me with what the issue could.
    Any suggestions on directing me are welcome,
    thanks,

    hey
    have a look at the followin
    Status:  TO_BE_DELIVERED
    Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
    TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
    Solution:
    This is done via the Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
    /<PROTOCOL>
    Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
    Try logging into Sap GUI with two users:  XIAPPLUSER & XIAFUSER
    to see if they are blocked 
    We can check the messages:
    AdapterFramework 
    com.sap.aii.adapterframework.serviceuser.language 
    com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
    com.sap.aii.adapterframework.serviceuser.pwd 
    ApplicationSystem 
    com.sap.aii.applicationsystem.serviceuser.language 
    com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER 
    com.sap.aii.applicationsystem.serviceuser.pwd
    in the exchange profile to make sure the right passwords
    thanx
    ahmad

  • Messages are hanged in "Delivering" status

    Hi everyone,
    I have an IDoc -> PI -> File scenario. Everything works fine until the message reaches the file adapter. In the Communication Channel monitoring there is no activity for that message, and the channel is correctly configured and started. However, in the Message Monitoring, when I filter for my receiver interfacce, I see that there are 4 messages that have been in "Delivering" status for 2 days. Then, there are a lot more messages in "To Be Delivered" which I guess are waiting for the first ones to finish.
    I stoped & started the channel, I tried to resend the messages and nothing happened. Any suggestions? Thank you very much!
    Regards,
    Pablo

    Hi Pablo,
    "However, in the Message Monitoring, when I filter for my receiver interfacce, "
    --- First Remove all the filters in the RWB,
    now set the status filter as "System Error" and select the date range for more than six months or 1 yr ...
    now if you see any message then delete them,
    Again set the status to "To Be Delivered" and delete all of them.
    now set the status to "Delvering" and restart them,
    this is what i do when ever i face this problem.
    Regards,
    Karna...

  • Message in Delivering status

    Guys,
    How do you stop messages running in scheduled state with status 'Delivering\.
    It is been in that status for couple of days.
    Am still getting error 239, connection refused from receiver FTP server.
    When i checked their log, it was in FIN_WAIT2 status.
    Please share light on this.

    Hi,
    " to be delivered" status may be because of following reasons:
    -Receiver is not available
    -Queue hang-up: check out SMQ2 for the message queue status
    -try to restart the messages from the RWB-->Message Monitoring
    -try out the accessibility of NFS folder from the PI server
    -Re-activate the Receiver file channel with Receiver agreement..
    for more on the Adapter Engine log, you can check this from the Visual Admin- log files
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Delivering Status in Messaging system

    Hi,
    I am monitoring messages in messaging system. I can see some message status as "Delivering" from so many days. I am unable to delete those messages. It is not even changing to undelivered status. Please help.
    Thanks,
    Gunasree

    Hi Gunasree,
                           The messages in the DELIVERING status can not be cancelled. The messages might have gone to delivering stage due to many reasons. If some earlier message got failed in the queue or the connection between the Receiver and adapter engine break...or some other reason.
    For messages in the delivering status it can be cancelled by stopping the adapter engine only.
    Thanks
    Ajay

  • Trigger Alert E-Mail When messages were in To Be delivered Status

    Hello all,
    Is it possible to trigger an Alert E-mail if a message struck up in 'To be delivered' status ??
    I Know this status is not an error status with AE to trigger alert automatically. We are facing this problem often and when we restart XI AF messaging system, all messages were processed.
    We would like to know if messages were struck up with that status more than 15mins.
    Any thoughts??
    Regards

    Hi,
    Standard Alert Frame work will not support sending an Alert for To Be delivered status.
    you have to do some work around,
    check below blog and apply this design
    /people/shweta.walaskar2/blog/2011/05/12/trigger-alerts-for-messages-in-to-be-delivered-status-monitoring-adapter-queue-lock
    Regards,
    Raj

  • To Be Delivered Status for AS2 messages

    Hi Experts,
        We have an issue with the EDI messages that are sent out of XI through AS2 Adapter. The messages were going out successfully till yesterday. From yesterday onwards, we see the messages under To Be Delivered Status in the Message Monitoring of Adapter Engine messages in RWB.
    We have restarted the J2EE engine and it doesn't help.
    The Service is not EOIO and hence the question of QUEUEs doesn't arise.
    Did anyone ever face such an issue? Please help.
    Regards,
    Ravi Kanth

    "To be delivered " occurs while the message is put into the Messaging System receive queue. It means that the message was successfully delivered from Integration Server and it is passed on to the Messaging System.
    - Make sure that XIAPPLUSER XIAFUSER are not blocked
    - Otherwise try retyping the passwords for XIAPPLUSER & XIAFUSER in exchanegProfile
    - Restarting would be always helpful
    Regards,
    Prateek

  • BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

    Hi All,
    I have a BPM interface running fine since 1 year.
    In this BPM I have wait step for 5 minutes.
    But yesterday message  is stopped on wait and not proceeding ahead.
    I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
    and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
    Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface Request_SI</Trace>
      <Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
      <Trace level="1" type="T">--start determination of receiver interface action</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface Request_SI</Trace>
      <Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    Regards

    Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

  • "To Be Delivered" status in XI integration server

    Hey Guys!
    I have a question, right now we are trying to load Items into SRM; however, the records are being given the “To Be Delivered” status in the XI Integration Server. The records do not reach SRM. We have tried refreshing the XI Cache, as well as restarting the J2EE engine, all to no avail. Would anyone of you guys know how to address this issue? Thanks in advance!!
    Best Regards,
    Glenn

    Hi,
    Status:  TO_BE_DELIVERED
    Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
    TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
    Solution:
    This is done via the Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
    /<PROTOCOL>
    Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
    1. Try logging into Sap GUI with two users:  XIAPPLUSER & XIAFUSER
       to see if they are blocked
    2. We can check the messages:
    AdapterFramework
    com.sap.aii.adapterframework.serviceuser.language
    com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
    com.sap.aii.adapterframework.serviceuser.pwd
    ApplicationSystem
    com.sap.aii.applicationsystem.serviceuser.language
    com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
    com.sap.aii.applicationsystem.serviceuser.pwd
    in the exchange profile to make sure the right passwords
    Regards
    Agasthuri Doss

Maybe you are looking for