This model typically dispenses with both the web update control file and the local configuration file. Instead, you (the site administrator) manually places the desired update package into the special %MIAME%/atesetup directory on the server. The name of the package indicates both its version and type, so there is no additional need for configuration files to control either of those options. (There are, however, a couple of additional but optional files to customize the behavior, described below.)

When each workstation connects to the server, A-Shell on the server scans the atesetup directory for the presence of any file matching either of the package naming schemes:

ate-#.#.#.#{-suffix}.exe

ate-#.#.#.#{-suffix}-web.exe

ate-#.#.#.#{-suffix}-web.txt

 

(The first two of these package types have already been described. The last type is not really a package but just a text file containing the URL of the desired package. This alternative is useful in the case where file transfer between the server and the workstation doesn't work well.)

If any package file is found whose version is later than the version currently running on the workstation, the user is prompted to update. The actual text of the message may be customized by editing the file %miame%/ate.txt; otherwise a generic message is used.

If the user responds affirmatively to the message requesting the update, A-Shell on the server sends the update package to the workstation and forces it to launch. (In the case of the .txt pseudo-package, it simply sends a command to the workstation to download the specified URL, which eliminates the file transfer from the server, but leaves it to the user to deal with the prompts from the browser needed to save and execute the file.)

If the file %miame%/atesetup/options.txt exists, the contents of the first line will be appended to the command line used to launch the update package (allowing you to specify additional command line switches). Currently the only available option is /SILENT, which disables all of the extra user interface elements of the update package.

Note that if newer monolithic and incremental (web-based) update packages are available that are newer than the current version on the workstation, the -web package will be used by preference, unless the server can detect that the workstation does not have Internet access. (This is only possible for workstations already running ATE 5.1)