Skip to Content

Solman BPM monitors - auto reactivate after outage?

We've been using Busingess Process Monitoring for a while and actually have some business teams relying on the reports (yay!  small victories with Solman!!).  Unfortunately it's not as robust as we need it to be.  With system restarts, the BP monitors often stay off, as if they've been deactivated and then we need to go back and reactivate, usually when a business client notices they haven't received any alerts in a while.  Not a good scenario.

Is this something that is unique to our installation? (wouldn't be the first time, we seem to be good at "hmm you'r the only one doing that" responses from SAP).

Case in point - few weeks back something mysteriously took out 1 application server from several of our SAP systems.  Solman, ECC, two other systems each lost one app server.  We run multiple app servers, so it appeared that the systems were functioning , but Solman lost all technical monitors and the agents would NOT report any system availability stats, and the bpm monitors stopped as well.

We restarted all the systems and TechMonitoring came back online, but the BP Monitors did not restart.  And we've had that happen in the past as well. You would think/hope that a system restart would reactivate any running monitors, but apparently this isn't always the case. 

Anyone noticed this behaviour?  Or am I in a class of 1, again?  😊  Almost seems like I need a way to automate a global reactivation of all BPM processes once a month or so.

Solman 7.1, sp12, Solaris

Thanks.
Bernie

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 24, 2015 at 08:59 AM

    Hi Bernie,

    at the moment we are just running a small POC for BPmon with only one Monitoring Object for a very simple Business Process. It used to work fine but the MO just deactivated itself one day and since then we can't activate t anymore. I have engaged SAP AGS for that via an OSS incident but... I remember that when it used to work it would be deactivated after a system restart, just the way you describe it

    Indeed it could be good to have SAP thinking about a solution or create an automatic process to restart them after a system restart!

    Thanks,

    Nicolas

    Add comment
    10|10000 characters needed characters exceeded

    • Interesting.  Hopefully they have suggestions. I have a feeling there is something weak in the EFWK  - a monitoring solution should be robust enough to be able to recover from "events", otherwise the trust level drops quickly.

      Thanks.
      Bernie