1 / 37

OFC329 Migrating your CMS 2002 web sites to Microsoft Office SharePoint Server 2007

OFC329 Migrating your CMS 2002 web sites to Microsoft Office SharePoint Server 2007. Arpan Shah Group Product Manager. Session Objectives and Key Takeaways. Pre-requisites: You must be familiar with Office SharePoint Server You must know CMS 2002 Session Objectives

rae
Télécharger la présentation

OFC329 Migrating your CMS 2002 web sites to Microsoft Office SharePoint Server 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. OFC329Migrating your CMS 2002 web sites to Microsoft Office SharePoint Server 2007 Arpan Shah Group Product Manager

  2. Session Objectivesand Key Takeaways • Pre-requisites: • You must be familiar with Office SharePoint Server • You must know CMS 2002 • Session Objectives • Understand the two core piecesof migration – content and code • Understand the use of the content migration feature • Understand how out of the box features eliminate common custom code solutions • Your CMS ’02 content will make it into Microsoft Office SharePoint Server 2007!

  3. Agenda • Migration strategy • Content migration • Artifact mapping • Using a migration profile • Pre-migration analysis • Where your content goes • Re-branding • Code migration • Application analysis • Replacing custom code with new outof the box features

  4. The Art of Migration “If you know the enemy and know yourself, you need not fear the result of a hundred battles. If you know yourself but not your enemy, for every victory gained you will also suffer a defeat. If you know neither the enemy nor yourself, you will succumb in every battle.” The Art of War, by Sun Tzu

  5. Technology Convergence Content Management Server 2002 SharePoint Portal Server 2001 SharePoint Team Services “v1” SharePoint Portal Server 2003 Windows SharePoint Services “v2” Windows SharePoint Services “v3” Office SharePoint Server 2007 Portal, Web Content Management, and More

  6. 2007 Microsoft Office Servers Base CALs Enterprise CALs E-Forms services Spreadsheet publishing and reporting Business data integration Collaboration portal + content management Document lifecycle capabilities Enterprise search enhancements Publishing of InfoPath forms Editing and submitting via browser Centralized e-Forms catalog and lifecycle management Project tracking Plan, schedule, assign resources Time and status reporting Portfolio analysis and optimization Track assets, operations, & products Life cycle analysis and planning On-premise server with AD integration Deploy, manage & integrate clients Relay Manager & Data Bridge - Utility Server -No CAL Required

  7. Platform ServicesWorkspaces, Mgmt, Security, Storage, Topology, Site Model Microsoft SharePoint Feature Areas Server-based Excel spreadsheets and data visualization, Report Center, BI Web Parts, KPIs/Dashboards Docs/tasks/calendars, blogs, wikis, e-mail integration, project management “lite”, Outlook integration, offline docs/lists Business Intelligence Collaboration Enterprise Portal template, Site Directory, My Sites, social networking, privacy control Rich and Web forms based front-ends, LOB actions, pluggable SSO BusinessForms Portal Content Management Search Integrated document management, records management, and Web content management with policies and workflow Enterprise scalability, contextual relevance, rich people and business data search

  8. Getting On The Microsoft Office SharePoint Server 2007 Train • Two core pieces • Content • Code • We'll talk about both • Most common custom-code solutionsare handled by out of the box features

  9. Migration Strategy • Planning • Analyze old application • Map custom solutions to new features • Migrate • Use the Content Migration feature • Post-migration tasks • Check, refine migrated site • Re-brand site • Incrementally migrate new content • Switch over to Microsoft Office SharePoint Server 2007 site

  10. Whitepapers • Planning • Analyzing and Assessing • Microsoft Office SharePoint Server 2007 forCMS developers • API Comparison • SharePoint Migration Center on MSDN

  11. 2007 MicrosoftOffice system Migration Strategy

  12. What Is “Content”?

  13. Migration Profiles • Contains the settings for the migration of a site • CMS ’02 database connection information • Top-level channel to migrate • Site collection to migrate into • By running the profile, content gets migrated to Microsoft Office SharePoint Server 2007 • Don’t need CMS ’02 installed on your Microsoft Office SharePoint Server 2007 farm • One profile for every migration

  14. Common CMS ‘02 Implementations • One CMS ’02 install -> One web site • One CMS ’02 install -> Multiple web sites • Each site in a top level channel • Possibly using host header mapping • Depending on the CMS ’02 structure, your migration profile configuration will change slightly

  15. One Web Site Site Collection

  16. Site Collection A Site Collection B Multiple Web Sites

  17. A Migration Profile

  18. Pre-Migration Analyzer • Microsoft Office SharePoint Server 2007 is a new architecture • Identifies things that need to or should be changed in your CMS 2002 application before migration • Runs automatically as part of migration • Errors and Warnings • Errors: Cause migration to fail until they are changed • Warnings: Migration can proceed but some content may not look like you expect in Microsoft Office SharePoint Server 2007 • Pre-migration analyzer can be run without performing a full migration

  19. Post-Migration Tasks • Test content • Refine content • Adjust navigation • Add custom field controls • Customize Branding • Master pages • Page layouts

  20. Code Migration • Moving from the CMS APIto SharePoint Object Model • No backwards compatibility • We are providing whitepapersto help customers through this

  21. Code MigrationCustom code

  22. Code MigrationCustom placeholders • HTML Placeholders are migrated to HTML Field controls • Custom Placeholders need to be migrated to Field controls • The XML Placeholder isn’t supported • If you are using it, you need to create a custom field control

  23. Code MigrationWorkflow • Microsoft Office SharePoint Server 2007 leverages Windows Workflow Foundation • Several workflows are provided that you can configure or create new workflows • Microsoft Office SharePoint Server 2007 workflows are based on content types and/or sites

  24. Code MigrationMetadata • Channel Properties • Move to a “Property Bag” on the site • Access through API • Posting Properties • Become fields on the page • Only visible in page edit mode

  25. CMS Assessment ToolOverview • Creates an inventory of your application’s use of the CMS Publishing API (PAPI) • Creates an inventory of the CMS Repository • Collects Statistics about the CMS Repository • Pre-Migration Analyzer • Reports are in XML and Microsoft Office Excel

  26. CMS Assessment Tool

  27. CMS Assessment ToolCode analysis • PAPI Inventory • Where in your code you are calling PAPI • Summary of the PAPI calls • Which placeholders are being used on which templates • Workflow hooks

  28. CMS Assessment ToolPre-migration analysis • Executes many of the same tests against the CMS Repository as Microsoft Office SharePoint Server 2007 • The same errors and warning text is used • Identify potential issues before attempting to upgrade

  29. A Re-Branded PostMigration Site

  30. FAQs • Connected Pages • Examine what you were trying to do • Possible solutions include: • Variations • Content Query Web Part • Reusable HTML Fragments • Navigation modifications • Revision History • Not as visual as CMS 2002 • Pages Library and URL • Can change Pages Library name

  31. Best Practices for Current Dev • Update your CMS 2002 application to SP2 • Upgrade to ASP.NET 2.0 • Use Master Pages • Leverage the ASP.NET 2.0 Navigation and Authentication Provider Model • Minimize the number of templates • Minimize your custom placeholder server controls • Plan customizations based on what you know is coming! • Integrated Search • Workflow customizations • Authoring Console • OOB Web Parts • Avoid using Connected Templates/Pages

  32. What You Can Do Now • Download Beta 2 and Migrate your site! • Check out the Migration Center • Assessment Tool • Planning guide • White papers • Learn all about Office SharePoint Server! • E-Learning • SharePoint DVD • Designing Your Microsoft Content Management Server 2002 Solution for Reusability

  33. Additional Community Resources • Web Casts: • Migration Web Cast • Evolution of Web Content Management in Office SharePoint Server • Blogs: • Stefan Gossner • Andrew Connell (MVP) • Spencer Harbar (MVP) • Mark Harrison • Mitch Prince

  34. The 2007 Microsoft Office System Clients. Servers. Solutions. Install Beta 2 today! It’s in your attendee bag Learn more at the Office System TLCDemo Stations / Hands-on-Labs / Chalk-talks Talk Lab Demo Get more informationhttp://www.microsoft.com/office/preview/default.mspxhttp://msdn.microsoft.com/office/

  35. Resources

  36. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related