Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 13 ppt

MCT USE ONLY. STUDENT USE PROHIBITED Planning a Service Application Architecture 2-41 Farms with No Local Service Applications Farm A has no local service applications, but consumes all of its services from the Enterprise Services Farm. This limits the range of possible services to the User Profile Service, the Managed Metadata Service, the Business Connectivity Services, the Search Service, the Secure Store Service, and the Web Analytics Service. This means that the farm is probably not one where users would consume more obvious functional service applications, such as Excel Services or Visio Services. This design is probably best suited to publishing environments. The benefits of this design include: • Centralization of resources on the Enterprise Services Farm. • Reduced administrative overheads on Farm A. • Provision of pan-organization services, such as the User Profile Service and the Managed Metadata Service. Collaborative Farms Farm B has a range of local services, which makes it more useful for collaborative working because these may include Excel Services and Access Services. This taxonomy still benefits from the organization-wide User Profile Service and Managed Metadata Service. Note that there is a divisional Managed Metadata Service on Farm C, which indicates that there is a subgroup taxonomy that is applicable to both Farm B and Farm C. The benefits of this design include: • Access to centralized service application resources. • Local administrative capability. • Integration with other farms. Specialized Farms Farm C is a smaller environment, with only one Web application that uses primarily local services. This may indicate that this is a specialist department that has specific requirements. In this instance, the Excel Services and Business Connectivity Services applications are isolated from other farms. This farm also has its own Managed Metadata Service so that it can manage a taxonomy that is distinct from the organization’s taxonomy. MCT USE ONLY. STUDENT USE PROHIBITED 2-42 Designing a Microsoft® SharePoint® 2010 Infrastructure The benefits of this design include: • Service isolation. • Metadata autonomy. • Access to centralized services, such as the User Profile Service and the Managed Metadata Service. MCT USE ONLY. STUDENT USE PROHIBITED Planning a Service Application Architecture 2-43 Lesson 4 Mapping Service Applications to Your Logical Architecture All design must be driven by business need and documented by the solution architect. For service applications, you must design your solution based on the existing logical architecture. This is an additional layer of functionality that will lead to a final overarching set of design documentation. When you map requirements to service applications, you must ensure that you get business stakeholders to sign off the design. This will largely be a high-level agreement on function because supporting services will have little meaning for most business users. As with the logical design, it is essential that you maintain the documentation of your service application for management and administration purposes. MCT USE ONLY. STUDENT USE PROHIBITED 2-44 Designing a Microsoft® SharePoint® 2010 Infrastructure Objectives After completing this lesson, you will be able to: • Describe how to identify the service application requirements for an organization. • Describe how to use a planning worksheet to document service application instances. MCT USE ONLY. STUDENT USE PROHIBITED Planning a Service Application Architecture 2-45 Identifying Business Requirements for Service Applications Key Points Mapping business requirements to the available service applications demands that you have a thorough understanding of what service applications offer and what your business users want to achieve. It should not be your goal to use as many service applications as possible, but to use the right ones. For example, just because information workers use the Microsoft Office system does not mean that you should deploy all of the service applications that are related to Microsoft Office; these are necessary only if you want to use their functionality. Required Applications Identifying service applications that the organization requires is dependent on the information that you gather as part of your analysis of business requirements. It is rare for a user requirements document to specify any need for the User Profile Service, so you must interpret which services are necessary to deliver business functionality. For example, if the business requirements specify that the business wants to use more social computing functions, such as tagging and My Sites sites, you should be able to rationalize that to a need for the User Profile Service. MCT USE ONLY. STUDENT USE PROHIBITED 2-46 Designing a Microsoft® SharePoint® 2010 Infrastructure Isolated Services When you have identified all of the required services, you should then identify whether some divisions or departments have a requirement for isolated instances of these services. This is not a function of preference, but rather a result of real business need. For example, a department may have a taxonomy that they want to use for search. If this is unique to this department, you should consider deploying a separate service instance that enables departmental users to manage their own taxonomy. These users will not be separated from the corporate Managed Metadata Service, but they will have an additional taxonomy that they can use. You may also need to identify the level of isolation that is necessary for service applications so that you can decide whether to provide separate service application databases. Multiple Instances You should identify which, if any, services are critical to your business and a level of performance that is acceptable to the users. When you have this information, you may choose to include multiple instances of important service applications for improved performance or increased security. If you do require multiple instances for resilience, ensure that you host these instances on separate servers. For example, you should implement two instances of Excel Services in the same application pool to ensure increased availability for users of Excel Services. By having two instances on separate servers, you can ensure that the service continues, even if an application server fails. Performance All service applications place resource demands on servers. If you have a series of resource-intensive service applications, such as Excel Services or the Visio Graphics Service, you should ensure that you implement these on separate platforms. Multiple Farms From a performance and management perspective, your goal should be to deliver a single farm solution for your organization. Often architects regard farm separation as the first, or even only, option to isolate users. However, Web applications and site collections are the first options that an architect should select. Remember that you can only share six services across farms. If you must deploy multiple farms, you should identify and group common requirements so that you can design for easy management and better performance. MCT USE ONLY. STUDENT USE PROHIBITED Planning a Service Application Architecture 2-47 Centralized Services If you have a compelling reason for establishing two or more farms for your deployment, you should identify which of the available service applications you can share. This will minimize administrative overheads and create a corporate unity for business components such as social computing. MCT USE ONLY. STUDENT USE PROHIBITED 2-48 Designing a Microsoft® SharePoint® 2010 Infrastructure Mapping Instances by Using the Service Applications Planning Worksheet Key Points You must document the service applications that you plan to implement and the core information about these. You should always maintain documentation about the service applications that you deploy. This will help you to maintain the environment. It will also enable you to ensure that you have configured dependent service applications. Planning Worksheet The planning worksheet is specific to the logical design that you have created for your organization because it reflects the Web applications with which services are connected. The columns in the worksheet include: • Service application. This column lists all of the service applications. You can add service applications based on your SharePoint 2010 SKU and any third-party service applications that you use. • Description. This column gives a brief description of the service functionality. Although this may not be necessary for an experienced architect, it makes it MCT USE ONLY. STUDENT USE PROHIBITED Planning a Service Application Architecture 2-49 easier to map services against business requirements. You may add dependencies here to assist less experienced IT staff. • Service application instances. This column enumerates the number of instances for each service application. Make sure that you have all of the instances that are necessary for isolation and performance. • Web application proxy groups. This column lists the Web application proxy groups. For each Web application that uses a service application, you should identify the name of the proxy group. For most proxy groups, this should be the Default option. However, you can also specify the custom groups with their associated Web application. There may be a series of these columns. • Proposed database names. This column lists the names of the service application databases that you intend to create. For each service application that you create, you should name the associated database or databases. Remember that multiple instances can share a common database set, so if you want to isolate service applications at the database level, you must provide names for each service instance. You may need to consult with your DBA to ensure that you select names that fit with any existing standard. MCT USE ONLY. STUDENT USE PROHIBITED 2-50 Designing a Microsoft® SharePoint® 2010 Infrastructure Lab: Planning a Service Application Architecture Exercise 1: Designing a Logical Architecture Scenario The logical design for the Contoso, Ltd environment has been signed off, so you now need to define the service applications that are necessary to service the business requirements. Your team must also test part of the design by creating Managed Metadata Service instances for Contoso, Ltd and Contoso Research on the test environment. The main tasks for this exercise are as follows: 1. Read the supporting information. 2. Complete the Service Applications Planning worksheet. . For each service application that you create, you should name the associated database or databases. Remember that multiple instances can share a common database set, so if you want to isolate. Services applications are isolated from other farms. This farm also has its own Managed Metadata Service so that it can manage a taxonomy that is distinct from the organization’s taxonomy PROHIBITED 2-50 Designing a Microsoft SharePoint 2 010 Infrastructure Lab: Planning a Service Application Architecture Exercise 1: Designing a Logical Architecture Scenario The logical design