Page Comparison

This program allows to send alerts whenever MB servers are switched (it can be achieve by background job). On the selection screen of the report, user can enter list of e-mails that receive information about the incident.

...

Such e-mail contains data such as the system it is running on, the time of incident, and which one message broker port has been disabled or enabled. Example of e-mail:

...

Additional, the history of Message Broker changes are stored in the ‘failover history’ button. This ALV report display information about Logical Port, MB state, MB unavailability code, Message textThe /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.

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

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).