Content deployment in MOSS 2007

1,853 views
1,694 views

Published on

Content deployment in MOSS 2007

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,853
On SlideShare
0
From Embeds
0
Number of Embeds
221
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • © 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

    1. 1. 13 th May, 2010 Salaudeen Rajack [email_address] Content Deployment
    2. 2. Overview <ul><li>Content deployment feature overview </li></ul><ul><li>Typical usage scenarios </li></ul><ul><li>Architecture fundamentals </li></ul><ul><li>Paths and Jobs </li></ul><ul><li>Quick deploy jobs </li></ul>
    3. 3. <ul><li>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. </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul>What is Content Deployment?
    4. 4. Content Deployment Overview <ul><li>Copies content from one site collection to another site collection </li></ul><ul><ul><li>Within a web application or farm </li></ul></ul><ul><ul><li>Across web applications or farms </li></ul></ul><ul><li>Secure, flexible and efficient </li></ul><ul><li>Automated – no manual interventions required </li></ul><ul><li>Comprehensive administration UI </li></ul><ul><li>Primarily for Intranet based authoring farm </li></ul>
    5. 5. Content Deployment Topology Production Farm Authoring Farm Content Deployment
    6. 6. Content Deployment - Setup <ul><li>Controlled from Central Administration Operations tab: </li></ul><ul><li>Must set up Content Deployment Settings before configuring Paths and Jobs </li></ul><ul><li>Create a Deployment Path </li></ul><ul><li>Create a Deployment Job (schedule) </li></ul><ul><li>Quick Deploy </li></ul>
    7. 7. Single farm deployment <ul><li>Deploy content between site collections with in the same farm </li></ul><ul><li>Site collections should be in separate web applications </li></ul><ul><li>Site collections should be in separate content database. </li></ul>
    8. 8. Fundamentals contd. <ul><li>Content deployment is not a replication or synchronization </li></ul><ul><li>Three steps: </li></ul><ul><ul><li>Exported from Source </li></ul></ul><ul><ul><li>Transported from source to destination </li></ul></ul><ul><ul><li>Imported to destination </li></ul></ul><ul><li>Uses HTTP/HTTPS </li></ul><ul><li>Requires FARM admin privileges to configure </li></ul>
    9. 9. Fundamentals <ul><li>Incremental by default </li></ul><ul><li>Versioning </li></ul><ul><ul><li>Most major and minor versions will be published. </li></ul></ul><ul><ul><li>Destination site must be a blank site for first time deployment. </li></ul></ul><ul><li>Can be a processor intensive. If required need separate WFE </li></ul>
    10. 10. Content Deployment - Path <ul><li>Path </li></ul><ul><ul><li>Defines source, target site collections </li></ul></ul><ul><ul><li>Specifies authentication information for deploy </li></ul></ul><ul><ul><li>Controls whether user names are deployed </li></ul></ul><ul><ul><li>...and whether security info is deployed </li></ul></ul><ul><li>Paths can only be set up between servers in the same network </li></ul>
    11. 11. Content Deployment - Job <ul><li>Job </li></ul><ul><ul><li>Bound to a single path </li></ul></ul><ul><ul><li>Specifies sites to deploy </li></ul></ul><ul><ul><li>Frequency of deployment </li></ul></ul><ul><ul><li>Notifications can be sent </li></ul></ul>
    12. 12. Content Deployment <ul><li>Quick Deploy Job </li></ul><ul><ul><li>Allows content authors to publish “On Demand” </li></ul></ul><ul><ul><li>Automatically created on sites with “Publishing feature enabled” </li></ul></ul><ul><ul><li>Configurable schedule: 10 minutes minimum. </li></ul></ul><ul><ul><li>Can be enabled for any path </li></ul></ul><ul><ul><li>Allows delegation of deployment </li></ul></ul><ul><ul><li>...at individual page level </li></ul></ul><ul><ul><li>Page authors can click “Quick Deploy” on page edit toolbar </li></ul></ul>
    13. 13. Content , Not code <ul><li>Only content is deployed </li></ul><ul><ul><li>Features and solutions must be present on destination </li></ul></ul><ul><ul><li>Copy the features to the destination server and install them </li></ul></ul><ul><ul><li>Do not activate features on destination </li></ul></ul><ul><ul><ul><li>Content deployment will take care of activation </li></ul></ul></ul>
    14. 14. Additional considerations <ul><li>Do not edit the destination site directly! </li></ul><ul><li>Create a repeatable mechanism for deploying code and configuration changes </li></ul><ul><ul><li>Features and solutions </li></ul></ul><ul><ul><li>windows Power Shell </li></ul></ul><ul><li>ensure the infrastructure updates are applied </li></ul>
    15. 15. Thank You!

    ×