Design a share point 2013 architecture – the basics

3,467 views

Published on

session walks you through the necessary steps to design a SharePoint 2013 architecture. It explains what information is needed to actually design such an architecture and discusses the many things you need to know to make the right decisions. It helps you to design a small, medium or large SharePoint farm for your customers

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,467
On SlideShare
0
From Embeds
0
Number of Embeds
1,668
Actions
Shares
0
Downloads
90
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • 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.
  • Design a share point 2013 architecture – the basics

    1. 1. 
    2. 2.         
    3. 3. How to create an architecture
    4. 4.                
    5. 5. My Sites Intranet Internet Load Balancer
    6. 6. Explain the steps in creating an architecture
    7. 7.            
    8. 8.                 
    9. 9.   Groups of people Location Data Accessed 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
    10. 10.           
    11. 11.      
    12. 12.         
    13. 13. SharePoint Online Hybrid On premises Subscription Active Directory SharePoint Online 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
    14. 14. Business Owners Steering committee IT Management Risk & Security Compliance Development Team End users
    15. 15.     
    16. 16. New! New!  New!    New!
    17. 17.  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
    18. 18.     Enterprise      Enterprise Enterprise
    19. 19. Topologies
    20. 20.         
    21. 21. Role Traditional Topology Streamlined Topology Streamlined (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
    22. 22. Farm Number of servers Purpose Limited Deployment 1-2 Used for 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
    23. 23. Start designing your SharePoint 2013 architecture
    24. 24.      http://technet.microsoft.com/en-us/library/cc263199.aspx
    25. 25.
    26. 26. • •
    27. 27.
    28. 28. • •
    29. 29. • • •
    30. 30. • • • • •
    31. 31. • • • •
    32. 32. • • • • •
    33. 33. Load Balancer
    34. 34. Load Balancer
    35. 35.             
    36. 36. the complete picture
    37. 37. My Sites Intranet Internet Load Balancer
    38. 38.          
    39. 39. Other important things that concern architecture
    40. 40.         
    41. 41.      
    42. 42. Questions?

    ×