Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
Application edition manager states
All applications can be in the running or stopped runtime states, and in the non-existent or existent configuration states. WebSphere® Virtual Enterprise application editions have additional configured states beyond those of WebSphere Application Server applications. Consider these additional configuration states as sub-states of the existing state.
Application edition manager editions transition into multiple states. The transition of an application between the running and stopped runtime states occurs through start and stop operations. The transition of an application between the non-existent or existent configuration states occurs when you install or uninstall the application. As the application edition transitions from one state to another, various actions occur, such as installing, validating, activating, performing a rollout, deactivating, or uninstalling. The following table features a list of the transitions and the resulting actions:
Table 1. State transitions From state To state Transition action Notes Non-existent Inactive Install application edition (none) Inactive Validation Validate1 Validation deployment target is created. Inactive Active Activate or perform a rollout1 Performing a rollout deactivates the previous edition. Validation Active Perform a rollout1 Validation deployment target is deleted. Active Inactive Deactivate1 (none) Active Non-existent Uninstall application edition (none) Validation
Inactive
Cancel validation
Validation deployment target is deleted.
Inactive Non-existent Uninstall application edition (none) 1Validate, activate, perform a rollout, and deactivate are new application edition operations introduced by the application edition manager.
Related concepts
Application edition manager operational environment Application edition manager