Delete redundant AppEngines

You can disable redundancy in an AppEngine after Application Server creates the Backup object. If you disable redundancy and check in the Primary AppEngine, the Backup is deleted from the Galaxy. The exception is when the Backup is already deployed. In that case the newly configured Primary object cannot be checked in.

To delete a Backup AppEngine from the Galaxy, you must undeploy it first.

There is no redundancy-related configuration required on ApplicationObjects hosted by an AppEngine configured for redundancy. When a system failure occurs, the ApplicationObjects and their attribute values are duplicated on the Standby AppEngine, which becomes the Active AppEngine. For more about failover functionality, see Redundant AppEngines during deployment.

If the Platform hosting the redundant AppEngine is shutdown in OCMC, the AppEngine cannot be flagged as "On failure mark as undeployed" when you undeploy the AppEngine. You see an engine communication error in the Deploy dialog box.