Download - Content deployment in MOSS 2007
Overview
• Content deployment feature overview• Typical usage scenarios• Architecture fundamentals• Paths and Jobs• Quick deploy jobs
• Deploy content from one site collection into another site collection. The source and destination site collections can be in the same farm or in different farms.
• Paths: A content deployment path defines a relationship between a source and destination site collection for content deployment. Once a path is created, jobs can be created and associated with the path to begin deploying content.
• Jobs: A job is associated with a path, and defines the specific content to be deployed from the source to the destination, and the schedule on which the deployment should occur.
What is Content Deployment?
Content Deployment Overview
• Copies content from one site collection to another site collection– Within a web application or farm – Across web applications or farms
• Secure, flexible and efficient• Automated – no manual interventions required• Comprehensive administration UI• Primarily for Intranet based authoring farm
Production Production FarmFarmAuthoring FarmAuthoring Farm
Web Front End
DBServer
`
Approvers
Authors
`
`
`
Approval Workflow
`
Web Designer
Word Authoring
Web-based Authoring
Master PagePage Layout
Content Deployment Topology
NLB
Web Front End
Content Content DeploymentDeployment
Content Deployment - Setup
• Controlled fromCentral Administration Operations tab:
• Must set up Content Deployment Settingsbefore configuring Paths and Jobs
• Create a Deployment Path
• Create a Deployment Job (schedule)
• Quick Deploy
Single farm deployment
• Deploy content between site collections with in the same farm
• Site collections should be in separate web applications
• Site collections should be in separate content database.
Fundamentals contd.
• Content deployment is not a replication or synchronization
• Three steps: – Exported from Source– Transported from source to destination– Imported to destination
• Uses HTTP/HTTPS • Requires FARM admin privileges to configure
Fundamentals
• Incremental by default• Versioning
– Most major and minor versions will be published.– Destination site must be a blank site for first time
deployment.
• Can be a processor intensive. If required need separate WFE
Content Deployment - Path
• Path– Defines source, target site collections– Specifies authentication information for deploy– Controls whether user names are deployed– ...and whether security info is deployed
• Paths can only be set up between servers in the same network
Content Deployment - Job
• Job– Bound to a single path– Specifies sites to deploy– Frequency of deployment– Notifications can be sent
Content Deployment
• Quick Deploy Job– Allows content authors to publish “On Demand”– Automatically created on sites with “Publishing
feature enabled”– Configurable schedule: 10 minutes minimum.– Can be enabled for any path– Allows delegation of deployment– ...at individual page level– Page authors can click “Quick Deploy” on page edit
toolbar
Content , Not code
• Only content is deployed– Features and solutions must be present on
destination– Copy the features to the destination server and
install them– Do not activate features on destination
• Content deployment will take care of activation
Additional considerations
• Do not edit the destination site directly!• Create a repeatable mechanism for deploying
code and configuration changes– Features and solutions– windows Power Shell
• ensure the infrastructure updates are applied
Thank You!