All applications can be in the running or stopped runtime states. Transition to and from these states occurs through start and stop operations. All applications can also be in the non-existent or existent configuration states. Transition to and from these states occurs through installing or uninstalling an application. WebSphere Extended Deployment application editions have additional configured states beyond those of WebSphere Application Server applications. These additional configuration states can be seen as sub-states of the existing state.
This topic describes the application edition manager edition states, and how they transition.
WebSphere Extended Deployment application states are depicted in the following state transition diagram.
From state | To state | Transition action | Notes |
---|---|---|---|
Non-existent | Inactive | Install application edition | (none) |
Inactive | Validation | Validate++ | Validation deployment target is created. |
Inactive | Active | Activate++ or rollout++ | Rollout deactivates the old edition. |
Validation | Active | Rollout++ | Validation deployment target is deleted. |
Active | Inactive | Deactivate++ | (none) |
Active | Non-existent | Uninstall application edition | (none) |
Validation | Non-existent | Uninstall application edition | Validation deployment target is deleted. |
Inactive | Non-existent | Uninstall application edition | (none) |
++ Validate, activate, rollout, and deactivate are new application edition operations introduced by the application edition manager.