Redundant AppEngines during deployment

During initial deployment of a redundant pair of AppEngines, files are deployed in the following order:

• Code modules and other files for the Primary AppEngine are deployed

• Those files for its assigned ApplicationObjects

• All of these files are deployed to the Standby AppEngine by the Active engine’s WinPlatform using the redundancy message channel (RMC)

  Note: If some or all of these files already exist on the Standby AppEngine’s WinPlatform, perhaps, assigned to another AppEngine on that platform, only the delta files are deployed to the Standby AppEngine.

In the configuration environment, objects are always assigned to the Primary AppEngine.

During run time, objects are always deployed to the Active AppEngine whether or not it was initially configured as the Primary object.

All files are deployed by the Active AppEngine’s WinPlatform to the Backup AppEngine using the RMC.