The Group model is really just a layer on top of the Site model, providing a way for an off-site administrator to arrange for the desired update packages to be installed in the %miame%/atesetup directory of each site, without having to manually connect to each site. To accomplish this, the administrator must customize the local update configuration file (previously discussed) to point to a custom web update control file (maintained by the administrator) and install the customized local update configuration file at each affected site. In addition, a provision must be made for the ATEUPDATE.LIT program to get executed regularly, in order to check for updates and download them as needed.
Although the ATEUPDATE.LIT utility can be launched manually (mainly for testing purposes), it is normally launched automatically via your startup command file, so that whenever a new session is launched, the off-site web update control file is checked against the local ATE version and the locally installed packages, and if necessary, an updated package is downloaded into the %miame%/atesetup/ directory (after which the procedure described in the Site model will take care of recommending and initiating the update for each user that connects).
See the following section for further details on ATEUPDATE operation and switches.
