Application Statuses 

Use

During a deployment operation over an application, that 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.

Integration

When an application is under any deployment operation, the Deploy service sets a lock on that application to control the access from other operations to it. The types of lock are explained in Deployment Operations.

Features

An application can be in the following statuses:

·        STARTING – only the deployment operation has an access to the application.

·        STARTED – the application is available to all other applications.

·        UPGRADING – during this state, the application is being updated.

·        STOPPING – only the deployment operation has an access to the application.

·        STOPPED – the application is not available to any operations. You have to start it before you can use it.

·        IMPLICIT_STOPPED – the Deploy service waits until the strong referenced resources become available to start the application.

Activities

The Deploy service changes the state of application depending on the currently performed operation.

Basic Operations

The figure below illustrates the changes that occur as a result of the following deployment operations:

·        deploy

·        start

·        stop

·        remove

Lifecycle sequence:

·        At the beginning, the applications are not deployed.

·        When you start the deploy operation, the Deploy service changes the application state to STOPPED.

·        When you start the start operation, the Deploy service changes the application state to STARTING.

·        If all required references are available, the status can be changed from STARTING to STARTED.

·        When you stop an applicaiton, the Deploy service changes the status from STARTED to STOPPING.

·        Upon successful stop, the status of the application Deploy service changes the status to STOPPED.

·        Now you can remove the application from the server or start it again when necessary.

Update

The figure below illustrates the changes that occur as a result of the following deployment operations:

·        update

·        single file update

Lifecycle sequence:

·        If the application is STARTED, then the Deploy service checks if it has to be stopped.

·        If the application has to be stopped, the Deploy service stops it.

·        If the application does not need to be stopped, the Deploy service directly starts the UPGRADING operation.

·        If the UPGRADING operation finishes successfully, the Deploy service checks whether the application has to be started.

·        If the application has to be started, the Deploy service changes its status to STARTING and then to STARTED.

·        If the application does not need to be started, the Deploy service returns the application to the initial state before the upgrade operation has started.

Implicit Stop

The figure below illustrates the changes that occur when a strong referenced resource is not available or becomes unavailable.

Lifecycle sequence:

·        If the application was STARTED, and a strong referenced resource becomes inactive on the server, the Deploy service changes the status of the application to STOPPING and then to IMPLICIT_STOPPED.

·        If the application was STOPPED and you try to start it, the Deploy service changes the status of the application to STARTING. But if a strong referenced resource is not active on the server, the Deploy service changes the status of the application to IMPLICIT_STOPPED.

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 the Deploy service will automatically try to start an application in status IMPLICIT_STOPPED when the required resource becomes available on the server.