Edition activation distinguishes between two states in
which an application edition might exist. When an application edition
is first installed, the application edition is in the inactive state.
You can start the application edition only when it is in the active
state. The transition from inactive to active is known as activation.
Three methods exist to activate an application edition: activating,
performing a rollout to a new application edition, or validating the
application edition.
Before you begin
- You must have an application installed and in the inactive state.
- To activate an application edition, you must have a configurator
or administrator administrative role.
Note: The first installed edition of an application is automatically
activated.
Procedure
- In the administrative console, select .
- Select the application edition that you want to activate.
- Complete one of the following actions.
- Click Activate.
Activating
marks an application edition as available to be started. After you
activate an application edition, you must update the routing rules,
and click
Apply and
Save regardless
of what item is displayed in the list. For more information about
activating editions, read about Creating routing policies for application
editions.
Avoid trouble: After you update the routing rules,
you must click Apply and Save even
if only one edition of the application is displayed in the menu list.
- Click Roll out.
Performing
a rollout to an application edition activates one edition in place
of another. The new application edition automatically starts because
it replaces a running application edition. For more information, read
about performing a rollout on an edition
- Click Validate.
Validation
activates an application edition on a clone of its original deployment
target. For more information, read about validating an edition.
Results
The application edition is activated.
What to do next
If you used the activate or validate options, you can
start your edition application.