Microsoft Office SharePoint Server 2007 administrators companion phần 8 pdf

780 Part V Upgrading to Microsoft Office SharePoint Server 2007 Figure 22-12 MCMS Assessment Tool Report workbook Note The MCMS Assessment Tool Report workbook contains macros. Depending upon the configuration of Office Excel, it might or might not be configured to enable macros. If Office Excel is configured to disable mac- ros, they must be enabled prior to loading the reports. To enable macros in Office Excel 2007, got to the Security Warning panel and select Options. In the Security Alert – Macro dialog box, select Enable This Content and click OK. Referring back to Figure 22-12, you can see this Security Warning just above the CMS Assessment Tool Results blue bar. 2. On the MCMS Assessment Tool Report workbook, click the Load Analysis Results button. 3. On the Select Folder With The Assessment Tool Output page, browse to the folder where the reports were saved as specified during the execution of the CMS Assess- ment Tool and then click OK. After you select the folder that contains the generated reports, the MCMS Assessment Tool Report workbook creates a separate worksheet tab for each generated report. To view the reports (as shown in Figure 22-13), click the Menu button on the Main worksheet or select the appropriate worksheet tab at the bottom of the workbook. In the following sections, we’ll give a brief overview of each report that the assessment tool generates. Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 781 Figure 22-13 CMS Assessment Tool Results—navigating the reports Note Figure 22-13 represents only a sample of the available reports that are generated by the CMS Assessment Tool. It is not a complete list of all reports listed in this chapter. Site Summary Report The Site Summary report contains a snapshot of the Content Management Server 2002 Web application project. It contains a list of all the classes, methods, properties, ASP.NET Web pages, Web controls, and assemblies used by the Web application project. This report is helpful in determining the scope of the migration effort when it is time to con- vert the Content Management Server 2002 Web application project to a WCM publishing site. Publishing API Usage Summary Report The Publishing API Usage Summary report contains a list of all the methods the Content Management Server 2002 Web application project calls in the Content Management Server Publishing API. This report is helpful to determine whether the Web application project uses any Content Management Server custom properties by applying a filter to 782 Part V Upgrading to Microsoft Office SharePoint Server 2007 the Class Name column for Posting or Channel and then applying another filter for Cus- tomPropertyCollection or CustomProperties to the PAPI Method Name column. In addition, this report is helpful in determining whether the Web application project contains any custom placeholders by applying a filter to the Class name column for Base- PlaceholderControl and then applying another filter for BasePlaceholderControl to the PAPI Method Name column. Publishing API Class Usage Report The Publishing API Class Usage report contains a list of all the PAPI classes the Content Management Server 2002 Web application project is using. Placeholder Control Usage Report The Placeholder Control Usage report contains a list of all the placeholder controls the Content Management Server 2002 Web application project contains, as well as how many times they are used. This report is helpful in identifying which placeholder controls need to be rewritten as field controls or Web Parts. They will need to be rewritten because custom placeholder controls in Content Management Server 2002 are not compatible with SharePoint Server 2007. User Methods Calling Publishing API Report The User Methods Calling Publishing API report contains a list of the methods that con- tain calls into the Publishing API within the Content Management Server 2002 Web application project. Methods Returning Publishing API Report The Methods Returning Publishing API report contains a list of the methods in the Con- tent Management Server 2002 Web application project that return a Publishing API object or receive one as an argument. Classes with Publishing API Fields Report The Classes with Publishing API Fields report lists all the classes that contain calls into the Publishing API Content Management Server 2002 Web application project. Workflow Event Handling Report The Workflow Event Handling report contains a list of all instances of publishing event handlers in the Content Management Server 2002 Web application project. SharePoint Server 2007 contains a different publishing and workflow engine than what Content Man- agement Server 2002 uses. Event handlers written for Content Management Server 2002 need to be rewritten for SharePoint Server 2007 and Windows Workflow Foundation. Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 783 User Classes with Publishing API Parents Report The User Classes with Publishing API Parents report lists all classes in your Content Man- agement Server 2002 Web application project that are derived from classes in the Pub- lishing API. This report is helpful in identifying any custom placeholder controls or custom Web Author actions contained in the Web application project. To find custom placeholder controls in the Content Management Server 2002 Web application project, apply a filter to the PAPI Class column, limiting it to the following results: ■ BasePlaceholderControl ■ HtmlPlaceholderControl ■ SingleAttachmentPlaceholderControl ■ SingleImagePlaceholderControl To find custom Web Author actions in your Content Management Server 2002 Web application project, filter to the PAPI Class column for the following results: ■ BaseAction ■ BaseNewWindowAction ■ BasePostbackAction Placeholders per Template Report The Placeholders per Template report contains a list of all the placeholder names and controls, as well as the number of times they are used on each template. This report is helpful in determining which templates contain custom placeholders that will need to be rewritten because they are not comparable with SharePoint Server 2007. In addition, this report also helps you identify which templates are using XML placeholders that need to be rewritten for SharePoint Server 2007 because there is no equivalent control for the Content Management Server 2002 XML placeholder control. To find the XML place- holder controls used in the Content Management Server 2002 Web application project, apply a filter on the Placeholder Control Type column for Microsoft.ContentManage- ment.Publishing.Extensions.XmlPlaceholder. Template vs. Placeholder Control Report The Template vs. Placeholder Control report contains a list of all the templates in the Content Management Server 2002 Web application project and the placeholder controls found in each template. This report helps to identify templates that do not contain any placeholders or templates that are used only for summary links. 784 Part V Upgrading to Microsoft Office SharePoint Server 2007 Web Author Consoles Report The Web Author Consoles report contains a list of all custom controls and templates in the Content Management Server 2002 Web application project that implement the Web Author console. This report helps in identifying whether the Web application project has implemented multiple instances of the Web Author console. Http Modules Report The Http Modules report lists all the Http modules the Content Management Server 2002 Web application project is using as they are listed in the project’s web.config file. Many Content Management Server 2002 Web sites use custom Http modules to improve site performance, implement SSL support, and provide URL rewriting. Because these cus- tom Http modules are used by the Content Management Server 2002 Publishing API, they have to be rewritten to use the new object model in SharePoint Server 2007. Output Cache Settings Report The Output Cache Settings report contains a list of all templates in your Content Man- agement Server 2002 Web application project that are configured to use ASP.NET output caching. To find the templates using output caching, apply a filter for non-blank values on the following columns: ■ Duration ■ Location ■ VaryByHeader ■ VaryByParam ■ VaryByCustom SharePoint Server 2007 includes robust support for caching but does not permit setting the OutputCache attribute in the Page directive of each page layout. Instead, cache settings are managed using the browser-based administration tools. Because of this, any cache set- tings defined at the template level need to be removed when migrating the Content Man- agement Server 2002 Web site to SharePoint Server 2007. Project Line Count Report The Project Line Count report contains the number of lines of code in the Content Man- agement Server 2002 Web application project. This report is helpful in determining the scope of the code-migration task. Keep in mind that not all custom code will need to be rewritten, as many elements that required custom code in Content Management Server 2002 are not included in SharePoint Server 2007. Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 785 ASP.NET Control Usage Report The ASP.NET Control Usage report contains a list of all the custom controls used in the Content Management Server 2002 Web application project. This report is helpful in determining the Content Management Server 2002–specific controls that will need to be rewritten for SharePoint Server 2007. A sample ASP.NET Control Usage report, generated by running the CMS Assessment Tool against the Woodgrove Bank sample Content Management Server 2002 site, is shown in Figure 22-14. Figure 22-14 An ASP.NET Control Usage report CMS Repository Size Report The CMS Repository Size report contains the total number of channels, postings, tem- plate galleries, templates, resource galleries, and resources in your Content Management Server 2002 Content Repository. A sample CMS Repository Size report, generated by running the CMS Assessment Tool against the Woodgrove Bank sample Content Management Server 2002 site, is shown in Figure 22-15. 786 Part V Upgrading to Microsoft Office SharePoint Server 2007 Figure 22-15 A CMS Repository Size report Channel Information Report The Channel Information report contains a list of all the channels in the Content Man- agement Server 2002 Web site and many of the properties for each channel. This report is helpful in determining which channels use channel-rendering scripts. Gallery Information Report The Gallery Information report lists all the template galleries and resource galleries in the Content Management Server 2002 Content Repository, including the number of items in each gallery. Template Information Report The Template Information report lists all the templates in the Content Management Server 2002 Content Repository, including the ASP.NET file associated with the template and the number of postings dependent upon the template. Template Property Definition Report The Template Property Definition report lists all the custom properties for each template in the Content Management Server 2002 Content Repository. Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 787 Placeholder Definition Usage Report The Placeholder Definition Usage report lists all the placeholder definitions used in the Content Management Server 2002 Web application project, as well as the number of times each one is used throughout the project. Posting Information Report The Posting Information report lists all the postings in the Content Management Server 2002 Content Repository and the major properties of each posting. This report helps identify any connected postings in the Content Management Server 2002 Content Repos- itory, as these will need to be addressed because SharePoint Server 2007 does not sup- port connected postings. Posting Custom Properties Report The Posting Custom Properties report lists all the custom properties for each posting in the Content Management Server 2002 Content Repository. Duplicate Posting Names Report The Duplicate Posting Names report lists all postings that have duplicate names. Share- Point Server 2007 does not support two postings with the same name in the same site, so this issue needs to be addressed before migrating the content from the Content Manage- ment Server 2002 Content Repository to SharePoint Server 2007. Site Analyzer Results Report The Site Analyzer Results report lists information about the hardware the Content Man- agement Server 2002 Web site is hosted on, as well as various metrics for the Content Repository, such as user and role information and metrics on Content Management Server 2002 content not covered in other reports. Pre-Migration Analyzer Results Report The Pre-Migration Analyzer Results report identifies issues that might arise during migra- tion from Content Management Server 2002 to SharePoint Server 2007. Potential issues include broken links, checked-out items, depreciated placeholders, invalid HTML objects, and objects with invalid names. This report produces the same results generated when executing the analysis step on a migration profile in the SharePoint Central Administration Web site. 788 Part V Upgrading to Microsoft Office SharePoint Server 2007 Summary of Migration Steps You will successfully migrate a Content Management Server 2002 Web site to SharePoint Server by following four unique and very important stages: planning, preparing, upgrad- ing, and testing/deployment. Each stage builds on the preceding stage and makes the next stage as streamlined and easy as possible. Best Practices The primary goal for all Content Management Server 2002 to SharePoint Server 2007 migration projects should be to migrate your site with all existing functionality before attempting to add features, add capabilities, or implement customizations. Planning the Migration In this first stage in the migration of a Content Management Server 2002 Web site to SharePoint Server 2007, the goal is to develop a solid plan for the complete migration pro- cess. It is here where any potential problems are identified, and those that can be addressed ahead of time are resolved or mitigated. The following tasks will assist in com- posing a plan for the migration. Run the CMS Assessment Tool Obtaining a complete and comprehensive report form the CMS Assessment Tool should be the first thing you do during the planning stage. The report will help you to under- stand the scope of the migration project by using its many analyses. It should be fairly easy to identify trouble areas—such as heavily used templates and custom placeholders that need to be rewritten as field controls—by analyzing the various reports generated by the CMS Assessment Tool. Some of the issues identified using the CMS Assessment Tools can be addressed prior to migration—such as postings with duplicate names in the same channel, which is not supported in SharePoint Server 2007—making the process of upgrading less error prone. Stop Current Development and Determine Site Migration Order If the Content Management Server 2002 Web site that is the subject of the migration project is currently under active development, this should stop while the migration pro- cess is determined and a plan is put into place. Otherwise, actions such as changing tem- plate definitions and rearranging channel hierarchies could have a dramatic effect on the scope of work and analysis the migration plan is based on. Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 789 Run the SharePoint Server 2007 Content Migration Tool The last step in planning for a migration of a Content Management Server 2002 Web site to SharePoint Server 2007 is to create a content migration profile in SharePoint Central Administration and run it against your Content Management Server 2002 Web site. The content migration task in SharePoint Server 2007 allows for multiple content migrations following an initial migration. This also will help in identifying any content issues that might arise during the migration process. If any errors are found, they should be addressed and resolved prior to migration. Preparing for Migration The second stage in the migration of a Content Management Server 2002 Web site to SharePoint Server 2007 involves updating your environment to the latest available ver- sion of Content Management Server 2002. In addition, if time permits, you can perform certain development tasks on the Content Management Server Web application solution that could reduce the amount of time required during the code-migration phase of the process. One example of this is if any business logic is included in the code behind of a template file in the Content Management Server Web application that contains calls to objects in the Publishing API, developers could refactor this code to put the Publishing API–specific calls into an abstraction layer that is separate from the template file. Upgrade Content Management Server 2001 or 2002 to Content Management Server 2002 Service Pack 2 To migrate to SharePoint Server 2007, the Content Management Server Web site must be running the latest version of Content Management Server: Content Management Server 2002 Service Pack 2. If your Web site is running Content Management Server 2001, the server must first be upgraded to Content Management Server 2002 and then patched with Service Pack 1a, followed by Service Pack 2. Note Content Management Server 2002 Service Pack 1a is cumulative, includ- ing Service Pack 1. However, Content Management Server 2002 Service Pack 2 is not cumulative, and therefore, Service Pack 1a must be installed prior to installing Service Pack 2. Upgrade Content Management Server Web Site Application to ASP.NET 2.0 If the migration to SharePoint Server 2007 is not planned for the immediate future or active development is still being performed on the Content Management Server Web site, and the site has not been updated to leverage some of the new features provided in ASP.NET 2.0 (for example, Content Management Server 2002 Service Pack 2 adds [...]... you need to upgrade from Microsoft Office SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007, refer to Chapter 24, “Upgrading from Microsoft SharePoint Portal Server 2003.” Before you upgrade, it’s best to read the relevant material Fortunately, Microsoft has published a body of good, detailed information concerning the topic of upgrading your Windows SharePoint Services 2.0 installation,... to re-create your Windows SharePoint Services 2.0 environment See the Microsoft TechNet article, “Backing Up and Restoring Web Sites Created with Windows SharePoint Services,” at http://www .microsoft. com/technet/prodtechnol /office/ office2003/maintain/bureswss.mspx 3 Install Windows SharePoint Services 2.0 SP2 80 3 80 4 Part V Upgrading to Microsoft Office SharePoint Server 2007 More Info For more information... installing Windows SharePoint Services 2.0 SP2, see http:/ /office .microsoft. com/en-us/assistance /HA01160 788 1033.aspx and Microsoft Knowledge Base article number 87 53 58, “You must update all the Web servers that are running Windows SharePoint Services in a Web farm,” found at http://support .microsoft. com /default.aspx/kb /87 53 58 This Knowledge Base article lists the version numbers of Windows SharePoint Services... between the Content Management Server 2002 Web application project and SharePoint Server 2007 The most significant change is that the Content Management Server 2002 Publishing API is not compatible with the SharePoint Server 2007 object model This incompatibility typically requires a significant amount of manual cod- 793 794 Part V Upgrading to Microsoft Office SharePoint Server 2007 ing and rewriting of... issues that might arise during the final content migration Chapter 22 Migrating from Content Management Server 2002 to SharePoint Server 2007 Migrating Content Management Server 2002 to SharePoint Server 2007 Now that the migration of a Content Management Server 2002 Web site to SharePoint Server 2007 has been planned and prepared, the next step is to execute the migration As previously covered in this... Install Windows SharePoint Services 3.0 binaries ■ Task 2: Run the prescan tool ■ Task 3: Run the SharePoint Products And Technologies Configuration Wizard ■ Task 4: Upgrade and migrate your Windows SharePoint Services 2.0 Web sites 80 7 80 8 Part V Upgrading to Microsoft Office SharePoint Server 2007 If you want to use the content database migration upgrade approach, you should install Windows SharePoint. .. in Figure 23-6 Chapter 23 Upgrading from Microsoft Windows SharePoint Services 2.0 Figure 23-6 Preupgrade report _Log.txt file The _Summary.xml file contains similar information, as shown in Figure 23-7 Figure 23-7 Preupgrade report _Summary.xml file 81 3 81 4 Part V Upgrading to Microsoft Office SharePoint Server 2007 Important Do not add any servers to your server farm after this point in the upgrade... should read Here are a few good starting points: ■ Microsoft Windows SharePoint Services in Windows Server 2003 TechCenter found at http://www .microsoft. com/technet/windowsserver /sharepoint/ default.mspx ■ Deployment for Windows SharePoint Services 3.0 Technology found at http:// technet2 .microsoft. com /Office/ en-us/librar y/b9490b1a-45de-45fd-9f4c754dab1 383 e61033.mspx Whichever upgrade option you choose,... the Windows SharePoint Services Central Administration Web page, under the Virtual Server Configuration section, click Configure Virtual Server Settings c The Virtual Server List is displayed Check that each virtual server is at version 6.0.2.65 68 or above, as shown in Figure 23-1 Figure 23-1 Windows SharePoint Services 2.0 Virtual Server List Chapter 23 Upgrading from Microsoft Windows SharePoint Services... analyze your current Windows SharePoint Services implementation You can use SPSiteManager (found at http://www.codeplex.com/Release /ProjectReleases.aspx?ProjectName=SPUS on the Releases tab) and SPReport (http://www.gotdotnet.com/workspaces /workspace.aspx?id=8eb2bfa3-aac8-4b5a-b3a2-5accb29970eb) Once the product is 80 5 80 6 Part V Upgrading to Microsoft Office SharePoint Server 2007 released to manufacturing, . Management Server 2002 to SharePoint Server 2007 789 Run the SharePoint Server 2007 Content Migration Tool The last step in planning for a migration of a Content Management Server 2002 Web site to SharePoint. Management Server 2002 to SharePoint Server 2007 791 Migrating Content Management Server 2002 to SharePoint Server 2007 Now that the migration of a Content Management Server 2002 Web site to SharePoint Server. upgrade from Microsoft Office SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007, refer to Chapter 24, “Upgrading from Microsoft SharePoint Portal Server 2003.” Before you