By mapping each goal to a specific requirement and solution, you create an easy to follow architecture for your portal. Each requirement is implemented by one of more features and you can create an installation and configuration checklist that maps directly to your requirements.
This section walks though the SharePoint implementation for each requirement and solution outlined in Table 22.2.
You will configure the ability to deploy content across multiple servers, from one site collection to another so that staged content is modified on the internal server and published content is modified only via the content deployment process.
You must first define the content deployment path and then configure a job to deploy content for the content path. The content deployment path defines the relationship between the two site collections for deployment. Jobs determine the specific content to be deployed from the source to the target and the schedule upon which the deployment occurs.
Paths and jobs are created from the SharePoint 3.0 Central Administration site.
For more information on content deployment jobs, please see Chapter 11.
From Central Administration, navigate to the Operations page.
In the Content Deployment section, click Content deployment paths and jobs.
On the Manage Content Deployment Paths and Jobs page, click New Path.
In the Name and Description section, ...