Added October 2016
In the Summer and Fall of 2016, a customer requested a process whereby end-users could be directed to a single webpage which would either run ATE—if it were already installed on the user's PC—or download, install and then run—if ATE were not already installed on the user's PC. This operation presented some challenges, but we eventually came up with a means of doing approximately what the customer wanted. In order to accomplish the project, which was tentatively named "Web Connect," the following changes were made to ATE:
| • | The MIAME environment variable is now always set to match the location of the miame.ini file. This is almost always the case anyway, except that when launched from a URL link, visibility restrictions on the environment between Windows and the browser were resulting in it reverting to C:\VM\MIAME. |
| • | The Cache and PermCache directories now default to %MIAME%\Cache and %MIAME%\PermCache, respectively, if not set. This was a potential issue when building a minimal configuration on the fly from the URL. |
| • | When building the ATE configuration on the fly, you can define pseudo configuration values LoginSBX=<xcallname> and WebRepo=<url dir> to cause ATE to check the web repository for the custom login dialog. |
History
2016 October, A-Shell version 6.3.1530: Build ATE run / download-and-run process for customer, add components to ATE.
