Skip to Content

SOAP ICO - Queue Monitoring

Hello!

We have a PI7.4 dual stack and configured a SOAP Receiver [Async] scenario. For some reason the messages are failing in receiver side which is evident from communication channel log, with the ICO configured how can we monitor the queues [smq1 and smq2] ? it may be silly to ask but would be good to have this clarified please?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Oct 13, 2017 at 12:12 PM

    Hi Prabhu!

    SMQ1 and SMQ2 transactions are intended to monitor AS ABAP Integration Engine queues. When you use ICo, your message processing takes place on AS Java Adapter Engine side. It uses its own Sender and Receiver queues.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 31, 2017 at 03:05 PM

    Hello Prabhu,

    Evgeniy is absolutely right, as soon as ICO is being processed in Adapter Engine (Java stack) you can monitor the corresponding queues in NWA. There are 4 queues overall dedicated for every adapter

    • Send (Asynchronous outbound),
    • Rcv (Asynchronous Inbound),
    • Call (Synchronous outbound),
    • Rqst (Synchronous inbound).

    Please read this great blog: https://blogs.sap.com/2011/01/26/tuning-the-pi-messaging-system-queues for better understanding.

    To access the queue monitoring tool in NWA, please follow the path: NWA -> SOA (Tab) -> Monitoring (Sub-tab) -> Adapter Engine Status -> Additional data (Tab) -> Queues (Default sub-tab).

    However, in order to capture the actual error, I'd suggest you to check log entries in default trace (you can manually open the trace file as per SAP Note 1596214 or access the Log Viewer tool in NWA. Or, alternatively, you can monitor the failing channel.

    Yet another possible way - to check the failed messages in Message Monitor in NWA.

    Best regards,
    Vadym

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 31, 2017 at 06:39 PM

    Have you tried : http(s)://host:port/MessagingSystem .

    Add comment
    10|10000 characters needed characters exceeded