Content deployment sharepointserver2010
0 likes214 views
Content deployment in SharePoint Server 2010 allows copying content from a source site collection to a destination site collection. It is commonly used to separate authoring and production environments. The content deployment process involves defining paths between source and destination sites, running jobs on a schedule to export content from the source and import it into the destination. It can be useful when topologies, security, or performance needs differ between environments.
Content deployment sharepointserver2010
- 1. Content Deployment in SharePoint Server 2010 Overview of content deployment Content deployment process flow What is content deployment? When to use content deployment The tasks involved in content deployment are controlled by the timer The content deployment job uses the service account information that is process on the server that hosts the Central Administration Web site provided in the content deployment path settings to authenticate with a that is used to administer the content deployment jobs. Web service on the destination server. This Web service acts as the Content deployment is a subset of the Enterprise Content Management feature of Although content deployment can be useful for copying content from one site collection pathway for all communication between the source and destination servers. Microsoft SharePoint Server 2010 that you can use to copy content from a source site to another, it is not a requirement for every scenario. The following list contains reasons collection to a destination site collection. Most content deployment topologies include for why you might want to use content deployment for your solution: two or more server farms, to separate the authoring environment from the production 1 When a content deployment job starts, it checks the change token to · The farm topologies are completely different. A common scenario is one in which determine when the last successful content deployment job was run. environment. Source Server there are authors publishing content from an internal server farm to an external In most content deployment scenarios, the source site collection, from which content is server farm. The topologies of the server farms can be completely different. After the change token has been verified, the export process is started being deployed, is in a server farm that is separate from the destination site collection. However, the content of the sites to be published is the same. on the source server. If SQL snapshots are enabled for the content Typically, the destination server farm (the "production" farm) has tightened security to · The servers require specific performance tuning to optimize performance. If deployment job, a snapshot is taken before the export process starts. minimize the actions that can be done in the production environment. It is not expected you have a server environment in which both authors and readers are viewing that authoring will be done on the production server, because changes to content on the content, you can separately configure the object and output caches on the different Start the content In preparation for export, settings such as the file location, base file production server might be overwritten by a content deployment job. In most content deployment job. site collections based on the purpose of the site or the user role. name, and other values are specified for the content deployment job. deployment scenarios, the source server farm and the production server farm are in independent Active Directory® domains. · There are security concerns about content that is deployed to the destination farm. If you do not want users to have separate accounts on the production server, 2 Next, the content to be included is exported to a temporary and you do not want to publish by using only approval policies, content deployment What are paths and jobs? 1 directory on the source server, where it is packaged into .cab files lets you restrict access to the production server. Check changeLog on for transport. Alternatives to content deployment source server for A content deployment path defines a source site collection from which content content. Alternatively, you can use the deployment can originate, and a destination site collection to which content is deployed. Microsoft.SharePoint.Deployment.SPExport namespace from the A path can be associated with only one site collection. Before you implement a content deployment solution, you should carefully consider SharePoint Server 2010 API to export content. whether content deployment is really necessary. The following list contains alternatives A content deployment job copies specified content on a specified schedule by using a to using content deployment: specified path. After a path is defined, one or more content deployment jobs can be 2 After the source server has authenticated with the Web service on defined. · One alternative is to extend a Web application. This option lets you have a separate Export files to local the destination server, it calls the Web service to prepare the import IIS Web site that uses a shared content database to expose the same content to temp directory. on the destination server. There are two kinds of standard content deployment jobs: full and incremental. These different sets of users. This is typically used for extranet deployments in which jobs are managed by a server farm administrator, and they enable you to specify different users access content by using different domains. After the files have been packaged into .cab files on the source server, whether to deploy all content, including any content that might have been deployed 3 previously, or only content that was added, updated, or deleted since the last successful · A second alternative is to use the Microsoft.SharePoint.Deployment.SPExport and the files are transported to a local temporary directory on the deployment. These jobs are run on a schedule that the server farm administrator Microsoft.SharePoint.Deployment.SPImport namespaces from the SharePoint destination server via HttpPost. specifies. Server 2010 API to develop a custom solution to meet your needs. Package files into .cab files. The content deployment job then calls the Web service to start the A third kind of content deployment job, Quick Deploy, is a special job that enables users · A third alternative is to use backup and recovery to copy content from one site import process on the destination server. to quickly publish content without waiting for the next standard content deployment job to collection to another. run. This job runs automatically, at a specified interval. In preparation for import, settings such as file location, base file name and other values are set by using the information that was stored in the 3 content deployment job when the files were prepared on the source How many farms do you need? Send .cab files to server. destination server. Destination Authoring and production farm Server Description Recommended for: 4 While import is in progress, the content The two-farm topology is a standard Internet site topology and is typical of § Internet-facing sites. deployment job calls the Web service to get the Internal network Perimeter network status of the import process. topologies that are used to publish an Internet site. It includes two server § Extranet sites with read-only access. 4 farms: one to host the production site collection and the other to host the Poll destination Copy .cab files to authoring site collection along with other sites that are used by the local temp directory. server for status. authoring team. Users of the production server farm belong to a separate Active Directory® domain, and some production farm users might be During import, the .cab files are extracted to a anonymous. 5 temporary directory on the destination server, · A front-end Web server in the authoring farm must be configured to and then they are imported into the database. Authoring farm Production farm 5 export content from the authoring site collection to the production farm. Any site collection features that are required Extract .cab files. by items that were included in the import are · One front-end Web server in the production farm must be configured to activated, and scheduling is then configured import content from the authoring farm. for the imported items. No Is import done? Authoring, staging, and production farm Alternatively, you can use the Microsoft.SharePoint.Deployment.SPImport Description namespace from the SharePoint Server 2010 Recommended for: Import files into API to import content. A three-stage topology includes an authoring farm, a staging farm, and a Internal network Perimeter network § Environments in which a multistage database. production farm. The staging farm is used to test or review the content approval process is a business Yes before it is published to the production farm. The site collections for requirement. authoring and staging can be located within the same farm. § Validating content in an environment that is more reflective of the 6 · A front-end Web server in the authoring farm must be configured to After import has finished, it returns either a production environment before 6 export content to both the staging and production farms. Discard change Import status = Return import Success or Failure status to the Central Authoring farm Staging farm Production farm deploying it to production. No Success? Status. token. Administration server. If the import status is · A front-end Web server in both the staging and production farms must be § Testing content with custom Web Success, the change token is saved. If the configured to import content from the authoring farm. Parts and code before moving it to import status is Failure, the change token is the production farm. discarded. Yes Single publishing farm Description Recommended for: Single Farm Update changeLog on source server. Content deployment can be configured within a single server farm. In · Intranet environments. this topology, authors work in one site collection and deploy to a Application pool A Application pool B · External environments in which duplicate publishing site collection on the same farm. The site collections Web application—Authoring Content Web application—Published Content staging verification is not a business are in separate Web applications, and they use separate databases on requirement. the same computer running Microsoft® SQL Server®. http://authoring http://Fabrikam · Segregating security settings and Content Note If you have a single farm, consider extending the Web application authentication between two deployment job to a separate IIS Web site, rather than using content deployment. This HR Facilities Purchasing HR Facilities Purchasing locations, when only one farm is ends. option uses the same content database for both sites, and reduces available or necessary. administrative overhead by eliminating the need to manage content deployment paths and jobs, and manage multiple site collections. DRAFT This document supports a preliminary release of Microsoft® SharePoint® Server 2010. © 2009 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].