Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

(S4)PACG 200 SP05

The /PACG/ECM_HEARTBEAT is a report (there is no t-code defined) that lies at the foundation of the entire solution. Its purpose is to check the status of a running (primary) message broker and in case of failure start the secondary one. So in other words - it controls and is responsible for the failover mechanism.

This report must be scheduled as a background job and it is recommended to run it every single minute.

The /PACG/ECM_HEARTBEAT report can also:

  • show the history of failover in the form of a simple ALV grid - this can be achieved with the ‘Failover history’ button in the report’s toolbar

  • delete previously defined jobs if the ‘Delete old jobs’ checkbox is ticked

And analogically to other Connector’s reports, the /PACG/ECM_HEARTBEAT can:

  • save logs if the ‘Save Log’ checkbox is ticked - these logs can be later viewed using SLG1

  • display logs if the ‘Display Log’ checkbox is ticked - this checkbox should be unticked when the report is executed as a background job

(S4)PACG 200 SP10

In case of a failure of a running message broker and switching to a redundant instance, the /PACG/ECM_HEARTBEAT can also send an email notification. To enable notifications' sending it is sufficient to provide recipient(s) email(s) in the reports selection screen. Such email contains the following information:

  • ID of a source system

  • Time of occurrence

  • ID of disabled and enabled logical ports (to which physical instances of the message brokers belong).

  • No labels