AppEngine object Redundancy tab

Enable redundancy

Redundancy.Enabled

If selected, a backup AppEngine (redundant partner) will be created automatically for this AppEngine.

None

Forced failover timeout

Redundancy.ForcedFailoverTimeout

The maximum allowed time, in milliseconds, for a standby engine to become active after a forced failover has been initiated using the ForceFailoverCmd attribute. If the standby engine does not become active within this time period, this engine will revert back to the active engine.

Supervisory, User

Maximum checkpoint deltas buffered

Redundancy.CheckpointDeltasBufferedMax

The maximum number of checkpoint deltas that can be buffered before a full checkpoint synchronization is performed.

Supervisory, User

Maximum alarm state changes buffered

Redundancy.AlarmStateChangesBufferedMax

The maximum number of alarm state changes that can be buffered before a full snapshot of the alarm state changes for the engine is performed.

Supervisory, User

Standby engine heartbeat period

Redundancy.StandbyHeartbeatPeriod

The time interval, in milliseconds, at which heartbeats are sent by the failover service on the standby engine to the failover service on the active engine via RMC.

Supervisory, User

Active engine heartbeat period

Redundancy.ActiveHeartbeatPeriod

The time interval, in milliseconds, at which heartbeats are sent by the failover service on the active engine to the failover service on the standby engine via RMC.

Supervisory, User

Maximum consecutive heartbeats missed from Active engine

Redundancy.ActiveHeartbeatsMissedConsecMax

The maximum number of heartbeats from the active engine that can be missed before a bad connection is assumed by the standby engine via RMC. For example, if the maximum consecutive heartbeats missed from active engine is configured as 5, and the active engine heartbeat period is configured as 1000 milliseconds, then the standby engine will assume a bad connection from the active engine if no heartbeats are received within five seconds.

Supervisory, User

Maximum consecutive heartbeats missed from Standby engine

Redundancy.StandbyHeartbeatsMissedConsecMax

The maximum number of heartbeats from the standby engine that can be missed before a bad connection is assumed by the active engine. If a bad connection is detected, the active engine will switch to the "Active - Standby Not Available" state via RMC. For example, if the maximum consecutive heartbeats missed from the standby engine configured as 5, and the standby engine heartbeat period is configured as 1000 milliseconds, then the active engine assumes a bad connection from the standby engine if no heartbeats are received within five seconds.

Supervisory, User

Maximum time to maintain good quality after failure

Redundancy.StandbyActivateTimeout

Themaximum time period, in milliseconds, after the active engine fails before subscribed references to it are set to "uncertain."

Supervisory, User

Maximum time to discover partner

Redundancy.PartnerConnectTimeout

The maximum time period, in milliseconds, allowed for the connection to the failover partner to be established before the failover partner state is set to "unknown."

Supervisory, User

Force failover command

Redundancy.ForceFailoverCmd

Allows you to set the security settings for manually forcing a failover.

Supervisory, User

Restart engine process when transitioning from Active to Standby

Redundancy.RestartOnTransitionToStandby

If true, the engine process is restarted when the transition from active to standby is made. The default is true.

None

Run warm

Redundancy.RunWarm

If true, the standby engine runs in offscan mode after being started and initialized at the time the galaxy is deployed. When the transition to standby to active is made, the engine goes to onscan.

If false, the standby engine is not started or initialized until a failover condition occurs. The default is false.

Supervisory, User