Content deployment entry (lower)

How to configure content deployment?

======================================

1. Create a New empty site set based on the blank site template on the target server farm to receive the initial deployment job.

2. on the target server farm, the SharePoint Management Center website, configure the current server farm on the content deployment settings page to allow receiving of the arrival deployment job, configure a WFE server as the import server to manage the incoming deployment job, and determine whether to enable encryption from the source server farm to the target server farm.

3. configure a front-end server as the export server on the content deployment settings page to manage the output deployment job.

4. In the source server farm, create one or more deployment paths on the manage content deployment path and Jobs page of the management center.

5. In the source server farm, create one or more deployment jobs for each deployment path on the manage content deployment path and Jobs page.

6. Run the initiate deployment job to initialize content on the target server farm.

7. If the path does not deploy all the security information, create an initial user set, role, and permission for the content and site on the target server farm.

 

Security of content deployment

======================================

The content security configuration of the target server farm is usually different from that of the source server farm. in many publishing solution, the target server farm authenticates users through different Active Directory domains, instead of the Creation environment or the domain in the production environment, there may be no trust relationship in these two domains.

 

When configuring content deployment path, you can choose from the following security options:

• All. deploy all content-related security information, including role definition and access control lists (map user and role to the content and configure whether they have read or modify permissions ), there are also users. this option is valid for user sets with the same permissions in the source and target server farms. for example, this option may be the best when deploying from authoring farm to staging farm, because the same user needs to have the same permissions in both sets.
• Role deninitions only. deploy the content-related role definitions and access control lists ). in this option, the same role will be applied to the source and target server farms, but different users will be added to different roles in different server farms.
• None. do not deploy any security information. the Security Information in the target field must be managed by the administrator of the target field, and the user and role permissions must be granted to access the site and content in the field. for example, if you deploy an Internet-facing site from staging farm to a company, this option will help us ensure that the security options in the two server farms are managed independently.

Definition of content deployment

======================================

Content deployment copies content from a source Moss site to the target Moss site. the whole source site set can be copied (full mode), or a part of the site set can be copied (incremental ). in any case, content deployment is incremental by default, and only the changed pages are deployed with related resources (such as images ). you can perform full deployment on the site. However, you should only run full deployment job when deploying an empty site set. in addition, the quick deployment feature allows the author to deploy a single page.

Note: To make the quick deployment feature work properly, you must enable the Office Sharepoint Server publishing infrastructure feature for both the source site set and target site set.

 

 

Content source:

Plan content deployment

Http://technet.microsoft.com/en-us/library/cc263428.aspx

Link:

Content deployment (Part 1)

Http://www.cnblogs.com/awpatp/archive/2010/01/06/1640624.html