This scenario describes how to dispose of unwanted application
editions.
After multiple successive editions of an application are deployed and
rolled out, which is not unusual in the life span of many production applications,
you might have a number of editions stored in your repository that are no
longer needed. The following steps show you how to clean up your repository
and remove unwanted editions.
An edition can be in any one of three states. Therefore, the method for
deleting or uninstalling an edition varies slightly based on its current state.
The three states are:
- Inactive: This edition is neither assigned for use in any deployment
target, nor the default. An inactive edition can be uninstalled at any time.
- Active: This edition is currently assigned for use in one or more
deployment targets. One or more servers are assigned to use this edition.
An active edition cannot be uninstalled. It must first be made inactive. The
default edition is always marked active because it is used for any new server
that is added to a server cluster. To deactivate an edition, you can either
replace it by following the edition rollout procedure, described in the full
and graduated rollout scenarios, or you can use the Deactivate edition option
to stage the deactivation. By staging the deactivation, the edition is deleted
from the master repository but remains in use in any server that is running
that edition. The next restart of the server activates the default edition
instead of the edition that you just deactivated.
- Default: This is the edition marked as default. The default edition
can never be uninstalled. To uninstall the edition currently marked as the
default, another edition must be marked as the new default edition. If the
default edition is also truly active, that is, assigned for use in some deployment
target , you must deactivate it first, as described previously active editions.