Upgrade APS application instance
An APS application upgrade may be initiated by Provider (for all instances of APS application) or by a customer (for a particular application instance).
In both case POA schedules the following tasks to upgrade APS application instance installed in customer subscription:
|Task name||Task purpose|
The task marks application service instance as 'Upgrading' in POA database.
This task completes almost immediately after customer finished APS application upgrade wizard in POA CP since it just updates POA database.
|Configuring URL mapping for instances of APS applications||Configures URL mappings for APS application access in the .htaccess file in webspace.|
|Dump config image for domain service||Updates virtual host configuration of a customer website where application is installed on web server.|
|performing hosting operations||Performs pre-upgrade actions on the APS application instance - adjusts permissions of files/folders in webspace.|
|Upgrading files of site||Physically updates files of APS application in customer's webspace.|
|performing hosting operations||Performs post-upgrade actions on the upgraded APS application instance - adjusts permissions of files/folders in webspace.|
|Dumping content of scripts directory for instance of APS site application||
The task performs the following actions:
1. Get content of application provisioning scripts from the scripts/ folder in the APS package (the scripts are actually stored in POA database)
2. Create .tar file with all scripts put in it
3. Upload created .tar file to the server which will act as Provisioning Gateway Host.
4. Unpack scripts from the .tar file
5. Remove .tar file.
|executing configuration script||Task checks all parameters passed to it and executes appropriate script (configurein most cases) with appropriate environment variables (taken from passed parameters) and command'upgrade'.|
|performing hosting operations||Performs post-installation actions on the installed APS application instance - adjusts permissions of files/folders on webspace.|
|Finalizing upgrade||The task marks corresponding object (application instance, service user, application service) in POA database as Installed or Ready.|
The task 'Dumping content of scripts directory for instance of APS site application' is being executed along with tasks 'Initiating configuring', 'Executing configuration script' and 'Finalizing configuring' every time application instance has to be reconfigured/upgraded which means that POA re-uploads scripts on every application reconfiguration which in turn means that if to fix problem you make manual changes in script file on provisioning gateway server, your changes will be overwritten when customer does similar change from Control Panel.
The correct way to solve the problem with APS task failing due to wrong provisioning script is to repack package with correct scripts, upload new version of package and upgrade existing applications to the new version.
See the main KB article #115664 APS: General information, Best Practices and Troubleshooting for more information.