Downloaded 125 times
Uploaded byAlexander Meijers
Design a share point 2013 architecture – the basics
The document provides guidelines for creating a SharePoint 2013 architecture, detailing the roles of various servers, such as web and application servers, in supporting internal and external users. It outlines topologies and deployment options ranging from limited to large scale, highlighting the importance of load balancing and fault tolerance. Additionally, the document discusses integrating services and components necessary for operations, emphasizing the need for a well-structured plan to support intranet and extranet functionalities.
More Related Content
Similar to Design a share point 2013 architecture – the basics
More from Alexander Meijers
Design a share point 2013 architecture – the basics
- 2.
- 3.
- 4.
- 5.
- 6.
- 7. Explain the steps in creatingan architecture
- 8.
- 9.
- 10. Groups of people Location DataAccessed Internal employees Intranet Intranet Portal, Company information, internal data, internal project sites, my sites and profiles. External employees Internet, Remote Session Same as internal employees Partners Internet, Remote Session Project sites, Partner Portal Visitors Internet A companies website, customer Portal
- 11.
- 12.
- 13.
- 14. SharePoint Online Hybrid On premises Subscription Active Directory SharePointOnline Directory synchronization Windows Azure Windows Azure Active Directory Tenant On premises Subscription SharePoint Online Sites Sites Search portal Azure SharePoint Server 2013 Reverse proxy Search portal On Premises On Premises SharePoint Farm Windows Server Active Directory and DNS On Premises Active Directory Web servers WFE 1 80/443 App SQL 1 WFE 2 App SQL 2 AD 1 Active Directory AD 2 Cloud Service VPN Tunnel WFE 3 Cloud Service Virtual Network Application servers Windows Azure All databases Dedicated applicat ion servers for search components
- 15.
- 16.
- 17.
- 18. IIS Web Site—SharePoint Web Services Application Pool Managed Metadata User Profile Excel Services Access Services Visio Graphics Secure Store Service Search Business Data Connectivity Word Automation Work App Management Management Machine Translation Default group Application Pool Application Pool Web Application—Published Intranet Content http://Fabrikam Web Application—Community Sites Web Application—My Sites http://my Web Application—Team Sites http://team http://communities http://my/personal/<user> HR Facilities Purchasing Team 1 Team 2 Team 3
- 19.
- 20.
- 21.
- 22. Role Traditional Topology Streamlined TopologyStreamlined (each tier optimized) Topology (Optimize for) Web Server Fast, Light-weight server which responds to user requests from web pages. All web servers are mirrors of each other and load balanced. Directs requests to the appropriate application servers Service Applications, Services and components that serve user requests directly Low latency Runs one or more services in the SharePoint Farm. Load balancing possible by redundant application servers Service Applications, Services and components that process background tasks. Also called batch processing. Load Application Server Access Services, BCS, Metadata, User Profile User Profile Synchronization, Workflow, Machine translation, Work management Search on separate dedicated machines Database Server Stores content and service data. Databases can be clustered or mirrored for failover protection Stores content and service data. Databases can be clustered or mirrored for failover protection Throughput
- 23. Farm Number of servers Purpose Limited Deployment 1-2 Usedfor product evaluation, development and testing with a limited number of users Small farm 3-4 Serve a large number of users and scales out based on how heavily services are used. These types of farms are not always fault-tolerant Medium farm 6+ Serve a large number of users and scales out based on how heavily services are used. Their goal is a multipurpose environment with possible optimalisation. These farms are always fault-tolerant. Large farm Mostly a lot Serve a large number of users. Group service applications, services or databases that have similar performance characteristics on dedicated servers
- 24.
- 25.
- 26.
- 27.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
Editor's Notes
- #24 As an alternative to the traditional farm design, Microsoft® SharePoint® 2013 topologies can be designed to optimize system resources and to maximize performance for users. Optimizing each tierFront-end servers — Service applications, services, and components that serve user requests directly are placed on front-end servers. These servers are optimized for fast performance. Batch-processing servers — Service applications, services, and components that process background tasks are placed on a middle-tier of servers referred to as batch processing servers. These servers are optimized to maximize system resources. These servers can tolerate greater loads because these tasks do not affect performance observed by users.Database-servers — guidance for deploying database servers remains the same.In a small farm, server roles can be combined on one or two servers. For example, front-end services and batch-processing services can be combined on a single server or on two or more servers to achieve redundancy.