Microsoft Office SharePoint Server 2007 administrators companion phần 2 ppt

78 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 2007 Single-Server Deployment In a single-server deployment scenario (shown in Figure 3-7), a single server services all the client’s needs and offers all the needed services to the network. This topology also uses the SQL Express database engine and installs it on this server. A single server is assigned all the farm roles, including the following ones: ■ Web front-end The role to which users always connect to access all farm services, including search and indexing, Excel Calculation Services, collaboration, portals, and more ■ Query server The role that allows users to query the index to find content ■ Search server The role that crawls and indexes content from content sources ■ Excel Calculation The role that hosts complex queries for end-user Excel spread- sheets and helps users maintain persistent connections to data points ■ Forms Server The role that offers InfoPath forms to the users on your network ■ Web content management The role that allows staging and publishing of Web content Single-server roles are best suited for environments with a small user base or for testing labs. Figure 3-7 Single-server topology Small Server Farms A small-farm environment (shown in Figure 3-8) is a two-tiered environment in which one server is running SQL Server and the other server is running all the roles in the SharePoint farm. If performance becomes an issue, you can always add another WFE server to the farm. If data redundancy becomes an issue, you can always cluster your SQL servers. If both increased performance and data redundancy are needed, you can add servers to your SharePoint farm as needed and cluster your SQL Server server. Both actions will help ensure that users can access their data quickly and easily. Front End Server Application Server Database User Requests Chapter 3 Design Considerations and Deployment 79 Figure 3-8 Small-farm topology Medium Server Farms We move to a three-tier topology with a medium server farm. This topology places the application services —such as search, query, Excel calculation, Office Forms Server and other services —on the middle tier (as shown in Figure 3-9). In this topology, two servers are dedicated to being WFE servers: one application server in the middle tier, and a clus- tered SQL Server deployment for data redundancy. The most likely reason you’d add a second server to the middle tier is to isolate the search function on a single server, because that activity is very processor and RAM intensive. Figure 3-9 Medium server farm topology Web Front-End Server Application Server User Requests Dedicated SQL Server Web Front-End Server User Requests Application Serve r 80 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 2007 In addition, by modifying this topology and adding another server to the middle tier, you can achieve maximum redundancy with the fewest number of servers, which is six. (See Figure 3-10.) Each tier has two servers offering the same services, thereby giving you the greatest opportunity for redundancy with the fewest number of servers. Most environ- ments for small and medium servers will be similar to what I’ve described in this section. Figure 3-10 Medium server farm topology with redundancy Large Server Farms A large farm merely builds on the medium farm topology and allows us to scale out serv- ers for any combination of services that are needed. Figure 3-11 offers one illustration of a large server farm for SharePoint Server 2007. Note that there is redundancy at each tier and for each service. Notice also that you’re writing content to multiple SQL clusters. Finally, notice that as you need to, you can scale out any tier and service you need with additional servers. The only servers that need NLB are the WFE servers. All other servers merely have their services started or stopped and SharePoint Server 2007 does the rest to ensure they are all utilized properly. Web Front-End Server User Requests Application Servers Clustered or Mirrored SQL Server Chapter 3 Design Considerations and Deployment 81 Figure 3-11 Large server farm topology Multiple Farms At times, you will find that multiple SharePoint Server 2007 server farms are required. (Figure 3-12 shows content deployment in a multiple-farm environment.) As an example, software development requires development, test, and production environments. Share- Point Server 2007 perfectly meets this need by using multiple farms, which allows devel- opment and test environments to be on intranets and schedules the publishing of production content to a screened subnet. Geographically dispersed organizations and implementations with unique legal and regulatory requirements will require multiple farms as well. Network Load Balanced Web Front-End Servers Network Load Balanced Application Servers SQL Server Clusters Configuration Database (one per farm) Profile Database (one per Portal) Service Database (one per Portal) Indexing Search Excel Calculation Services Project Server Content Database 1 Project Server Database Content Database 2 82 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 2007 Figure 3-12 Content deployment in a multifarm environment Using Interfarm Shared Services If you have several SharePoint Server 2007 server farms, you should leverage SharePoint Server 2007 capabilities of interfarm shared services. Interfarm shared services reduce the administrative and operating overhead by limiting custom Shared Services develop- ment to one server farm. A single Business Data Catalog connector, a single MySites namespace, and centralized search and indexing are the most common reasons for a uni- fied Shared Services implementation. There are some limitations to be aware of when designing this model, the most obvious being bandwidth limitations. Interfarm shared services are generally not supported over WAN links. Robust search and indexing, Busi- ness Data Catalog, and My Sites can require huge amounts of expensive bandwidth. However, with the advent of large, high-speed optical carrier (OC) backbones, an excep- tion might be made in some large organizations. Refer to Chapter 18, “Administrating Shared Services Providers,” for information on integrating interfarm and intrafarm Shared Services. Note To avoid My Site URL collisions between multiple domains, be sure to select Domain and User Name when defining Site Naming Format. Internet Layer 1 Network Load- Balanced Front-End Web Servers Read-Only Development Cluster Network Load- Balanced Front-End Web Servers Layer 2 Application Servers and Database Servers Router Content Deployment Search Server SQL Server Production Cluster Index Server App Server (other apps) SQL Server Chapter 3 Design Considerations and Deployment 83 Summary This chapter presented you with an overview of the considerations involved in designing and deploying SharePoint Server 2007. Don’t let the many features intimidate you—these are easily deployed with research, planning, testing, and peer reviews. Remember that SharePoint Server 2007 is very flexible, so you can change your mind if your original deployment isn’t an exact fit. If you are in a small IT department or you are the only administrator, consider consulting with local technology users groups or the numerous newsgroups available for SharePoint Server 2007. There are many Microsoft MVPs (Most Valuable Professionals) and others with extensive experience ready to help you. 85 Chapter 4 Multilingual Planning, Deployment, and Maintenance Multilingual Support in Windows SharePoint Services 3.0 and SharePoint Server 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Selecting a Product Installation Language . . . . . . . . . . . . . . . . . . . . . . . . . 87 Creating a Variation Hierarchy of Web Sites . . . . . . . . . . . . . . . . . . . . . . . . 91 Incorporating Variation Concepts into Planning . . . . . . . . . . . . . . . . . . . . 94 Planning Variation Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Managing Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Deploying Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 This chapter focuses on the new capabilities of Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 to host sites in different languages and present content in multiple languages within the same site collections. This new func- tionality and the flexibility of multilingual options presents new planning decisions prior to deployment, new deployment options, and new maintenance concerns. You’ll find an in-depth discussion of the functionality of the Variation feature provided by Office Share- Point Server 2007 and how variations extend beyond the more common application of synchronizing content in multiple languages. This chapter helps you understand the planning issues for content translation encoun- tered in a multilingual scenario and the solutions provided by the translation workflow and variation packaging. It includes a discussion of the limitations or constraints in the variation processes, including issues with some Web Parts. The tools provided to assist in managing the process of manually translating content are also covered in this chapter, with particular focus on planning issues. 86 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 2007 Multilingual Support in Windows SharePoint Services 3.0 and SharePoint Server 2007 Windows SharePoint Services 3.0 supports hosting site collections, sites, and content in multiple languages on the same servers across your farm. This support is an enormous step forward from previous versions, which required the product to be installed in a spe- cific language version that could host content only in that single language. SharePoint Server 2007 extends this multilingual support with several features that sim- plify the implementation and maintenance for the administrators and the utilization for the users. Multilingual support does, however, create myriad planning decisions that should be addressed prior to implementing your farm. These decision points are intro- duced throughout the chapter in the discussions of the technology itself. Preparing Front-End Servers for Multiple Languages Before you install language packs on SharePoint farm servers, you must install the neces- sary regional and language files on at least your front-end Web servers. Because roles within your farm might change, installing and configuring these regional files on all members of your farm could prevent problems later on. All members of the farm should be configured with the same options, including having all the same regional and lan- guage files installed. Regional and language files are used by the operating system to provide support for dis- playing and entering text in multiple languages. These files include keyboard files, Input Method Editors (IMEs), TrueType font files, bitmap font files, codepage translation tables, national language support (.nls) files, and script engines for rendering complex scripts. Most language files are installed by default on Windows Server 2003; however, you must install language files for East Asian languages and languages that use complex script or require right-to-left orientations. The East Asian languages include Chinese, Jap- anese, and Korean; the complex script and right-to-left-oriented languages include Ara- bic, Armenian, Georgian, Hebrew, the Indic languages, Thai, and Vietnamese. Microsoft recommends that you install only the language files you need. The East Asian files require about 230 megabytes (MB) of hard disk space. The complex script and right- to-left languages do not use much disk space, but installing either set of files might cause some slowdown in performance when entering text. Note You must be an administrator on the computer to install these language files. Once the language files are installed, the languages are available to all users of the computer. You need your Windows Server 2003 product disc to perform this procedure. Alternatively, you need to know the location of a shared folder that contains your operating system installation files. Restart your computer after supplemental language files are installed. Chapter 4 Multilingual Planning, Deployment, and Maintenance 87 Installing Additional Language Files To install additional language files, perform the following steps: 1. On your server, in Control Panel, select Regional And Language Options. 2. In the Regional And Language Options dialog box, click the Languages tab. In the Supplemental Language Support section, do one or both of the following: a. Click Install Files For Complex Script And Right-To-Left Languages (Includ- ing Thai) if you want to install language files for Arabic, Armenian, Georgian, Hebrew, the Indic languages, Thai, and Vietnamese. b. Click Install Files For East Asian Languages if you want to install language files for Chinese, Japanese, and Korean. 3. When prompted, insert your Windows Server 2003 product disc or provide the location of your Windows Server 2003 installation files. 4. When prompted to restart your computer, click Yes. As this process indicates, the language files must be installed in the server operating sys- tem to be available to the SharePoint Technologies platform. Selecting a Product Installation Language After you install the necessary language files on your servers, you need to install Win- dows SharePoint Services 3.0 or SharePoint Server 2007 and run the SharePoint Products And Technologies Configuration Wizard. Your first planning decision is the language you want to use for administering your farm. This will always be the language version of the product you install on all members of your farm. Only one installation language is supported per farm. All members of the farm must have the same language version of the product installed. To change the language used for administering the farm requires removing and re-installing the product on all members of the farm. The product language does not have to be the same language as that of the operating sys- tem, but it probably will be in most cases. However, if your server administrators prefer English but your SharePoint farm administrators prefer a different language, install the appropriate language version of the operating system and add the necessary regional and language files on the server before installing SharePoint in the desired language. The operating system must provide the appropriate language support for the SharePoint product or even the installation dialog boxes cannot be displayed. [...]... default.aspx Hide variation sites in navigation 95 96 Part I ■ Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Neither Windows SharePoint Services 3.0 nor SharePoint Server 20 07 provide a translation service to translate text from one language to another However, SharePoint Server 20 07 does provide tools to assist you in managing the translation process See the “Managing Translations”... page content Neither Windows SharePoint Services 3.0 nor SharePoint Server 20 07 provide a translation service to translate text from one language to another Your organization might have translation capabilities in-house or need to engage the services of an external provider SharePoint Server 20 07 has addressed both options Local Translation Management Tools SharePoint Server 20 07 provides three translation... chapter Microsoft Content Management Server had the capability of linking different “channels” (sites in SharePoint Server 20 07) so that when a page was created in the source and approved, a corresponding page was created in the target with the same content but using a different template The SharePoint Server 20 07 Variation feature extends and enhances that concept With Content Management Server channels,... SharePoint Server 20 07 Variation feature extends and enhances that concept With Content Management Server channels, the user had to go to 91 92 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 the appropriate site With SharePoint Server 20 07 variation hierarchies, all users can go to the same root site and be redirected to the appropriate site with no user interaction... multinational deployments where a single server farm supports people in several different locations or in situations where sites and Web pages must be duplicated or hosted in one or more languages Language packs are also specific to Windows SharePoint Services 3.0 or SharePoint Server 20 07 because of the number of extra templates included with SharePoint Server 20 07 Table 4-1 lists the product language... and then click SharePoint Products And Technologies Configuration Wizard 89 90 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 2 On the Welcome To SharePoint Products And Technologies page, click Next 3 Click Yes in the warning dialog box that appears notifying you that some services might need to be restarted during configuration 4 On the Modify Server Farm Settings... Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Understanding Language Template Packs Language template packs allow site administrators to create SharePoint sites and site collections in multiple languages without requiring separate installations of Windows SharePoint Services 3.0 Language packs are installed on your front-end Web servers and contain language-specific... Content And Structure 2 The shortcut menu of the published object in the source variation contains the option to initiate a new variation as shown in Figure 4 -2 For a site, select New, and then select Site Variation For a page, select New Page Variation 97 98 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Site Variation selection Figure 4 -2 Manually initiating... until you fill out the required profile properties for the document 1 In your Translation Management Library on the Upload menu, click Upload Document 111 1 12 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 2 In the Upload Document section, click Browse to locate the document you want, and then click Open and then click OK 3 On the properties page for the document,... Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Removing Redirection Functionality To remove the redirection functionality, complete the following steps: 1 In Internet Explorer, enter the full URL for the root site including the name of the welcome page file in the URL Normally, the Welcome page would be default.aspx 2 From the Site Actions page, choose Site Settings, . Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Multilingual Support in Windows SharePoint Services 3.0 and SharePoint Server 20 07 Windows SharePoint Services 3.0 supports. Calculation Services Project Server Content Database 1 Project Server Database Content Database 2 82 Part I Planning Your Deployment and Installing Microsoft Office SharePoint Server 20 07 Figure 3- 12 Content deployment. Your Deployment and Installing Microsoft Office SharePoint Server 20 07 ■ No built-in translation tool Neither Windows SharePoint Services 3.0 nor Share- Point Server 20 07 provide a translation service