Skip to Content
Technical Articles

Enhanced: Alerting for stuck messages on the Adapter Engine

Introduction

With the blog post Alerting for stuck messages on the Adapter Engine a feature to alert on messages that appear to be no longer processed has been provided. This functionality has later been included in the standard coding.

In certain situations this alert mechanism may not be sufficient or more specifically procude false alarms as it does not allow to filter on message status.

Download & Deployment:

Use the following link to download the enhanced version:

Download EAR

The ear-File then needs to be deployed to your system. Make sure that these changes are tested on a non-production system before using it in your production environment.

After deployment  you can find the new application via NetWeaver Administrator -> Operations -> Systems -> Start&Stop -> Java Applications. The application list should have a new entry with name “pi.alertstuckmsgv2” and vendor “cust.sap.com”. Please verify that it is started without errors.

 

Scheduling the Job

Scheduling and configuring the job can be done via NetWeaver Administrator -> Operations -> Jobs -> Java Scheduler. Here you can find the new job template in tab “Job Definitions”. It should list a new job type with name “AlertStuckMessagesJobv2” and application “cust.sap.com/pi.alertstuckmsgv2”.

 

For details about scheduling refer to the original blog post:

https://blogs.sap.com/2016/04/13/alerting-for-stuck-messages/

The difference in scheduling which supports the new enhancement is the parameter “StuckMessageStatusList” which can be populated with comma-separated status values. The mentioned status values are those which are taken into account for alerting. Messages having another status will not be alerted.

The default value (list) is: TBDL,DLNG,HOLD

All other parameters from the original version and the provided information in the blog post is still valid.

 

Summary

This blog post and its provided alerting application allows you to filter for “stuck messages” to be alerted on by message processing status. It heavily builds on already available functionality published in other / earlier blog posts and available in SAP NetWeaver Process Orchestration standard functionality.

 

6 Comments
You must be Logged on to comment or reply to a post.
  • Hi Frederic,

    Thanks for the detailed blog.

    I have followed the blog and set up configurations in my PI Dev system.

    I made messages to get stuck to test it. But the alerts are not triggered.

    Can you please let me know if I am missing something?

    Regards,

    Pavan

    /
  • Hi Frederic,

    I was just looking into this for a customer of mine.
    What is strange is that in the original AlertStuckMessagesJob (PO 7.5) I only see the parameter “Additional” .

    I would have at least expected some of the other parameters.

    Also where does this EAR come from? Is it mentioned in a SAP note?
    I may not be able to convince my customer to install an EAR which I picked up from Google drive if I cannot show them that it is a regular software deployment.

     

    Kind regards,

    Tom