Redeploy objects

Updating assets that are already deployed requires a redeployment of the asset. Redeploying an asset or a group of hierarchical assets can be done almost seamlessly, with very little downtime. When you redeploy an asset, a maximum of two scan cycles are needed between the time the existing asset configuration is undeployed and the asset with new configuration information is deployed in its place (typically, less than one second). This redeployment workflow provides two important benefits:

• Minimized downtime. While an asset is down, it does not provide status updates and does not respond to scripts or commands.

• Reduced points of failure. The existing configuration remains in effect until the new configuration is available.

This minimal downtime needed to redeploy assets ensures that uptime is maximized and the impact on operations is minimized. To ensure against a deployment failure due to communications or other error, the existing asset configuration remains deployed and onscan until the new configuration has been successfully deployed. Therefore, if a redeploy attempt fails for any reason, operations are not affected, as the existing configuration remains available within the production environment. The asset is not stopped or taken offscan until the new configuration replaces it. Since less than two scan cycles are needed for a redeploy operation, and this occurs only at the final stage of pushing out the new configuration, there is little risk of adverse effect on operations.

• Redeploying assets follows the same workflow as deploying assets. See Deployment overview for additional information. Redeployment occurs when you select and deploy the asset.

When assets with retentive attributes are redeployed, the Application Engine for the assets restores the retentive attributes to the values previously set at run time, if the Preserve Runtime Changes option is selected. See Deploy objects and Retentive attribute properties and behavior for additional information.

You may have an object with a Pending Update deployment state. The Pending Update state means the object changed since it last deployment. When you deploy those changes, the new object is marked as the last deployed version in the Galaxy.

To redeploy

1. On the Home ribbon, in the Deploy area, select Deploy.

2. Follow the procedure for Deploy objects.