Manage editions

The manage editions page shows details of each edition of an application. With this page you can manage the life cycle of an edition. The related actions are: activation, validation, rollout, and deactivation.

To view this page, click Applications > Edition control center > application_name.

If you are a user with either a monitor or an operator role, you can only view the edition manager information. If you have the role of configurator or administrator, you have all the configuration privileges for the application edition manager.

Editions

Specifies the name of the edition. For example, 1.0, or Base edition, is used, if no edition is specified.

Description

Specifies a description of edition that you can provide.

Target

Specifies the deployment targets to which modules for the edition are mapped. The target can be a server or cluster on which this edition is installed.

State

Current state of edition.

Actions

Activate

Changes an edition state from inactive to active. Only active editions can be started.

Validate

Changes an edition state from inactive to validation. Entering validation mode creates a clone of the edition's current deployment targets and prepares the edition to be started on the cloned deployment targets for validation. When an edition that is in validation mode is rolled out, the rollout acts on the original deployment targets and the cloned deployment targets are deleted.

Rollout

Changes an edition state from inactive to active. You can use either atomic or group rollout.

Group rollout divides the target cluster into groups for rollout. Group rollout is most effective when your cluster is large. You can specify the group size with a sub-option. The group size gives the number of nodes to process at a time. The default is 1.
Atomic rollout replaces half the servers in the deployment target at a time. The edition that is replaced is put into the inactive state. The replacement is performed cooperatively with the on demand router to ensure that no application requests are lost during the edition transition. This rollout strategy ensures that no loss of service occurs for single server deployment targets.

Deactivate

Changes an edition state from active to inactive. Inactive editions cannot be started.

Cancel Validation

Cancels the validation mode for an edition. If you find a problem when you are testing an edition validation, you can use this function to set the application to inactive state, perform the validation cleanup process, and delete the validation target. The original deployment target is restored.

File name: app_edition_details.html