What is the Solution Accelerator for intranets? This version of the new content document overview Overview of other resource issues Overview Business Questions Collaboration Information Discovery Personalized Application Integration Architecture Custom Challenge Architecture Development Resource Assessment Suggestive Hardware Selection Solution Support Enterprise Internal Network Regulatory Solution Solution Overview Creates Enterprise Interior required network products SharePoint Portal Server Windows SharePoint Services Microsoft Office system Windows Server 2003 and Internet Information Services 6.0 solution Overview value Proposition solution Accelerator for Intranets logical concept of shared infrastructure solution development architecture development resource assessment recommended hardware solution of choice Service Portal Workspace Regional Medium Server Field Large Serve Structure Subtock Reference Logical Architecture Typical logical architecture solution Physical architecture High availability High performance Easy to operate Easy to grow Better Physical architecture growth options Growth to large farms Add a dedicated Windows SharePoint Services Server Support Problem Solutions Service Advisor Service Preferred Support Services
introduction
Welcome to Microsoft® Solution Accelerator for intranets (Microsoft® Solution Accelerator for Enterprise Internal Network). This accelerator is based on the Microsoft Solution for Intranets (MSI) version 1.5, which is based on Microsoft Office SharePointTM Portal Server 2003, Microsoft Office System, and Microsoft Windows ServerTM 2003, introduces a flexible and highly available internal network architecture.
The goal of Solution Accelerator for intranets is that helping partners and corporate customers quickly build enabled internal network solutions that provide corporate search, document management, web-based team collaboration and integrated with Microsoft Office System.
What is SOLUTION Accelerator for intranets?
Solution Accelerator for intranets is a set of document collections that provides specifications for design, deployment, operation, and growth of internal network solutions with high availability, and guidance for strict testing and support services. Ways and methods. In the process of developing such a solution, accelerator documents can solve those problems that are not discussed in the product documentation, such as service ready planning, resource requirements, and capacity planning. Similar monitoring, backup and recovery. Contents such as growth planning and disaster recovery are also involved.
In addition to how to intend to increase capacity and enhance power, Solution Accelerator for intranets add value to users by giving a basic server configuration with high availability. Provide performance and capacity numbers by providing basic configuration and "lateral telescopic" configuration, Solution Accelerator for Intranets helps partners quantifying a physical system architecture.
Finally, the Standardization Architecture described by Solution Accelerator for intranets has been strictly tested by Microsoft and is actually running and verified by other partners and users while fully enjoying Microsoft's product support services.
New content of this version
SharePoint Portal Server 2003 is different from SharePoint Portal Server 2001: it provides a very flexible deployment option. The shared service features enable a distributed server topology, and better performance and scalable capability make the product to meet the collaboration, personalization and integration of super-large organizations. Solution Accelerator for intranets provides guidance and assistance for these new server topologies. In addition, this release also introduces Microsoft Windows® SharePoint Services close cooperation with Microsoft Office 2003, as well as the development direction of team sites, My Sites, document workspaces, and conference workspaces. This version discusses the planning methods and performance advantages of these new features in detail.
Document overview
Solution Accelerator for intranets document is divided into 4 independent guides, each guide focuses on a specific topic and access group objects. The Solution Accelerator for Intranets Overview Guide introduces the accelerator. The Solution Accelerator For Intranets Planning Guide summarizes the design process of architecture and applications. The Solution Accelerator For Intranets Build and Test Guide describes the construction and verification methods of the architecture. The Solution Accelerator for Intranets Operation Guide introduces the process of the final solution. The following list details these 4 guides.
Solution Accelerator for intranets Overview: This guide describes the concept, targets, and structures of the Solution Accelerator for intranets, and overviews from higher levels from higher levels. Overview Guide also summarizes the target business situation for documents, using the SHAREPOINT product family can be assembled and discussed on the final architecture. Solution Accelerator For Intranets Planning Guide: Describes the design decisions involved in the process of creating an application presentation based on the Solution Accelerator for Intranets architecture. Planning Guide focuses on demand collection, risk analysis and determination of customer risks and definitions. It details the decision-making that deployment issues and the required decisions, and provides some work forms to collect decisions when building and deploying solutions. In addition, this guide also discusses hardware requirements and the situation in which retractable. Solution Accelerator For intranets Build and Test Guide: To build and deploy solutions for users, provide a detailed guidance and distribution process. The construction and test guidelines provide hardware installation guidance and provide help for software products installation and configuration. Solution Accelerator For intranets Operation Guide: Help you understand how to manage and operate newly configured environments. Operation Guide provides guidance for the backup, recovery, monitoring, and growth of the system. In addition, it also includes details on Microsoft SQL ServerTM failover clusters and Windows network load balancing.
Other resources
Solution Accelerator for Intranets does not mean that it can replace the product documentation of SharePoint Portal Server or Windows SharePoint Services. Solution Accelerator for intranets provides a test method for testing, which is a useful supplement to these product documents. For more information, see:
SharePoint Portal Server online documentation: http://www.microsoft.com/sharepoint/server/techinfo/productdoc/default.asp SharePoint Portal Server Product Overview http://www.microsoft.com/sharepoint/server/evaluation/overview. /Technologies.asp. SharePoint Portal Server Resource Kit: http://www.microsoft.com/sharepoint/server/techinfo/reskit/default.asp. http://www.microsoft.com/sharepoint/server/evaluation/ CaseStudies / Default.asp. For more information on Microsoft Accelerators and Internal Network Solutions, see:
Http://www.microsoft.com/sharepoint/intranets/ http://www.microsoft.com/sharepoint/community/default.asp http://www.microsoft.com/business/solutions/ http: // www . Microsoft.com / Solutions / MSI / http://www.microsoft.com/solutions/msib/ http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/intranet/ DEFAULT.ASP
Problem overview
Today's companies face many information questions, in order to solve these problems, partners will cost a lot of time and resource creation and verify the effectiveness of their custom architecture. The content of this section summarizes these business issues that need to be resolved through internal network solutions and introduce the technical issues needed to implement the architecture of the descriptive guide (such as Microsoft® Solution Accelerator for Intranets).
Business problem
The efficiency of the information worker can be used to quickly find relevant information through him (or her), whether it can effectively achieve team collaboration and whether it can provide information to others. In general, companies and organizations will encounter many knowledge sharing issues that prevent information flow. These issues are logically speaking to collaborative issues, information discovery issues, personalized problems, and application integration issues.
cooperation
In many organizations, the only IT infrastructure used to support teamwork is an enterprise email system. Email-based collaboration activities means that the inbox, confusing document version control, one-time collaboration process, and unnecessary high communication fees. Useful collaborative tools (such as trail forums and surveys) have not been integrated with the management process of the document. Employees often need to search for an archived email folder to find information, then send a revised document multiple times by email. Document management systems that have not yet developed mature often hinder the process of collaboration because it is difficult to use. The information between team members is blocked due to the difficulty of publishing and revising shared documents.
Information discovery
Enterprise knowledge information is generally stored in various heterogeneous systems within the organization. It exists in a highly structured database, and in the organization's shared document folder. It is also saved in Customer Relationship Management System (CRM) or Enterprise Resource Planning (ERP) application. Customized applications and file servers and web servers. Finding information with a lookup or navigable interface is a challenge for companies, especially when there are different data stores (often incompatible) architecture. Collecting this information is very difficult, and more difficult is more difficult in consecutive and repeatable ways. Simple web portals will not make content more to browse and search. Simple search software lacks some advanced features, such as adaptive protocol handling and search results subscriptions. The department-level portal site for bringing data is sometimes too customized and complex, and it is difficult to take advantage of users and other departments of the entire enterprise. personalise
As the company's knowledge is growing, employees are increasingly difficult to find the information they need, and this information is represented in an intuitive manner. The information presented on the home page of the enterprise portal and department-level portal is generally some of the versatile content, which is forced to access multiple pages to see content for specific roles and users. Some sources of information, such as document libraries and forums with valuable value only when users directly obtain content change notifications. However, if there is no good notification management interface, the user will flood unable to get out of the information. Simple personalized solutions generally have forgotten the establishment of a close integration with email and schedule software.
Application integration
Business processes utilize various software platforms and applications. Employee strive to integrate these systems to access multiple applications and manual collection data. Organization has discovered that they don't make full use of funds put in these core applications, and the application's unreasonable and complexity often become the main stumbling block of the company.
Custom challenge of architecture
Microsoft SharePointTM Portal Server is an enterprise-class software platform to solve all the problems mentioned above. It has a well-designed function collection that has a continuous implementation, but because each user has a unique demand, it is also necessary for Microsoft partners to complete this "last mile" approach. Naturally, partners want to create a standardized service to achieve a relaxed re-deployment and support process. In general, this requires a benchmark descriptive architecture to form the core of each solution so that partners can take advantage of all repetitive labor to meet all the needs of customers.
Unfortunately, partners spend a lot of time and resources to create and verify their own custom architecture, not focusing on their customers. At some point, partners must invest in an investment when creating a service, and we will introduce below.
Architecture development
Creating a flexible and scalable physical server architecture is a challenging job. If you want to build high-quality solutions, you will be essential for a deep product knowledge and rich on-site experience. If you do not first implement an experimental project or an early adopter program to get true data from it, then the architecture we recommend will only be talking on paper. Software developers generally do not support users using non-standard topology to configure servers, and may not be able to use public domain faulty methods. This accelerator provides a test and scalable architecture that meets the needs of various size-sized enterprises and organizations.
If you use this accelerator, the user's project budget will be mainly used for the development of general collaboration products to implement a customized architecture, rather than developing functionality that meets user needs.
Resource assessment advice
In order to accurately determine the performance characteristics of the client / server application (such as an enterprise internal network), a wide range of performance testing is required. In order to build a large-capacity farm, the practical hardware input is required. In addition, the resources and the required skills needed are also very considerable. For some partners, the price of a single list is the price of the enterprise load test software. It is unbearable. Hardware selection
The hardware configuration of different vendors may have a wide variety of differences in performance and flexibility. Resource assessment recommendations and hardware selection is closely related, so if you do not use hardware that matches the user's corporate standard, it may not be able to reach a predetermined target capacity.
Solution support
If there is no standard physical and logical architecture, software vendors are difficult to provide support services, especially when customized code is used in partner solutions. The development of custom architecture generally requires partner design and implementation of a support plan. In general, this requires training and maintenance of a full-time support team.
Normative architecture of enterprise internal network
Solution Accelerator for intranets is a collection of normative documents that have been carefully tested to provide a good start to partner design with high availability of enterprise network solutions. The accelerator is developed under the SharePoint Portal Server product team, Microsoft Windows® SharePoint Services product team, Microsoft Product Support Services, and internal test users. Its design goal is to help partners use Microsoft software products to create high-quality solution products with less funds in less time.
Solution overview
This chapter describes some Microsoft product suits that will be used when using Microsoft® Solution Accelerator for Intranets to create a successful enterprise internal network solution, discuss the value positioning of this normative architecture of Microsoft test, and show us the first time. Logic and physical design.
Create products needed for enterprise internal networks
Microsoft® SharePointTM Portal Server 2003 is the core of the Solution Accelerator for intranets. When creating an attractive and practical internal network, many Microsoft products and technologies will be used, please refer to the following details.
SharePoint Portal Server
SharePoint Portal Server 2003 provides integration, collaboration, and customization capabilities, which helps people, teams and knowledge close together. SharePoint Portal Server 2003 helps you create a corporate portal to provide a central location for information, documents, applications, and personnel access, management, sharing, and interactions. Through the collection, organization and search of people, teams and information, the portal promotes end-to-end collaboration. The user can quickly find the desired information by customizing and personalizing the content and layout of the portal, and targeted access group. Organizations can send information, programs, and upgrades in accordance with the positions, team memberships, interested hobbies, security groups or other membership conditions of the organization, or other member relationships. SharePoint Portal Server is built on the Multi-functional features provided by Microsoft Windows® SharePoint Services 2003, which forms the core of the Solution Accelerator for Intranets architecture.
For more information on SharePoint Portal Server, see: http://www.microsoft.com/sharepoint/server/evaluation/overview/technologies.asp.
Windows SharePoint Services
Windows SharePoint Services (previously known as SharePoint Team Services) is a component of Microsoft Windows ServerTM 2003 that helps teams create Web sites for information sharing and document collaboration. Users can easily cooperate with Windows SharePoint Services in document, tasks, contacts, activities, and other information. In addition, the management personnel of the team and the site can easily coordinate the site content and the user's activities. SharePoint Portal Server 2003 uses Windows SharePoint Services sites to create a portal page for personnel, information, and organizations. In addition, the portal also uses some organizations and management tools to expand the functionality of the Windows SharePoint Services 2003-based Web site and allows the team to post the information on the team site to the entire organization.
Microsoft Office System
Microsoft Office System is an integrated desktop productive kit that integrates user familiar client tools and collaborative services in the server. With Microsoft's Enterprise Internal Network Collaboration Technology, Information Permission Management, and support for Scalable Markup Language (XML), this product can effectively link people, information, and business processes. Integration with SharePoint products and technology can help teams work more efficiently. Solution Accelerator for intranets can implement several applications, such as document workspaces, and personal sites, using this integration capability.
Windows Server 2003 and Internet Information SERVICES 6.0
In order to use SharePoint Portal Server 2003, your computer must run Windows Server 2003. Such a functional characteristic such as a modified cluster support, symmetrical multiprocessing and greatly improved file system performance can improve the performance and stability of the internal network. Windows SharePoint Services is included in Windows Server 2003.
Internet Information Services (IIS) 6.0 - It is already included in Windows Server 2003 - is a full-featured and high-performance web server product that makes it possible to deploy web applications and XML web services. IIS 6.0 includes a fault-tolerant process model that greatly enhances the reliability of Web sites and applications. In addition, IIS 6.0 also provides health monitoring, in order to prevent, discover, and restore the failure of web applications.
For more information on Windows Server 2003, see: http://www.microsoft.com/windowsserver2003/evaluation/overview/family.mspx.
For more information on IIS 6.0, see: http://www.microsoft.com/windowsserver2003/evaluation/overview/technologies/iis.mspx
Solution overview
Chapter 2 of the Overview Guide sumbs the typical knowledge sharing issues that today's business and organizations may encounter. Table 3.1 The problem is performed by one of these business issues with the specific function of SharePoint Portal Server 2003. But there is no representation of all functional features of SharePoint Portal Server 2003. For more information on the functional features of SharePoint products and technology, please visit: http://www.microsoft.com/china/sharepoint/
Table 3.1: Business Issues and SharePoint Portal Server 2003 Product Features
Business Problem SharePoint Portal Server 2003 Product Function Collaboration Team lacks contacts / large number of email attachment team sites, conference workspaces, document workspaces, and complex document collaboration document workspace, Microsoft Office System integrates lack of collaborative tool discussion, investigation, The photo library and custom list Slow documentation release process Upload multiple file information by Microsoft Office System Discovery is difficult to classify, organize, and partition portal information topics can be effectively organized into browse portal content, document profiles use rich elements that can easily search. Data describes documentation. Incompatible or custom architectural architecture management Source Sources for Source Portal Sites, Windows SharePoint Services Site, File System, Web Site, Microsoft Exchange Storage, and Lotus Notes Index Protocol handlers. Cannot provide common search You can subscribe to the search results Unable to access document text and properties Full text search Personalization is difficult to use personal information and document sharing personal site lack of personalization or targeted content issuance process notification, WEB Parts Personal Collection, customization Layout, personalized view, flexible profile architecture email, calendar tool, and portal content lack contact Microsoft Exchange Server 2003 integration lacks targeted portal content access group classification, access group rules application integration business application lack Integrated single sign-on, custom web part (Enterprise Application Integration), compatibility with Microsoft ASP.NET platform Solution Accelerator for intranets value positioning
Solution Accelerator for intranets is a strictly tested normative document package that provides a good start to provide you with high availability of enterprise internal network solutions. Users can shorten or eliminate the time and fund barriers to create high-quality internal network solutions using Microsoft products.
This section summarizes its advantages for partners and users.
Solution development
Solution Accelerator for intranets is designed to help you use SharePoint Portal Server 2003 to successfully develop an enterprise internal network solution. Figure 3.1 shows the customization of three levels of solutions. The configuration suggested here forms the core of an internal web service, and then the user can customize it to meet the unique needs of each user itself. This approach can:
Shorten the market time of the product, because the project planning and execution time has been significantly shortened. Keep a continuous architecture in all service products and specific solutions, allowing you and Microsoft to make it easier to provide support for the solution. Improve information about the availability and performance of your internal web service products. Ensure that services and solutions benefit from Microsoft to the subsequent development of accelerators and solutions.
Figure 3.1 Enterprise Internal Network Solutions Customized Hierarchy
Architecture development
In addition to maintaining a comprehensive compatibility with our recommended physical architecture, the SHAREPOINT Portal Server site and the Windows SharePoint Services site and the corresponding component logic planning have focused on the system in future growth and maintenance.
Resource assessment advice
Users and partners can benefit from the wide range of performance characteristics collected during the Solution Accelerator for intranets. During the development process, we established, test, and compare various large-capacity server configurations. Chapter 4 of the Planning Guide contains specific relevant information, and how to give a cut and realistic advice on how to meet current capacity and future growth. Seriously observe Chapter 4 of the "Operation Guide", in the application of the load, the behavior information of the farm is applied to determine whether the specific method of the service field is smooth, and when you add more capacity. Chapter 5 of the Construction and Test Guide describes the results that run performance tests on the reference hardware configuration. The original performance data is analyzed and compared with Microsoft's internal experimental projects, which can help you plan hardware and licenses budget. Hardware selection
The baseline test for hardware configuration is conducted by Hewlett-Packard to test the recommended architecture. By using the same hardware or hardware with similar features and performance, you can affirm that your development solution has the performance performance claimed by these documents. Chapter 2 of the Planning Guide contains a detailed specification parameter of the HP reference hardware, which is recommended to use the minimum server configuration, and give the network hardware selection recommendations.
Solution logical architecture
The structural composition of the tissue is 10,000, while the design of SharePoint Portal Server 2003 is extremely flexible. Solution Accelerator for intranets provides some specific recommendations around these topics based on SharePoint Portal Server and related and shared features.
concept
Understanding the following concepts is important before examining high-level configuration.
Share service
Sharing services are some public services in SharePoint Portal Server 2003, provided by a central portal and is used by other portals. These are briefly introduced these services that can be shared:
User profile: User profile organizes and displays all known user properties in the portal site. The configuration file can be imported directly from the company's Microsoft Active Directory® directory service. The benefit of a part of the configuration file as a sharing service is that the process of importing from Active Directory can be managed in a central location. Because the user can modify the properties of the configuration file, this centralized storage allows the user to change their data in one location and let this data is used for all portions. Access group: Access the group is a customized user group. Administrators can establish an access group based on Active Directory users, groups, or other properties. For example, if you want to build a visit group called "Sales Manager", you can create rules to add users and groups, and then add users with the "Sales Manager" in all positions. By using access group summary features, you can create a user's access group that contains users that are summarized according to the signed criteria. Access groups can be used to locate content related to portals, such as portal lists, news, and even Web Parts (see section below). The benefit of a part of the access group as a sharing service is that it can build a set of target groups across all portals. Search: Search Components provide search services for the portal. This is a service that responds to user queries. Search components work with index services. The index service is responsible for scanning the content and establishes an index. The search service reads the index and returns the query result. The benefit of a portion of the search service as a sharing service is that you can use the content to be used on all portals by scanning the content. Notice: Notification can help users track changes in the work-related content. Users can choose to get notifications when changing in the following:
Search Query Area file document library staff list will notify a part of the shared service is that users can keep a set of notifications for all portals. Because "My Alerts" will list "My Site" on the company, let Web Part contain a collection of notifications. In the context environment of the shared service, notifications only refer to notifications created in the portal. Notifications created in the subsequent SharePoint site will be saved in a separate site. Personal Site: Users can create a personal SharePoint site, which is called "My Site), which provides users with personalized custom information. The content displayed by the site is for a certain user individual according to the member relationship of the specific access group. In addition to personal notices for tracking content changes in portal sites and organizations, "My Site" also provides links to documents, users, or Web sites. The benefit of a part of "My Site" as a shared service is that in a business, users only need to have a "my site". Since it is tightly integrated with Office 2003, it is very important to have a "My Site" directly through the "Save As" dialog box. Single sign-in service: Single sign-on is an authentication process that allows users to access multiple applications only once. Single sign-on is the core characteristics of SharePoint Portal Server 2003, but it is not clearly used in the application context of Solution Accelerator for intranets. The benefit of a part of the single sign-on as a shared service is that the company can apply saving and managing credentials to an external application in a location and then use these credentials in all portions. Solution Accelerator for intranets explains how to configure and maintain shared services in a single server site, and referred to as "In-Farm Configuration).
For more information on using a shared service (or a par configuration) in the multi-server, see the product documentation of SharePoint Portal Server.
Portal
In general, the portal is a Web site for collecting information, applications, and services. You can use it to extract complex, multi-change information and services in your business system into a single unified interface. The portal has a front end that customizes it to meet your needs of content and services.
You can use the portal created by SharePoint Portal Server to provide a set of access points for information findings and management. From the portal site, users can search for "My Site" located within the organization, external information, browsing content, accessing him (or her), and add notifications. Users can customize the views of the portal by adding or configuring the default or customized Web Parts (such as Search, News and Notices). The portal contains the user's own security credentials. You can lock the entire portal and do not allow some users to access, or you can provide "reader" access to everyone. In one gateway, according to different business requirements, the contents of each part can have more or less security. Let everyone owns the "reader" permission on the portal is a reasonable approach. In the portal, you can create some subject regions and only allow some users to access.
Solution Accelerator for intranets provides guiding principles for the planning, construction, deployment, and operation of the organization and department-level (business unit) portal.
Work area
Workspace is a centralized meeting place, and information workers can use it shared intellectual capital and conduct projects and document collaboration. Workspace is Windows SharePoint Services components, with four distinct types. SharePoint Site: The SharePoint site is a key component of the Solution Accelerator for intranets. The SharePoint site is a Windows SharePoint Services site designed to drive teamwork. Document libraries, lists, advertisements, surveys, discussions, and links are all integral part of the team site. Because all SharePoint is based on Web Parts, users can customize page formats and layouts, and can be customized using third-party Web Parts. Personal Site: Personal Site is also known as "My Sites), which provides a place for the site's contributor and other users to share documents and links. Personal Site can include personal notifications created by users to track the case where the portal and the other places of the organization have changed. Document Workspace: Document Workspace is a short-term site associated with one or more documents. Users can use a copies of a document to edit a public document copy, or edit different copies, and the document will be updated regularly to save the user's modification to a public copy. Integration with Microsoft Office System not only enables users to easily create and manage document workspaces, but also enable them to access the content stored in the document workspace offline. Meeting Workspace: The meeting work area is a site that focuses on information related to one or more meetings. It can be used to release:
Meeting Schedule Participant List Related Documents Operations Project Task Memo
Solution Accelerator for intranets provides normative guiding principles for the planning, creation, backup, and recovery of site collection (working blocks and subgroups). Also surrounds how to organize teams and personal sites in order to be able to have higher flexibility and easily achieve future growth needs.
area
The portal site area in Microsoft Office SharePoint Portal Server 2003 provides an intuitive navigation for users to find and browse from the documentation to the site from the document to all types of content to the site. You can use the area (Areas) to organize information in the portal to different packets. Allow users to easily browse information. The area under the Topics can help users who are not familiar with other portal sites to find the information they need. Documents can appear in several different areas. The area can include content stored in SharePoint Portal Server and include links to other content sources (eg, a Web site or file shared). Creating a valid portal site structure requires a detailed plan, and has a certain understanding of the way others organize content.
Medium-sized farm
SharePoint Portal Server 2003 Product Documentation Use this word to describe a special configuration. For this document, the medium-sized server farm needs:
One or two front-end web servers and the search components are enabled. One index management and job server one or more computers running SQL Server 2000
Large-scale farm
Microsoft Office SharePoint Portal Server 2003 Product Documentation uses this word to describe a special system configuration. In this document, large-scale farms need:
Two or more front-end web servers. Two or more search servers. It is recommended that you do not use more than 4 search servers. One or more index management servers, one of which is used as a job server. The number of index management servers cannot be more than 4. A computer that runs SQL Server 2000 in a number.
Organizational structure
Large organizations are generally composed of multiple business units, and each business unit is composed of large and small teams. These different organizational units share information in a variety of different ways: interior, between each team, between the team, the business unit, and the entire company. Solution Accelerator for intranets provides a means for corporate organization, management, and sharing of these information wealth produced by various teams, business units, and entire enterprises. The purpose of the team is to solve specific business problems. In order to achieve this goal, team members need to make documents, conduct discussions and sharing research results. Windows SharePoint Services can manage the site to provide users with a centralized and secure web environment including a document repository, discussion group, schedule, task list, and site usage report. The establishment of the department is to organize the team within the border of the company in accordance with the administrative functions or geographic. Members of the department need to track news and activity information related to the department. They also need to browse the content related to their team or other team, and the content created by other teams. The department-level portal provides a safe internal site, including news and notices related to the department, so the activities that affect the entire large organization will be notified to all departmental teams and team members. In addition, each department may also need to provide applications for their users. Portal workspaces and reusable software component catalogs provide possible solutions to enterprise formation and delivery of such a solution with high quality and low development time. For example, companies can develop some business integration or business intelligence applications. Organizations can have a business portal to provide users with information (news and notices, as well as within organizations, external navigation information) and accessibility (search and notifications) of the collection information from department or team hierarchy. On all levels, content access can be restricted, allowing only specific users or group access, which allows them to bear a specific role on a particular content, such as the author or reader. If all the servers are authenticated through a public directory or domain, the access control can be implemented at all levels.
Benchmark logical architecture
Solution Accelerator for intranets is composed of a server farm (medium or large) and an enterprise portal with shared service. All search, configuration, profiles, notifications, and access group data are saved in the enterprise portal. In addition, enterprise portals is also responsible for hosting personal sites throughout the organization. The department-level portal is created in the farm.
Associated with each department-level portal is a numerous team site, each team site may have some sub-sites, conference workspaces, and document workspaces. Figure 3.2 shows an internal network solution with a central portal to provide sharing services for three sector-level portals. This central government portal is also associated with some personal sites. The figure shows the specific method of each department-level portal using the service provided by the central portal, and the way each department-level portal has a related team site.
Figure 3.2 Logical Architecture: Shared Service Wide and Hierarchy of Portal
Enabling shared services requires all portals to share the same configuration file, search, and personalized configuration. This can achieve a continuous user experience in the internal network of the entire enterprise, but some coordination work needs to be made between the various business units. Chapter 3 of the Planning and Architecture Guide introduces how these shared services should be planned to make it a specific need for specific needs of the entire organization.
Typical logical architecture
Since understanding the concepts of departmental and enterprise portals have been understood, you can now get a typical portal configuration. Each front-end web server can be configured to collect the portals, team sites, and personal sites required for the entire organization. Table 3.2 shows an example of a logical architecture. It pointed out the site (portal, team set or personal site collection), the name of the virtual Web site, and the URL example of the site.
Table 3.2: Site example with typical logical architecture
Site Description URL Sample Enterprise Internal Network Portal (Site Based on SharePoint Portal Server) http: // Corp (Main Enterprise Internal Network Gate) Personal Site Collection (Site Based on SharePoint Portal Server) http: // corp / mysite / (employee "My Site") Human Resource Portal (Site Based on SharePoint Portal Server) http: // HR (Human Resource Portal) HR Team Site Collection (Site Based on Windows SharePoint Services) http: // hrteams / seats / Recruiting ( Team site responsible for recruitment matters) IT portal (Site based on SharePoint Portal Server) http: // IT (IT department department portal) IT team site collection (Site based on Windows SharePoint Services) http: // itteams / seats / helpdesk (IT Support Department Team Site) Marketing Portal (Site Based on SharePoint Portal Server) http: // Marketing (Department-Level Portal) Marketing Team Site Collection (Site Based on Windows SharePoint Services) http: // MarketingTeams / Sites / Payroll Chapter 3, which is the Construction and Test Guide.
Solutions Physical Architecture
Solution Accelerator for intranets provides guidelines for building solutions with the following feature.
High availability
SharePoint Portal Server 2003 is a logical extension for Microsoft Office System. It provides collaboration, information retrieval, and classification features. As internal network solutions have gradually become extremely important focus issues with the core information tools and business processes of enterprises, stability and availability become extremely important focus. Implementing high availability is one of the most important objectives of Solution Accelerator for intranets.
high performance
High performance is one of the main design goals of SharePoint Portal Server 2003. This accelerator is recommended has excellent performance performance, you can use it to design your own solutions.
Easy to operate
"Operation Guide" details the method of operation required to maintain the physical architecture suggested here. It can significantly reduce the risk and unknown of an inner network solution to deploy and maintain an internal network solution.
Easy to grow
This accelerator provides a reference architecture that has two growth schemes designed for different requirements. Each solution can be easily implemented by gradually adding a server. In addition, you can also deploy two growth programs at the same time in order to greatly enhance the capacity of the system.
Benchmark Physical Architecture
The core requirements of the Solution Accelerator for intranets physical architecture are high availability, that is, all services that make up the user experience implement a comprehensive redundancy. The reference architecture specifies redundancy on the front-end web server, search server, and running Microsoft SQL ServerTM 2000. If the index management / job server fails, it does not immediately affect the user's web browsing or search experience, so these components can reside on a single backend server.
The final architecture includes the following components and described in Figure 3.3.
Two-to-end Web Server that enables search services, one index management / job server, two database servers
Figure 3.3 High-hierarchical physical architecture facing a reference farm with high availability has a minimum high availability. For more information on the future growth, see Chapter 4 of the Planning and Architecture Guide.
The front-end Web server uses the network load balance technology to load balancing. Network load balancing is a software-based cluster technology, which includes in all versions of Windows Server 2003. Network load balancing provides high performance and failover protection, which acts as an indispensable role in achieving high availability and horizontal telescopic performance of Solution Accelerator for intranets. For more information on network load balancing, see Chapter 4 of the "Operation Guide", hardware load balancing devices can also be used for network load balancing of the front-end web server, but Solution Accelerator for intranets does not provide support or guidance for this method. .
The database server can be configured using SQL Server's single instance failover cluster, which is a software-based failover technology based on Windows Clustering, and only SQL Server 2000 Enterprise Edition can provide such a failover technology.
At the database layer, high availability can not only be obtained, but also achieved by careful selection of data components and configurations. For more information on the hardware used when developing and testing the Solution Accelerator for intranets, see Chapter 4 of the Build and Test Guide.
SharePoint Portal Server 2003 has a very flexible farm topology. The "Configuration" department of the SharePoint Portal Server Administration Guide introduces three different levels of supported configurations: small, medium and large. The reference architecture of the Solution Accelerator for intranets corresponds to the medium-sized SharePoint server field architecture. By using a lateral telescopic manner provided by Solution Accelerator for intranets, it can be extended to a large-scale farm configuration. The specific scaling process can be found in Chapter 5 of the "Construction and Test Guide".
Growth option
Solution Accelerator for intranets describes two ways to transversely telescopic for the reference architecture, each way is equivalent. In which direction is expanded in, or whether expanded in both directions, depending on the specific usage of the internal network solution.
The use of the case configuration file describes the average usage of each component of the SharePoint internal network solution. Some users have to frequently use search functions frequently. And other users may use a large number of team sites. This configuration file defines the feature of the internal network load, helping you make a decision on how to extend the physical architecture of the solution. If you want to know the reference usage configuration file used during this accelerator, see Chapter 4 of the Build and Test Guide.
Although the reference farm supports high capacity of typical users, your user needs may require you to make a lot of investment in hardware at the beginning. This accelerator focuses on transverse telescopia (that is, adding more servers) instead of longitudinal telescopic (i.e., adding more processors and memory), because horizontal telescopic is more complicated in the architecture, and will result in larger operations Impact. Chapter 4 of the Plan and Architecture Guide and Chapter 5 of the Construction and Test Guide discusses capacity planning and system growth (which is also growing and why it needs to grow.
Growing into large-scale farm
If the number of users is very large, and you expect that they will continue to use search features, and you may need more index management servers, you should consider deploying large-scale farms. Deploying a large-scale farm is the only way to add more index management servers (the maximum number is 4), and the only way to separate the front-end Web service and search server. You can implement a minimal large-scale farm configuration by adding two dedicated search servers and searching for the existing two front-end web servers. The final architecture includes the following components and is shown in Figure 3.4.
Two front-end web servers two search servers one index management and job server two database servers
Figure 3. Dominant service field physical architecture
Note: The network load balancing configuration of the front-end Web server has not changed, and the failover cluster of the SQL Server for the database server is also better. You may notice that the dedicated search server has no load balancing architecture. The SharePoint Portal Server front-end web server will automatically balance the search request in all available search servers, so there is no need for additional configuration.
The SQL Server 2000 database server is configured in this case.
For more information on server topologies, see Chapter 3 of Chapter 3 and The Construction and Test Guide for Planning and Architecture Guide.
Add a dedicated Windows SharePoint Services farm
If you expect users to use SharePoint sites and the contents of the business and department-level portals, you should consider adding a dedicated Windows SharePoint Services farm for SharePoint sites. This can be achieved by adding two dedicated front-end web servers that resides Windows SharePoint Services. The virtual Web site used to reside the SharePoint site can then be moved to a new private server.
The final architecture includes the following examples and as shown in Figure 3.5.
The two front-end web servers for search components are enabled. Two Windows SharePoint Services front-end web server one index management and job server two database servers
Figure 3.5 Physical Architecture with a Windows SharePoint Services Server Square
The benchmark logic structure specifies in a separate and dedicated portal hosting team site. Therefore, the configuration of the SQL Server 2000 database server does not have to change.
For more information on server topologies, see Chapter 3 of Chapter 3 and The Construction and Test Guide for Planning and Architecture Guide.
stand by
The contents, scripts, templates, and examples in this guide are intended to help you smoothly implement an internal network solution in the production environment. These files and guidance do not enjoy subsequent support services. Microsoft does not have scripts and support files included in this guide provide any form of guarantee. Please note: Be sure to strictly and thorough testing in the test environment before using them to the production environment.
You can get support services for products that make up the Solution Accelerator for intranets through the following three services.
Problem Resolution Services Adviser Service (Premier Support Services)
Problem solving service
Microsoft's Problem Solutions (Microsoft Problem Resolution Services) can help users who have a problem with Microsoft products.
Problem Solutions The service is based on product failure. A Problem Resolution Fault is defined as a single support issue and requires reasonable labor to solve this problem. A single support problem refers to a problem that cannot be divided into multiple sub-problems. Table 3.3 provides a problem solving service support phone number. Table 3.3: Professional Support Phone Numbers for Problem Solutions
Professional Support Phone Number Developers (800) 936-5800IT Professional (800) 936-4900 Partners (Distributors and Consultants) (888) 456-5570Microsoft Certification Partners (888) 677-9444
For questions outside the United States, please visit: http://support.microsoft.com/common/international.aspx.
Consultant service
Microsoft Advisory Services is a support option that can be delivered in remotely, which adds predictable support services that provide improvements that exceed basic product maintenance needs.
Microsoft Consulting Services provides short-term advice and guidance for problems that have no coverage of problems, users can request services for consultants to help them solve the designs, develop, and deploy problems.
The consultant service can be contacted by the following call: (800) 936 - 5200.
For more information on consulting services, please visit: http://support.microsoft.com/default.aspx? Scid = fh; en-us; offerprophone # faq607.
Preferred support service
The Microsoft Premier Support is intended to help customers develop, deploy and manage business systems built with high quality Microsoft servers and desktop products. The preferred support provides a predictive account management relationship, personalized technical services, and fast, professional, and all-weather technical issues. The preferred support provides a comprehensive set of service suite, focusing on the following four key areas:
Account Management: Personal account management and the support within Microsoft ensure that the preferred support can meet the unique needs of your company. Proactive Services: Planning and knowledge transfer services aim to reduce system management and support costs, they will eliminate them in the germination state before the problem occurs. Premier Online Support: Extensive Information Service ensures that your support team can continue to get the latest technical problem solving knowledge and related products. Responsive Services: Fast, accurate and uninterrupted operational problems solve.
For more information on preferred support (Premier Support), please contact your Microsoft customer representative, or call Microsoft Enterprise Support Sales Center, users please call: (800) 936-3200, Canada users please call: (877) 568-2495.
