O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

MOSS Content Deployment 12.18.2008 Final

2.353 visualizações

Publicada em

Publicada em: Tecnologia
  • Entre para ver os comentários

MOSS Content Deployment 12.18.2008 Final

  1. 1. SHADEED ELEAZER, MCTS MOSS 2007 Content Deployment
  2. 2. Lecture Objectives <ul><li>Discuss history of deployment and publishing strategies in SharePoint’s previous platforms </li></ul><ul><li>Content Deployment Overview </li></ul><ul><li>Why utilize Content Deployment? </li></ul><ul><li>Deployment strategies and scenarios </li></ul><ul><li>Configuring Content Deployment </li></ul><ul><li>Walkthrough </li></ul><ul><li>FAQ </li></ul>
  3. 3. Meet the Speaker <ul><li>Shadeed Eleazer, MCTS </li></ul><ul><li>SharePoint integration with various third party server platforms. </li></ul><ul><li>Design, configuration, deployment, and testing of SharePoint servers. </li></ul><ul><li>Extensive enterprise SharePoint backup and recovery experience </li></ul><ul><li>Co-Founder Baltimore SharePoint User’s Group </li></ul><ul><li>Former VP of Marketing SharePoint User’s Group of Northern VA </li></ul>
  4. 4. Meet the Audience <ul><li>Please Provide a Brief Introduction </li></ul><ul><li>Primary SharePoint Skillset </li></ul><ul><li>Describe your current SharePoint environment </li></ul>
  5. 5. The Rules <ul><li>Questions are encouraged at any time during this discussion. </li></ul><ul><li>For additional questions resources: </li></ul><ul><li>[email_address] </li></ul><ul><li>www.twitter.com/mrshadeed </li></ul>
  6. 6. SharePoint Management History <ul><li>Managing WSS 2.0 and SPS 2003 dev-staging-production environments required updates made in real-time which caused difficulty from management/administrative perspectives. </li></ul><ul><li>Compromised the integrity of maintaining separate environments. </li></ul><ul><li>Configuration Management became a major pain-point for many organizations </li></ul>
  7. 7. Pre-Content Deployment <ul><li>Admins deploy changes from development team. </li></ul>Dev/Testing Production Command Line (STSADM) Developers Project Managers Administrator
  8. 8. <ul><li>Microsoft discontinued support on MCMS 2002 and rolled its core capabilities into MOSS 2007. </li></ul><ul><li>Built upon the Site Deployment feature of MCMS . </li></ul><ul><li>Utilizes the Content Migration API also known as “Prime” </li></ul><ul><li>Content Deployment is a feature of the Web Content Management subset of MOSS 2007. </li></ul>Content Deployment Working Parts
  9. 9. Content Deployment Is….. <ul><li>A MOSS 2007 native feature that allows administrators and specific members of an organization to manage scheduled content updates from one site collection to another. </li></ul><ul><li>A method to deploy updates through dev/QA/staging/production etc. in a repeatable manner without manually re-creating content which hinders scalability. </li></ul>
  10. 10. Content Deployment Is Not… <ul><li>An item-level migration tool between server farms and/or site collections </li></ul><ul><li>A feature utilized for backup and recovery of SharePoint sites and/or farm. </li></ul><ul><li>A two-way communication between two or more servers. </li></ul>
  11. 11. Configuration Essentials <ul><li>The destination site collection must be a blank site template. </li></ul><ul><li>The account used to configure content deployment must have access to the destination’s Central Administration. </li></ul><ul><li>You cannot deploy to sites hosted within the same web application. </li></ul><ul><li>A dedicated path must be configured to run jobs. </li></ul><ul><li>The destination must utilize a separate content database. </li></ul>
  12. 12. Deployment Strategies and Scenarios
  13. 13. The Basics <ul><li>Content Deployment Path – A dedicated server to server connection established between two SharePoint WFE. </li></ul><ul><li>A path tells MOSS where to deploy content to. </li></ul><ul><li>Content Deployment Jobs – A job tells MOSS when and what content should be deployed. </li></ul><ul><li>You can have one path but multiple jobs. </li></ul><ul><li>Quick Deploy Jobs enable members of Quick Deploy Group to publish single pages. Helpful for publishing to internet facing sites. </li></ul>
  14. 14. STSADM vs. Content Deployment <ul><li>If I have STSADM command-line tool why would I need content deployment? </li></ul><ul><li>Content Deployment is a better option in the following scenarios: </li></ul><ul><li>Environments with mixed permissions levels </li></ul><ul><li>Agencies with strict permission levels and server access. </li></ul><ul><li>24 hour Operations/Data centers that don’t allow quiesce of SharePoint server farm to run command line backup. </li></ul>
  15. 15. Real World Scenario <ul><li>Collaborative environments typically have different teams with varying permissions contributing to the same project. </li></ul>Public Facing Site Developers Designers Administrators
  16. 16. Deployment Scenario Permissions/Roles <ul><li>Permissions/Role Allocation </li></ul>Public Facing Site Prepare/Deploy Solutions Quick Deploy Grp Configure Path and Jobs
  17. 17. Designing Content Deployment Topology <ul><li>Typical Deployment Topology </li></ul><ul><li>Server Roles </li></ul><ul><li>Authoring/Dev   The farm contains the site collection that is used by the content-creating team to write the content. </li></ul><ul><li>Staging   The farm contains a site collection that is a copy of the production site collection, so that the content can be reviewed and tested before it is published. </li></ul><ul><li>Production   The farm contains the site collection that presents the content to its intended audience, and it usually has tightened security. </li></ul>
  18. 18. Server Topologies <ul><li>Single-farm topology </li></ul><ul><li>Authoring/Development in one site collection. </li></ul><ul><li>Deploy to a duplicate site collection on the same farm. </li></ul><ul><li>Separate source and destination Web applications </li></ul><ul><li>Separate Databases </li></ul><ul><li>Security management is based on access to the content as opposed to separate AD Domains. </li></ul>
  19. 19. Deployment Topologies <ul><li>Three-stage Topology </li></ul><ul><li>Dev/Authoring farm- Staging farm -Production farm </li></ul><ul><li>The staging farm is used to test or review the content before it is published to the production farm. </li></ul><ul><li>Dev farm Web Front End configured to export content. </li></ul><ul><li>Staging farm configured to export content. </li></ul><ul><li>Web server in the authoring farm must be configured to export content. A front-end server in the staging farm must be configured to import and export content. A front-end server in the production farm must be configured to import content from the staging farm. </li></ul>
  20. 20. Content Deployment Walkthrough <ul><ul><ul><ul><ul><li>Walkthrough </li></ul></ul></ul></ul></ul>
  21. 21. Common Cause of Problems <ul><li>Misunderstanding of the Content Deployment feature. </li></ul><ul><li>Lack of clearly defined configuration standards between Development/Staging/Production environment. </li></ul><ul><li>Lack of awareness of documented bugs and available patches. </li></ul>
  22. 22. Content Deployment Wizard <ul><li>Created by SharePoint MVP Chris O’Brien </li></ul><ul><li>Available on Codeplex Rls: 1.1 on Sep 22 2008 </li></ul><ul><li>http:// www.codeplex.com/SPDeploymentWizard </li></ul><ul><li>Key Functions </li></ul><ul><li>Moving list items from source to destination </li></ul><ul><li>Moving this document library from A to B </li></ul><ul><li>Moving Master pages, Page layouts, CSS etc. from A to B </li></ul><ul><li>Moving site collections from A to B </li></ul><ul><li>Moving list items from A to B </li></ul>
  23. 23. FAQ <ul><li>How does Content Deployment handle custom webparts and customizations? </li></ul><ul><li>How does Content Deployment handle Search settings? </li></ul><ul><li>How does Content Deployment handle separate Authentication zones? </li></ul><ul><li>When should my organization plan Content Deployment? </li></ul><ul><li>How has Service Pack 1 impacted Content Deployment? </li></ul><ul><li>What are known issues that you’ve encountered? </li></ul>
  24. 24. The End <ul><li>Questions/Comments. </li></ul>