Message Broker Failover Mechanism - manual control

(S4)PACG 200 SP 05 Message broker 3.4

Beside automatic control of message brokers running in failover mode it is also possible to do it manually. For that a new transaction was added /PACG/ECM_FAILOVER. It can be run via FSM Cockpit. In order to use this transaction user must have a valid authorization (authorization object /PACG/E001)

Open

/PACG/ECM_FAILOVER

As only two message broker can run in parallel in failover mode this report shows current state of each of them and more importantly it lets making a switch. For the sake of simplicity these message brokers are called primary and secondary just in order to distinguish them but and beside that, they must be identical. Columns in the display have following meaning:

• Exception - shows the current status of a cluster

• Primary logical port - name of logical port handling message broker called primary

• Status of primary service - it can be either up or down

• Status of primary service - it can take one of the following values:

  • Started

  • Stopped

  • Starting

  • Stopping

• Activate primary - allows switching to primary message broker when secondary is running

• Secondary logical port - analogically to the primary one

• Status of secondary service - it can be either up or down

• Status of secondary service - values same like listed above

• Activate secondary - allows switching to secondary message broker when primary is running