CONTENT DEPLOYMENT BOOTCAMP

Mark Rhodes

About Me•Infrastructure Consultant with OBS

•Infrequently blog at http://tinyurl.com/mrhodes

•Frequently tweet at @mrhodes

•Email markrhodes@gmail.com

WHAT IS CONTENT DEPLOYMENT AND WHAT DOES IT DO?

• MOSS 2007 / SharePoint Server 2010 Technology

• Replicates Content

• Can replicate across servers

• Is secure

• Works Efficient

• Can be very stable

• Retains Object Identities

• Fixes links

CONTENT DEPLOYMENT PERCEPTIONS

• The SharePoint team did a lot of work to optimize working with both Variations and Content Deployment. Both mechanisms are now more robust and reliable.

• Microsoft has done some significant work with the content deployment feature within SharePoint 2010. MOSS 2007 automated content deployment had serious limitations and was often avoided because of unexpected results. It is a bit early to say whether 2010 will avoid all of those issues, but getting a chance to work with it over the last days has demonstrated some huge improvements.

• The SharePoint team did a lot of work to optimize working with both Variations and Content Deployment. Both mechanisms are now more robust and reliable.

• I found the feature to be flaky in 2007, but if other improvements in 2010 are anything to go by I’m looking forward to seeing what it can do.

• Yes!

• Much better. I’ve found on a scale of 1 to 10 that Content Deployment 2010 is +3 to the scale of Content Deployment in SharePoint 2007.• Its fantastic, its such an improvement on 2010!

• Content Deployment indeed has a bad rep. Well deserved back in 2007 when MOSS was released. Not so much anymore. If done properly CDS will work just great in 2007 and there are some *huge* companies with *huge* sites using it. 2010 includes all the fixes from the IUs and beyond, in addition it has much better reporting and support for SQL Snapshots on export. Along with other under the covers improvements with PRIME.

• Content Deployment has had a bad rap over the initial stages of SharePoint 2007, however since Service Pack 2 there have been no compelling reasons not to use it when replicating content from a staging site to a production site.

• In the right hands, an extremely powerful tool for SharePoint Web Content Management

A BRIEF HISTORY OF CONTENT DEPLOYMENT

Microsoft Content Management Server

Microsoft Office SharePoint Server 2007

SharePoint Server 2010

EXAMPLE ARCHITECTURE

Internal Network Prod Network

Production ServerStaging Server

Internet

Content AuthorsContent

Deployment

Internal Network

Staging ServerContent Authors

ContentDeployment

SITUATIONS FOR CONTENT DEPLOYMENT?

• Security Concerns

• Site Performance

• Identical Content, Different Farm Topology

WHAT DOESN’T IT DO?

• Will not take anything stored outside of Site Collection

• Will not move configuration data or service application data

• Will not move solutions, features, assemblies

• Not designed for backup or restore purposes

• No Alerts, Audit Trail, Change Logs, Check In / Check Out State, Recycle Bin Items, Recycle Bin State, Security State, Workflow tasks, Workflow state.

• Bi-directional Replication

WHAT’S NEW IN 2010?

• Support for 2000+ pages on single site

• Web Analytics

• SQL Server Snapshot Support

• Publishing Sanity

• AJAX

• Content Deployment Aware Event Handling

• Support for Multi-Tenancy

Source ServerWeb Application

Site Collection

PATHS AND JOBS

Destination Server

Web Application

Site Collection PATHJob

GUI Options

• Source Web Application

• Destination Farm

• Destination Web Application

• Transmission Security

• Users and Security

API Options

• Compression

• Event Receiver Support

• Keep Temporary Files

CONTENT DEPLOYMENT ANATOMY : PATH

CONTENT DEPLOYMENT ANATOMY : JOB

Export Phase

Transmission Phase

Import Phase

Export Phase

Check Change Token

Export files

Package Files

Full DeploymentIncremental Deployment

Transmission Phase

Transmit Files

Poll Destination Status

Copy CompletedCopy in Progress

Import Phase

Import Processing Import Completed

Import SuccessfulImport Failed

Update Change TokenDiscard Change Token

Send Notification Emails

CONTENT DEPLOYMENT ANATOMY : PAYLOAD

{GUID}\ExportedFiles.CA

B

Configuration FilesExportSettings.xml LookupListMap.xml

Manifest.xml Requirements.xmlSystemData.xml RootObjectMap.xmlUserGroup.xml ViewFormsList.xml

ContentDAT Files

LETS SEE IT IN ACTIONContent Deployment Demo

TIPS FOR SUCCESSFUL IMPLEMENTATION

Security

Hygiene

DocumentationCommon Sense

Know your platform

TIPS FOR RECOVERING FAILED CONTENT DEPLOYMENTS

• Was the Destination Site blank?

• Recreate the Path and Job

• Create a fresh blank Site Collection

• Content Deployment Manifest Reader

• MOSS2007 – Service Packs and Cumulative Updates

• Check Trace Logs

• Upgrade to SharePoint 2010

RESOURCES

• Microsoft’s SharePoint 2010 Content Deployment Poster

• http://tinyurl.com/cdposter

• My Bloghttp://tinyurl.com/mrhodes

• Stefan Gossnerhttp://blogs.technet.com/b/stefan_gossner

• Spencer Harbarhttp://www.harbar.net

• Maxime Bombardierhttp://blogs.msdn.com/b/maximeb/

RESOURCES

QUESTIONS?

Thank you to our SponsorsPlatinum Media

Gold

Silver

Bronze