This phase is not supported by AH that don't support the Application Container modality. One
important parameter here is the so-called Differencing Granularity Level . This is the capability
of the established deployment circuit to save bandwidth by skipping the distribution of already
installed resources. The finer the granularity of the differencing mechanism, the higher the
potential bandwidth savings.
An example of a differencing mechanism is the JARDiff format used by the JNLP pro-
tocol. When given two JAR files, one already downloaded and installed and the other
one going to be downloaded, requests only the difference of the two files, with a
granularity level of the single Java class. See the Part III, “JNLP,” or Appendix B, “The
JNLP Specification,” for more details.
On-The-Run Application Management During AH Application
The On-The-Run Application Management During AH Application Support Phase describes
the features of some advanced AHs during the application execution.
This stage is composed of three possible steps:
1. Debugging Whenever an exception reaches the AH, it can perform some form of
remote debugging with the Deployment Server (or other servers). It works with versions
of the JRE that support remote debugging.
2. On-The-Run Updating While the application is running, some parts of it can be
replaced during this phase, possibly without causing the current execution to abort.
3. Other On-The-Run Management Several of these kinds of services are possible. For
example, a mechanism of remote logging or updating of some business data could be
performed in this phase, taking advantage of the deployment infrastructure.