Content deployment in MOSS 2007
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Content deployment in MOSS 2007

on

  • 1,936 views

Content deployment in MOSS 2007

Content deployment in MOSS 2007

Statistics

Views

Total Views
1,936
Views on SlideShare
1,736
Embed Views
200

Actions

Likes
0
Downloads
6
Comments
0

12 Embeds 200

http://www.sharepointdiary.com 91
http://salaudeen.blogspot.com 70
http://salaudeen.blogspot.in 23
http://salaudeen.blogspot.co.uk 4
http://salaudeen.blogspot.com.au 3
http://salaudeen.blogspot.no 2
http://salaudeen.blogspot.de 2
http://salaudeen.blogspot.ca 1
http://salaudeen.blogspot.dk 1
http://salaudeen.blogspot.pt 1
http://salaudeen.blogspot.co.at 1
http://salaudeen.blogspot.com.br 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Office System Developer Conference 2006
  • 04/09/11 13:39 © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Content deployment in MOSS 2007 Presentation Transcript

  • 1. 13 th May, 2010 Salaudeen Rajack [email_address] Content Deployment
  • 2. Overview
    • Content deployment feature overview
    • Typical usage scenarios
    • Architecture fundamentals
    • Paths and Jobs
    • Quick deploy jobs
  • 3.
    • 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?
  • 4. 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
  • 5. Content Deployment Topology Production Farm Authoring Farm Content Deployment
  • 6. Content Deployment - Setup
    • Controlled from Central Administration Operations tab:
    • Must set up Content Deployment Settings before configuring Paths and Jobs
    • Create a Deployment Path
    • Create a Deployment Job (schedule)
    • Quick Deploy
  • 7. 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.
  • 8. 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
  • 9. 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
  • 10. 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
  • 11. Content Deployment - Job
    • Job
      • Bound to a single path
      • Specifies sites to deploy
      • Frequency of deployment
      • Notifications can be sent
  • 12. 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
  • 13. 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
  • 14. 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
  • 15. Thank You!