How To Perform Phased Deployment of Application Center 2000 by Using Best Practices (318199)

SUMMARY

When you successfully deploy Application Center 2000, and the product is in production on server clusters, eventually you must update the content. Content availability on the Web is a priority, and content updates on production servers should occur with minimal loss of server capacity.

When newly-deployed content contains problems or errors, you need a method to roll back the new content and revert to the last known good version without any loss of consistency or server uptime. The following white paper addresses issues directly related to the phased deployment and rollback of content by using Application Center.

Best Practices for Phased Deployment Using Application Center 2000

MORE INFORMATION

Errata:

Applies to the November 2001 publication

When you clear the Include this member in synchronizations check box, you do not prevent the COM+ routing list from replicating to cluster members.
- Replace all mentions of clearing the Include this member in synchronizations check box with "shut down and disable the Application Center Synchronization service."
- Replace all mention of selecting the Include this member in synchronizations check box (or returning all servers to the synchronizations loop) with "start up and enable the Application Center Synchronization service."
WARNING: Disabling the Application Center Synchronization service may cause other errors and warnings to occur.

Applies to the following sections:
- Taking Segment A Offline - steps 3 and 5
- Returning All Servers to the Synchronization Loop