Topologías de SharePoint

Presentación del tema: "Topologías de SharePoint"— Transcripción de la presentación:

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

2 Microsoft SharePoint Conference 2009
3/29/2017 Agenda Arquitectura de servicios de SharePoint 2010 Variables que influencias las topologías 4 ejemplos de topologías © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3 Module 2: Creating a SharePoint 2010 Intranet
Course 10174A Capas lógicas Servidores Web (Front End) Servidores de Aplicaciones (Administración, Index, Query, Administración central, Excel Services, Form Server, etc.) Servidores de bases de datos

4 Microsoft SharePoint Conference 2009
3/29/2017 Aplicaciones de Servicio SharePoint Service Applications Search Excel Calc Service Business Data Connectivity User Profiles SharePoint Foundation Content Config Workflow Sandboxed Code Service Usage & Health Logging Word Conversion Service PowerPoint Broadcast Service PerformancePoint Visio Graphics Service Access Service Web Analytics Managed Metadata 3rd party services… © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5 Aplicaciones de Servicio
Module 2: Creating a SharePoint 2010 Intranet Course 10174A Aplicaciones de Servicio Las aplicaciones de servicio brindan funcionalidad específica de SharePoint Un application connection (proxy) permite la conexión a un aplicación de servicio Las conexiones se agrupan en application connection (proxy) groups Los aplicaciones Web se asocian con un application proxy group, que proveen conexiones (proxies) a una o más aplicaciones de servicio Introduce the terminology related to service applications. Be very accurate in your use or the terms service application versus service. The service is the machine service instance that runs (or does not run) on each SharePoint server based on what you have configured in the Manage Services on Server page in Central Administration. The service application is a logical, farm-level component that manages the behavior of services. You do not need to provide this level of detail to students now. This is for your information as an instructor. Point out that there are components that have two names Application connection (or connection) = proxy Application connection group (or connection group) = proxy group The terminology is inconsistent, even in Microsoft documentation, so it’s up to you, the student, to keep it straight in your head.

6 Module 2: Creating a SharePoint 2010 Intranet
Course 10174A Estructura Lógica Web Application Site Collection Top-Level Site Site List Library [Folder] Item Document Managed Paths Objective: Provide an overview of the SharePoint logical structure within a farm. Delivery Tips: Introduce the diagram, the structure, and the terminology. Do not go into detail as you will be detailing each component later in this lesson. Details: A Web application is the highest level component of the logical structure within a farm. A farm can have one or more Web applications. Within a Web application there are one or more site collections. Site collections have a URL that is a managed path. A site collection contains one or more sites. When you create a site collection, you also create the top- level site in that site collection. Below that top-level site can be one or more additional sites, often referred to as subsites or subwebs. Within a site are pages, lists, and libraries. Lists and libraries can contain folders. Within that list and libraries—possibly organized into folders—are items and documents, respectively. A site collection and all of its content is hosted in a content database. There can be one or more content databases associated with a Web application. An important element of the diagram shown above is that when you create a site collection, you also create a top-level site. They are two separate components, but they always go hand-in-hand. You can’t have a site collection without a top-level site, and you can’t have a top-level site without also having a site collection. Content Database(s)

7 Consideraciones lógicas
Microsoft SharePoint Conference 2009 3/29/2017 Consideraciones lógicas Necesidades del negocio Áreas con servicios aislados Restricciones regulatorias Geopolíticas Regulación o reglamentos Arquitectura de información La arquitectura de los sitios Web afecta su asociación con los servicios © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8 Consideraciones físicas
Escalar horizontalmente/verticalmente influencia la topología lógica Latencia de los vínculos Servicios cerca de los usuarios y el contenido Arquitectura dle directorio Servicios cerca del AD para mejorar la autenticación, sincronicación de perfiles, etc

9 Escalar servicios – Paso 1
Crecer dentro de la granja Scale-up: mejorar el hardware Incrementar memoria, CPU, disco, etc. Scale-out: agregar servidores en las capas Agregar Web Front Ends en NLBs para contenido Servidores exclusivos para servicios que consumen muchos recursos Escalar el servidor de SQL Scale SQL for data-centric services

10 Escalar servicios – Paso 2
Microsoft SharePoint Conference 2009 3/29/2017 Escalar servicios – Paso 2 Múltiples granjas de contenido Más difícil de administrar Múltiples granjas de servicios Se pueden distribuir geográficamente Se recomienda iniciar por la búsqueda © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11 Topologías de ejemplo Pequeña organización Empresas medianas
Empresas distribuidas grandes Estos son solo ejemplos.

12 Woodgrove Organización pequeña Una o pocas ubicaciones físicas
< 5000 Usuarios Usos principales: Colaboración y búsqueda TI: 1-3 personas con roles múltiples Necesita acomodar múltiples “proyectos”.

13 Arquitectura lógica

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

15 Puntos sobresalientes
Una sola granja Configuración predeterminada Capa de aplicaciones y Web combinada Administración del crecimiento Nuevo contenido en colecciones de sitios Agregar servidores adicionales

16 Fabrikam Organización mediana 10k-50k Usuarios
Puede usar alguna o toda la funcionalidad de SharePoint TI: ~10 con múltiples roles y soluciones Uniones intra-organizational limitadas Necesita acomodar múltiples “proyectos”

17 Arquitectura lógica

18 Topología física

19 Puntos destacados Una granja
Aplicaciones Web aisladas Múltiples aplicaciones de servicios Múltiples grupos de proxy Distinción entre los roles de los servidores Administración del crecimiento Agregar nuevos sitios, nuevas aplicaciones Web Horizontalmente al agregar servidores Web y de aplicaciones Se pueden dividir las granjas de contenido

20 Empresa grande Gran corporación multinacional >50k Usuarios
Distribuida geográficamente Múltiples departamentos de TI dedicados Límites organizacionales Puede usar alguna o toda la funcionalidad de SharePoint Brinda hospedaje interno con diferentes SLAs

21 Arquitectura lógica

22 Topología física

23 Puntos destacados Geo-distribución con múlples granjas de servicios
Los servicios empresariales son controlados por TI Central Administración del crecimiento Departamentos adicionales se pueden incorporar como Nuevas colecciones de sitios Nuevas aplicaciones Web en granjas existentes Nuevas granjas Horizontalmente al agregar servidores Web y de aplicaciones Geo-distribución con múlples granjas de servicios Consideraciones de alta disponibilidad y recuperación en caso de desastre

24 Otros escenarios Sitios públicos en internet
Hospedaje de sitios (Multi-tenant hosting)