Application Statuses 

Use

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.

Integration

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.

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 application starts only after the strong referenced resources become available to start the application.

Activities

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:

●      deploy

●      start

●      stop

●      remove

Lifecycle sequence:

●      At the beginning, the applications are not deployed.

●      When you start the deploy operation, the application state is changed to STOPPED.

●      When you start the start operation, the application state is changed to STARTING.

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

●      When you stop an application, the status is changed from STARTED to STOPPING.

●      Upon successful stop, the status of the application is changed 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, a check is made if it has to be stopped.

●      If the application has to be stopped, it is stopped.

●      If the application does not need to be stopped, the UPGRADING operation starts.

●      If the UPGRADING operation finishes successfully, a check is made whether the application has to be started.

●      If the application has to be started, its status is changed to STARTING and then to STARTED.

●      If the application does not need to be started, the application is returned 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 status of the application changes to STOPPING and then to IMPLICIT_STOPPED.

●      If the application was STOPPED and you try to start it, the status of the application changes to STARTING. But if a strong referenced resource is not active on the server, the status of the application changes 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 AS Java automatically tries to start an application in status IMPLICIT_STOPPED when the required resource becomes available on the server.