Site Deployment Manager

Site Deployment Manager

Site Deployment Manager is a conceptually distinct tool that is accessed through the Site Builder application. Only Content Management Server administrators are permitted to perform the export and import operations that constitute the Site Deployment Manager.

On computers serving as the deployment source (the development or staging computers), the Site Deployment Export dialog box is used to initiate the export process, resulting in a .rop file. This export process continues in the background, regardless of whether the Site Builder application is closed.

On computers serving as the deployment destination (the production computers), the Site Deployment Import dialog box is used to initiate the import process, extracting the state of various objects from a .rop file. Like the export process, the import process is performed in the background, and the Site Builder application can be closed without interfering with it.

The basic steps involved in deploying Content Management Server are:

  1. Export one or more objects to a package on the source computer, stored in a .rop file.
  2. Copy (or otherwise access) the .rop file to the destination computer.
  3. Import the object(s) in the .rop file into the destination computer.

As suggested by step 1, the export/import operations available in Site Deployment Manager can be performed in an incremental fashion. In other words, not all object types need to be exported, nor do all of the objects of a particular type need to be exported together. For example, just one portion of a Web site can be exported, such as a particular branch of channels or postings. Further, there are options for choosing whether to preserve the existing container hierarchy on the destination computer, or change it to correspond to a new hierarchy represented in the .rop file.

The following types of Content Management Server objects can be deployed to another computer by exporting their state into a .rop file:

  • Folders and pages
  • Channels and postings
  • Resource galleries and resources
  • Template galleries and templates
  • Rights groups and rights groups members

Site Deployment Manager is sophisticated enough to understand the various dependencies that can exist between these types of objects, such as pages being dependent on page templates and resources. Whenever an object is included in an export operation, Site Deployment Manager will also automatically export any other objects upon which the former objects depend.

What cannot be deployed using Site Deployment Manager are any file-based elements of the Web site, such as include files or other ASP files. Another deployment mechanism must be employed for such files, ranging from manual copying to a fully automated solution using a product like Microsoft Application Center.

Previous  Next


Microsoft Corporation - Microsoft. Net Server Solutions for the Enterprise
Microsoft .NET Server Solutions for the Enterprise
ISBN: 0735615691
EAN: 2147483647
Year: 2002
Pages: 483

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net