Deploying pending changes

Some configuration and administration changes require an extra deployment step.

When we use the graphical user interface on the appliance to specify changes, some configuration and administration tasks take effect immediately. Other tasks require a deployment step to take effect. For these tasks, the appliance gives you a choice of deploying immediately or deploying later. When we must make multiple changes, we can wait until all changes are complete, and then deploy all of them at one time.

When a deployment step is required, the user interface presents a message that says there is an undeployed change. The number of pending changes is displayed in the message, and increments for each change you make. If any of the changes require the runtime server to be restarted, the restart occurs automatically when we select Deploy. The runtime server will then be unavailable for a period of time until the restart completes.

Steps

1. When you finish making configuration changes, select Click here to review the changes or apply them to the system.

   The Deploy Pending Changes window is displayed.

2. Select one of the following options:

   Option	Description
   Cancel	Do not deploy the changes now. Retain the undeployed configuration changes. The appliance user interface returns to the previous panel.
   Roll Back	Abandon configuration changes. A message is displayed, stating the pending changes were reverted. The appliance user interface returns to the previous panel.
   Deploy	Deploy all configuration changes. When we select Deploy, a system message is displayed, stating the changes were deployed. If any of the changes require the runtime server to be restarted, the restart occurs automatically when we select Deploy. The runtime server will then be unavailable for a period of time until the restart completes.

Parent topic: Advanced Access Control administration