Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cotent Deploymet In Share Point 2007


Published on

A Presentation on Content Deployment Feature in SharePoint 2007

Published in: Technology
  • Be the first to comment

Cotent Deploymet In Share Point 2007

  1. 1. Online Training on SharePoint 2007<br />Check Training Details @Training Details<br />MossExperts<br /><br />
  2. 2. Content Deployment in SharePoint <br />MossExperts<br /><br />
  3. 3. Content Deployment – The Idea<br />Content Deployment allows to push out content from one server farm to another .<br />Content Deployment allows the deployment of content from exactly one site collection on the source farm to exactly one site collection on the target farm<br />MOSS 2007 contains Content Deployment as a new feature which has been added to fulfill the requirements of companies which plan to use SharePoint as a Web server to host public facing Web sites<br />The main purpose is to allow authors and reviewers to modify and evaluate on a different farm before the content is finally pushed to the public facing server farm<br /><br />
  4. 4. Content Deployment – The Idea<br />To have a single authoring environment and then push the content to multiple different farms of different departments - potentially on different continents.<br />The entire source site collection can be copied (full), or a subset of sites can be copied (incremental). In either case, content deployment is incremental by default, deploying only changed pages and related assets (such as images)<br />Content deployment only copies content — Web pages and resources used by the copied pages.<br />It does not deploy programs, assemblies, features, configuration information such as web.config files.<br />When a Web page is deployed, any items in the content database that the page depends on — such as images, style sheets, or layout pages — will also be deployed.<br /><br />
  5. 5. Sample Scenario<br /><br />
  6. 6. Supported Scenario<br />Not Supported Scenario<br /><br />
  7. 7. Content Deployment Path<br />A path is basically a connection between a source farm and a destination farm or<br />The link between the source and target site collection is called a content deployment path<br />The path contains information about which source web application and site collection you are deploying, authentication information for the destination farm, and the web application and site collection on the destination farm.<br />Multiple content deployment paths are possible in the farm as long as we don&apos;t have multiple paths that reference the same source and target site collection<br />A content deployment path is always defined on the source farm.<br />A path by itself doesn’t actually deploy any content.<br /><br />
  8. 8. Content Deployment Job<br />A job is associated with a path, and it determines exactly which sites in the source site collection will be deployed and on what schedule<br />One or more content deployment jobs for a single content deployment path. <br />Each job can be of a different type <br />Full<br />Incremental <br />Quick deployment<br />The content deployment job is always defined on the source farm<br />Each job can be configured with a different schedule.<br /><br />
  9. 9. Steps for Content Deployment <br />Create Production Site Collection and take Blank Template<br />Allow Incoming Content Deployment Jobs on the Production Site<br />Create Content Deployment Path from Staging to Production<br />Click New Path<br />Click Connect and Click OK<br />Create Content Deployment Job<br />Run Content Deployment Job <br />Run Quick Deploy Job<br /><br />
  10. 10. Quick Deployment Job<br />Content Deployment has a special job called “Quick Deploy” that is automatically created for every path in any site collection with the Publishing Resources feature enabled. <br />This job, once enabled in a path, runs every 15 minutes, by default) and checks a special list for content that should be deployed. <br />If the site owner has rights, he or she can deploy pages quickly to production by using the “Quick Deploy” link on the Page Editing toolbar. This adds that page to the special list, which the Quick Deploy job will check the next time it wakes up<br /><br />
  11. 11. Content Deployment Job Process<br />Every time a content deployment job runs, the following five steps are always executed:<br />Check the change log to determine changes.   After a job successfully completes a schedule, in the last step it updates the log on the source server to track the status of the content on the destination servers. This status is initially checked by each job to determine which content needs to be updated on the destination servers.<br />Create a new package on the source server.   This package is created based on information in the change log and temporarily deployed on the source server file system.<br /><br />
  12. 12. Content Deployment Job Process<br />Send the package to the destination server.   The deployment job uses HTTP or HTTPS protocols (depending on the setting in the Content Deployment feature). <br />Apply changes to the destination server.   After a package arrives at the destination server, the content deployment job temporarily extracts the files to a local folder and starts to apply the changes. It’s important to understand that this is not a transactional operation — if something happens while changes are being applied (such as a local failure, an exception, or a power outage), all changes that were applied successfully will not be rolled back. The next time the same job runs, it will try to re-apply the same changes.<br />Update the change log on the source server.   The last step a job performs is to update the content status of the destination site collection on the source server.<br /><br />
  13. 13. Important Considerations<br />The servers configured as export and import server need to host an instance of the Central Administration website <br />Ensure that sufficient disk space is available<br />Use an empty site collection as the destination of your content deployment job<br />Install all required features for your site on the destination server<br />Do not activate custom features for your site collection on the destination server manually<br /><br />
  14. 14. Important Considerations<br />The incremental deployment will not deactivate features in the destination server site collection<br />Ensure that all feature definitions of features activated on the site collection exist on the source server<br />Ensure that content deployment jobs do not run in parallel<br />Ensure that the patch level on source and destination farm is identical<br /><br />