Web Application Flow

A web application selected for use in Plesk passes through several transformation stages during its lifetime in Plesk. These stages are as follows.

Stage 1. The first stage lasts from the moment a web application is selected for Application Vault till it has got to AV Repository. This stage includes creating an installation package (1), wrapping it into a distribution package (2), and uploading this distribution to AV Repository (3).

At this stage, a web application turns into an installation package which serves as a minimal indivisible unit Application Vault can operate. To look at the detailed description of the installation package structure, open the Installation Package section of Reference. Later on, the installation package transforms into a distribution package. For instance, this can be done using the RPM utility. But this 'wrapper' package is only necessary to push the installation package into Application Vault. Once the distribution package is got to AV Repository, it is unwrapped, and the repository gets the installation package for storage.

Stage 2. The second stage refers to the time the web application is stored in AV Repository in the form of an installation package.

This stage comes to end when the installation package is deleted from AV Repository (5). Until this has happened, the installation package can experience as many installations to domains (6) as necessary. A web application can be installed on a domain on a commercial basis or free of charge. To switch between these states, one can apply the 'change status' operation to the installation package (4). Installing a web application on a domain does not affect the installation package as transferred to the selected domain is just a copy, not the package itself. Once a web application is installed on a domain, it begins to live its own life, and here the next stage begins.

Stage 3. This stage of the web application's life goes on the domain the application is deployed on. Such an application presents a copy of the installation package stored in AV Repository. Thus, all operations performed against this copy do not affect the original. E.g. one can install a certain application on the same domain as many times as wanted, and every time the new installation will be entirely identical to the previous one, provided the source installation package remains unchanged. During its lifetime on the domain, an installation can experience an unlimited number of reconfigurations (7). The application 'dies' at the moment it is deleted from the domain (8).