+

Search Tips   |   Advanced Search

Intelligent Management: application edition manager custom properties

By configuring custom properties for application edition manager, we can change the settings for our validation cluster. For example, we can set the operating mode of the validation cluster or create a custom property to keep the validation cluster after the rollout completes.


appedition.rollout.softreset.fulldrainageinterval

Force a soft reset to wait the entire drainage interval. Starting in v7.0.0.1, the application edition quiesce manager might not wait the full length of the drainage interval if all requests are quiesced before the interval times out. Performance Monitoring Infrastructure (PMI) statistics are available for the quiesce manager to determine if all active requests on a server have been quiesced.

Value Description
Scope Deployment manager
Valid values No value: Deactivated. The quiesce manager might not wait the full length of the drainage interval.

true: Enabled. The quiesce manager is forced to wait the entire drainage interval.


deactivate.checkRoutingRules

Enable if we do not want an application edition deactivation to occur when routing policy work classes are still routing workload to the application edition. If we do not set the property, the deactivation still occurs, even if routing policy work class actions are found that reference the edition.

Value Description
Scope Cell
Valid values No value: Deactivated, application editions can be deactivated even if routing policy work classes reference the edition.

true: Enabled. If routing policy work classes reference an edition being used deactivated, the deactivation does not occur until the actions are removed or changed.


saveClonedCluster

Maintain the validation cluster after we perform rollout to a new edition. If we do not set this custom property, the validation cluster is deleted after the rollout or after the validation is canceled. The saveClonedCluster custom property applies only to dynamic clusters.

Set this custom property on the validation cluster. To save the validation cluster, set the value to true.

Value Description
Scope Dynamic cluster
Valid values No value: Deactivated. The validation cluster is deleted after a rollout to a new edition.

true: Enabled. The validation cluster is saved when the rollout to a new edition occurs.


uninstall.checkRoutingRules

Enable if we do not want the uninstallation of an application edition to occur when routing policy work classes are still routing workload to the application edition. If we do not set the property, the uninstallation still occurs, even if routing policy work class actions are found that reference the edition.

Value Description
Scope Cell
Valid values No value: Deactivated. Application editions can be uninstalled even if routing policy work classes reference the edition.

true: Enabled. If routing policy work classes reference an edition being used uninstalled, the uninstallation does not occur until the actions are removed or changed.


VALIDATION_OPERATIONALMODE

To set the operational mode of the cloned validation cluster to a different mode from the production cluster, create the VALIDATION_OPERATIONALMODE custom property.

We can set this custom property on the production cluster before starting the validation process.

Value Description
Scope Dynamic cluster
Valid values automatic, manual, or supervised

If the value is unspecified or not valid, the validation cluster operational mode is set to the same operational mode as the production cluster. If we specify any other value or we do not specify a value, then the validation dynamic cluster is set to manual mode.


Related:

  • Application edition manager concepts
  • Validate an edition
  • Perform a rollout on an edition
  • Intelligent Management: application edition manager states