Ms net work-sharepoint 2013-applied architecture from the field v4

1,335 views

Published on

Practical Sharepoint 2013 solutions from the field

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

  • Be the first to like this

No Downloads
Views
Total views
1,335
On SlideShare
0
From Embeds
0
Number of Embeds
717
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ms net work-sharepoint 2013-applied architecture from the field v4

  1. 1. Tihomir Ignatov Senior Consultant Microsoft Corporation Sharepoint 2013: Applied Architecture from the Field (v4)
  2. 2. Agenda What is IT Architecture Lessons Learned from the Field Sharepoint 2013 Apps Public Sector Sharepoint 2013 Infrastructure Telco Oracle2MS migration Transport & Logistics
  3. 3. Software Architecture Deployment Architecture Network Architecture Deployment Architecture
  4. 4. What is IT architecture?
  5. 5. Architecture is Making ideas real “Make everything as simple as possible, but not simpler.” -Albert Einstein
  6. 6. www.iasaglobal.org
  7. 7. Sharepoint Architecture… ?!? Software Architecture Infrastructure Architecture Information Architecture Business Architecture Enterprise Architecture
  8. 8. Sharepoint (product) Architecture?!? Consulting Architects Org. Architects Presales Solution Governance IT Architecture Tradeoff Architecture Delivery Presales
  9. 9. Technical Principles CLOUD first1 Configure before customize 2 Solutions NOT products 3
  10. 10. General Sharepoint Architecture Guidance ALWAYS design against scenarios NOT features Take into account the product limits and boundaries Talk about RECOMMENDED and CURRENT instead of BEST practices Ask Microsoft Premier support about supportability Plan and maintain the capacity Add the Governance plan in scope
  11. 11. What is PLA? SHAREPOINT, LYNC & EXCHANGE MCS, PG & CSS DELIVERY THROUGH MCS
  12. 12. Lessons Learned – SP Apps Government Agency, Public sector  Case management  Multiple AutH sources  Rich reporting  KM  BI Customer Profile Scenario
  13. 13. Apps – Key Requirements Consider your identity sources Consider your App permissions level – hosting web/ tenant/…? Cloud dependency – TO BE OR NOT TO BE? Team skills – Sharepoint, ASP.NET, etc.
  14. 14. SPS 2013 App scenarios
  15. 15. O365 (SPO) Sharepoint 2013 Sharepoint hosted App Cloud On premise Sharepoint hosted App Sharepoint-Hosted App • Any supported AutH sources • Client side code only
  16. 16. O365 (SPO) Azure PaaS Remote App Cloud On premise Sharepoint Auto-hosted App Auto-hosted App • 100% cloud scenario • Any supported identity • Identity through Azure ACS ACS
  17. 17. Any Data Center Sharepoint 2013 Remote Web Internet On premise Provider hosted App Provider-Hosted App (Low-trust) • Any supported AutH sources • Server side code in Remote Web • Depends on Azure ACS Azure ACS Context token
  18. 18. Web serverSharepoint 2013 Remote Web Internet On premise Provider hosted App Provider-Hosted App (High-trust) • Any supported AutH sources • You have to take care about remote web identity and SSO • Server side code in Remote Web • NO cloud dependency S2S STS
  19. 19. Shared Corporate Network Services Sharepoint Server 2013 Sharepoint & Content DBs SQL Server 2012 DNS Attached Files and Metadata Web UI Office Web Apps Server (WAC) 1 2 3 4 Perimeter Network Web Services BizTalk Server Custom DB SQL Server 2012 eID / Government Gateway 5 6 7 8 9 Web publisher Exchange E-mail ADDS Back Officer Administrators Developers Front Officer HTTPS HTTPS External user HTTPS Load Balancer HTTPS HTTPSHTTPS HTTPS 10 SAML 11
  20. 20. Web UI A B C Custom DB Entity Framework BizTalk SPS and Content DBs D F G H 8 10 13 Presentation Layer Application Layer Data Layer Web Services/Web API 7 I E User Attached Files and Metadata C
  21. 21. Sharepoint 2013 Remote Web Gov Gateway STS ADFS
  22. 22. Lessons Learned – SP Infrastructure Telco  Recently upgraded to SPS 2010  They started with 2003  No Governance  No consistency in the customizations, multiple vendors  Want to have a structured, healthy and well performing environment Customer Profile Scenario
  23. 23. SP Infra – Key Considerations (1) Consider the availability and resources Plan your servers and capacity, plan also the data growth… Take into account the skills of the operations personnel According to the new SP Apps infrastructure plan to have a SP Web application with no host header Use host header site collections when you need site with unique URL After Sharepoint deployment always deliver a Governance plan document, even in “lite” format
  24. 24. SP Infra – Key Considerations (2) ALWAYS setup at least 2 environments – TEST & PRODUCTION Create a simple application to track site collection requests Plan a process for site collections and content DBs management Use QUOTAs
  25. 25. Recommended Topologies (1) WFE Front End Services Distributed Cache Back End Services Workflow Manager Crawl Admin Analytics Content Processing Index Partition #0 Replica DB Content Databases Search Databases Config & Service DBs • No HA • All services in a single box • Single point of failure • The data is not reserved • Up to 10M searchable items
  26. 26. Recommended Topologies (2) DB-1 DB-2 Content Databases Search Databases Config & Service apps DBs WFE-1 Front End Services Distributed Cache Back End Services Workflow Manager Crawl Admin Analytics Content Processing Index Partition #0Replica WFE-2 Front End Services Distributed Cache Back End Services Workflow Manager Crawl Admin Analytics Content Processing Replica • There is HA • All services and the data are reserved • Up to 10M searchable items • Recommended for business critical scenarios with small load
  27. 27. Recommended Topologies (3) DB-1 DB-2 Content Databases Search Databases Config & Service apps DBs WFE-1 Front End Services Distributed Cache WFE-2 Front End Services Distributed Cache APP-1 Back End Services Workflow Manager Crawl Admin Analytics Content Processing Index Partition #0Replica APP-2 Back End Services Workflow Manager Crawl Admin Analytics Content Processing Replica • There is HA • All services and the data are reserved • Up to 10M searchable items • Recommended for business critical scenarios with big load
  28. 28. Recommended Topologies (4) DB-1 DB-2 Content Databases Search Databases Config & Service apps DBs WFE-1 Front End Services Distributed Cache WFE-2 Front End Services Distributed Cache APP-1 Back End Services Workflow Manager APP-2 Back End Services Workflow Manager APP-SRC-1 Crawl Admin Analytics Content Processing Index Partition #0Replica APP-SRC-2 Crawl Admin Analytics Content Processing Replica • There is HA • All services and the data are reserved • Up to 10M searchable items • Recommended for business critical scenarios with big load and significant search requirements
  29. 29. Lessons Learned – Oracle2MS migration Transport & Logistics  No experienced Oracle resources on the local market  Microsoft Premier support and consulting are available  More value for the money  Better Enterprise level integration Customer Profile Scenario
  30. 30. The Transition and the Current Stage Oracle ERP BI Microsoft ERP Portal BI
  31. 31. The Solution ERP BI Portal
  32. 32. Architecture ERP Portal BI BE Trusted Network DMZ BI FEBi2sp proxy svc bi2sp svc Internet ERP
  33. 33. Hybrid Productivity • Collaboration • MS Azure DR for Sharepoint Microsoft Public Cloud On-premises Data Center SPS 2013 Prod Farm SPS 2013 DR Farm Azure VPN Microsoft Azure 6 1 23 4 5
  34. 34. File shares to Sharepoint
  35. 35. Contacts BLOG http://tihomirignatov. blogspot.com E-mail Tihomir.Ignatov@ Microsoft.com SUGBG http://www.sugbg.org
  36. 36. Ne zaboravite ispuniti upitnike. Čekaju vas vrijedne nagrade!

×