[Read notes] content deployment full Guide II Basic knowledge continue

Content deployment stage

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

Content deployment is divided into several different stages, which are partially executed on the source and target servers.

 

Preparation Phase

---------------

This stage is unique for jobs started through the Management Center UI. At this stage, the code in the exported server UI creates a one time timer job to execute the export operation.

 

Export phase

----------------

This stage is executed on the export server in the source field. it uses the content deployment and migration APIs of WSS to export content related to a specific content deployment job. the content will be exported to a flat file in the temporary folder of the export server.

 

Compression stage

----------------

This stage is executed on the export server in the source field. it uses the content deployment and migration APIs in WSS to compress the exported files to one or more compressed package files (cabinet files) (CAB files ). these files are stored in a temporary folder on the export server.

 

Transmission Phase

----------------

This stage is executed on the export server in the source field. it uses some of the content deployment feature features provided by moss 2007. in this phase, the compressed package files (cabinet files) are uploaded to the import server in the target site using the HTTP protocol, and are also stored in the Temporary Folder.

 

Decompression phase

-----------------

This phase is executed on the import server in the target field. It is completed through the WSS content deployment and migration APIs. They will decompress the compressed package files to the temporary folder of the import server.

 

Import phase

------------------

This stage is executed by the import server in the target field. import the decompressed files from the Temporary Folder through the WSS content deployment and migration APIs, and then generate content in the target site.

 

 

Content deployment path and task

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

Content deployment is based on two basic conceptual objects: content deployment path (PATH) and task (job ).

 

 

Content deployment path

-------------------

Content deployment allows you to deploy content from a site set in the source site to a site set in the target site.

 

The link between the source and target site sets is called the content deployment path. You can have multiple content deployment paths in the server farm, as long as their source and target site sets are not the same.

 

A content deployment path is always defined in the source field.

 

The two content deployment paths reference a site set in the source field as the source, and the two different site sets in the target field as the destination.

 

It should be noted that the source site and target site set can exist in the same server farm. therefore, the path can point to two different site sets in the same server farm, as long as the two site sets are not stored in the same content database.

 

Important: You cannot specify the site set that exists in the same database as the source site and target site set. the content deployment of the path in which this configuration is executed will cause an exception during the import phase, because this will cause the items with the same ID to exist twice in the same database, and SharePoint will not allow the items.

Similarly, you cannot specify multiple target site sets in the same content database to obtain content from the same source site set.

 

 

Content deployment task

-------------------

It is possible to create one or more content deployment tasks for a content deployment path. each job can be of different types (complete, incremental, and Fast deployment) and can be configured with different time plans.

 

In addition to rapid deployment, it is possible to configure different content deployment tasks and deploy different parts of the source site set in the same path. you can select a specific site to be deployed in a specific task. in this way, some parts of the site can be deployed once a day, while some frequently updated content in the site is deployed once an hour.

 

You cannot manually create a quick deployment task. when the publishing feature in the source site is activated, it is automatically created when the content deployment path is saved. one path can only have one quick deployment task.

 

Content deployment job is always defined in the source field. during the deployment to the target server farm, a "shadow" content deployment task is created in the target farm for import. this task will be automatically deleted after the import is successful.

 

Note that the "shadow" task is not displayed in the content deployment path and task page in the target field, because the task is not bound to a content deployment path.

 

Original article address:

Http://blogs.technet.com/stefan_gossner/archive/2009/11/02/content-deployment-the-complete-guide-part-2-the-basics-continued.aspx