During a deployment operation over an application, this application changes its status. Depending on the status some restrictions over the application usage exist due to limited availability of the application functions. These restrictions should be taken into account by the users when they try to perform operations over an application that is still in any deployment operation.
When an application is under any deployment operation, the lock on that application controls the access from other operations to it. The types of lock are explained in Deployment Operations .
An application can be in the following statuses:
The state of the application is changed depending on the currently performed operation.
Basic Operations
The figure below illustrates the changes that occur as a result of the following deployment operations:
Lifecycle sequence:
Update
The figure below illustrates the changes that occur as a result of the following deployment operations:
Lifecycle sequence:
Implicit Stop
The figure below illustrates the changes that occur when a strong referenced resource is not available or becomes unavailable.
Lifecycle sequence:
While the application is in status IMPLICIT STOPPPED, it behaves like the application is in status STOPPED. The difference between the STOPPED and IMPLICIT_STOPPED statuses is that AS Java automatically tries to start an application in status IMPLICIT_STOPPED when the required resource becomes available on the server.