In a publishing environment, different servers would be used for content authoring, staging, and publishing. In such a scenario, content approved for publishing needs to be deployed from the staging area to the production server. To facilitate this process, SharePoint 2007 provides built-in content deployment capabilities. This section explores the main components of content deployment and the different configuration aspects involved in setting it up.
One of the many features of WCM is the built-in content scheduling and content deployment capabilities. This section explores the content deployment features in more detail.
Content deployment in configured in two phases:
A path represents the connection between the source and the destination web applications. When a path is created, a quick-deploy feature associated with the path is also created. Quick deploy is a special job that can be configured to run at frequent intervals and allows authors to publish content immediately without waiting for the scheduled content deployment job to run. Authors need to belong to the Quick Deploy Users group in order to publish content through this special job.
A job is associated with the path and represents the deployment of a specific site collection or site under the source web application. A job can be scheduled to run at a specific time, and can also be configured to deploy all or incremental changes.
To configure content deployment, follow these steps: ...