Anúncio

SharePointDetails.ppt

Senior Sharepoint Consultant at CSM Technologies em CSM Technologies
26 de Mar de 2023
Anúncio

Mais conteúdo relacionado

Similar a SharePointDetails.ppt(20)

Anúncio

SharePointDetails.ppt

  1. Architecture SharePoint 2010 Smruti Ranjan Nayak
  2. hardware & software requirements
  3. SharePoint 2010 • SharePoint 2010 : hardware & software requirements • Installation scenarios • Single with bult-in database • Single server • Multiple server farm
  4. SharePoint 2010 • Hardware requirements—Web servers, application servers, and single server installations • Processor 64-bit, four cores • RAM 4GB (Dev) / 8GB (Prod) • HDD 80GB + 2*RAM • Hardware requirements—Database servers • Processor 64-bit, four cores (small deploy.) 64-bit, eight cores (medium deploy.) • RAM 8GB (small deploy.) 16GB (medium deploy.) • HDD 80GB min
  5. SharePoint 2010 • Software requirements http://technet.microsoft.com/en-us/library/cc262485.aspx Database Env Single built-in FE & App servers Microsoft SQL Server 2008 R2 (x64) Windows Server 2008 (x64) SP2 • Standard • Entreprise • Data Center • Web Server Windows Server 2008 R2 (x64) • Standard • Entreprise • Data Center • Web Server Windows Server 2008 (x64) SP2 • Standard • Entreprise • Data Center • Web Server Windows Server 2008 R2 (x64) • Standard • Entreprise • Data Center • Web Server Microsoft SQL Server 2008 R2 (x64) SP1 & CU2/CU5 or later* Microsoft SQL Server 2005 R2 (x64) SP3*
  6. Farm Topologies
  7. Development Farm
  8. Development Farm • SharePoint Server – All Roles – Sql Server – Evaluation Farm • Users ? – 100
  9. Development Farm • SharePoint Server – All Roles • SQL Server – All SharePoint DB • User ? – 10 000
  10. Small Farm
  11. Small Farm • SharePoint Server – Server 1 • Web Server • Query Server – Server 2 • Web Server • Query Server • Roles • SQL Server – All SharePoint DB • Users ? – 10 000/20 000
  12. Small Farm • SharePoint Server – Fend 1 & 2 • Web Server • Query Server – Application Server • SQL Server – All SharePoint DB • Users ? – 10 000/20 000
  13. Small Farm • SharePoint Server – Fend 1 & 2 • Web Server • Query Server – Application Server • SQL Server – Sql 1 • SharePoint Search DB – Sql 2 • SharePoint DB
  14. Medium Farm
  15. Medium Farm • SharePoint Server – Fend 1 • Web Server – Fend 2 • Web Server – Application Server – Query & Crawl Server • SQL Server – Sql 1 & 2 • Search DB – Sql 3 • SharePoint DB
  16. Large Farm
  17. Large Farm OR • Crawl • Query • All Services • Search • Content DB • All DB
  18. Farm Administration
  19. Farm Administration Staff position Small farm Medium farm Large farm Multiple farms System administrator 1 Full Time 1 Full Time 2 Full Time 2 Full Time Search administrator 1 Part Time 1 Full Time 1 Full Time 1 Part Time 3 Full Time Site designer 1 Part Time 1 Full Time 2 Full Time 3 Full Time Software developer N/A 1 Full Time 1 Part Time 2 Full Time 3 Full Time Software tester N/A 1 Part Time 1 Full Time 2 Full Time SQL DBA 1 Part Time 1 Full Time 1 Full Time 2 Full Time
  20. Search
  21. SharePoint 2010 • Microsoft SharePoint Foundation 2010 search • Search is scoped to a single site collection • Search does not crawl external data source • Most search capabilites are configured automatically • Crawls automatically without scheduling & with admin control • Ifilter for Office are included • 10m items / search server
  22. SharePoint 2010 • Microsoft SharePoint Foundation 2010 search – Single server SharePoint Foundation 2010, including search, can be installed on a single server.
  23. SharePoint 2010 • Microsoft SharePoint Foundation 2010 search – Dedicated search server • Search can be put on a dedicated application server • Search server includes both the query and index functions (these cannot be separated) • Search role cannot be deployed to more than one server for redundancy or to increase performance
  24. SharePoint 2010 • Microsoft SharePoint Foundation 2010 search – Scaled for capacity • Search servers are assigned to crawl different content databases • Search servers uses a separate crawl database and property database for indexing and responding queries
  25. SharePoint 2010 • Microsoft SharePoint Server 2010 • Scalable search technology (100m items) • Integrates with the SharePoint’s social networking features • Taxonomy • User generated tags • Taxonomy influences search rankings and experience
  26. SharePoint 2010 • Microsoft SharePoint Server 2010
  27. SharePoint 2010 • Fast Search Server 2010 for SharePoint – Require great performance, scalability – Require enriched entreprise search • Ability to customize query • Ability to customize navigation – Crawl different types of internal and external content sources • Database
  28. SharePoint 2010 • Fast Search Server 2010 for SharePoint • Process content and build index partitions • Process search queries FAST servers
  29. Server roles
  30. Server Roles • Web Server • Application Server Roles – Search Roles – Other Cross Farm Services – Client Services – Other single farm service • Database Server – Search DB – Content DB – Other Service DB
  31. Server Roles • Service Oriented Architecture
  32. Server Roles • Service Oriented Architecture – Access Database Services – Excel Calculation Services – …
  33. Server Roles • SSP is Dead – MOSS 2007 • Search • Excel Services • … – SharePoint 2010 • Service Applications
  34. Server Roles
  35. Security Configuration
  36. Security Configuration Account type Account name SQL Service sqlSvcAcc Setup Admin spAdmin Farm Account spFarmAcc Application Pool Account spAppPoolAcc_<Name of the webapp> Application Pool Account for BDC Service Application spAppPoolBDCAcc Application Pool Account for Excel Service Application spAppPoolEXCELAcc Application Pool Account for PowerPoint Service Application spAppPoolPPTAcc Application Pool Account for Word Service Application spAppPoolWORDAcc Application Pool Account for Search Admin Web Service spAppPoolSearchWebSvcAcc Application Pool Account for Search Queryr and Settings Web Service spAppPoolSearchQueryAndSiteSetAcc SharePoint Foundation Search Service Account spfSearchSvc SharePoint Foundation Search Content Access Account spfSearchCAAcc SharePoint User Profile Synchronization Service spUserProfileAcc SharePoint Site Collection Administrator spSiteColAdmin_<Name of the site collection> • Service Account naming
  37. Database Taxonomy
  38. Database Taxonomy • DB Taxonomy SP2010_Config Development Farm Config DB SP2010_AdminContent Development Central Admin content DB SP2010_Logging Development SharePoint Logging DB SP2010_Service_UserProfile_Social Development User Profile social database SP2010_Service_UserProfile_Synch Development User Profile synch database SP2010_Service_UserProfile_Profile Development User Profile database SP2010_Service_UserProfile_MySites Development User Profile MySites database SP2010_WebApp_Intranet Development Content DB for Intranet Top Level Site Collection SP2010_Service_ManagedMetadata Development Managed Metadata Service SP2010_Service_Search Development Search Service database SP2010_Service_Search_Crawl Development Search Service Crawl database SP2010_Service_Search_Property Development Search Service Property database SP2010_Service_WebAnalytics_Reporting Development Web Analytics Service reporting database SP2010_Service_WebAnalytics_Staging Development Web Analytics Service staging database SP2010_Service_SecureStore Development Secure Store Service database SP2010_Service_State Development State Service database SP2010_Service_Usage Development Usage Service database

Notas do Editor

  1. Database Environment - CU3/CU4 might send a compatibility warning - Hotfix needed for SQL Server 2005 SP3 (http://go.microsoft.com/fwlink/?LinkId=165748) Single built-in If you are running Windows Server 2008 without SP2, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically. Before install, you must install a hotfix for the Framework .NET 3.5 SP1. It’s an update for Windows Server 2008 and Windows Server 2008 R2 (KB979917). FE & App servers
  2. 1 Tier
  3. 2 tiers Avantage de pouvoir rajouter un autre serveur front end et application par après pour augmenter la ferme.
  4. Small farm: Typically < 50,000 users
  5. 2 Tiers
  6. 2 Tiers
  7. 3 Tiers 10 000 000 D’items indexer Pas de cluster SQL
  8. Medium f   : Typically < 100,000 users
  9. Deux front end et un troisième en relai éventuellement en cas de crash Deux serveur applicatif pour le crawl et les querys Troisième serveur pour les applications (excell, powerpoint, …) Quatrième serveur pour les applications éventuellement
  10. Large farm: Typically < 500,000 users
  11. Large farm: Typically < 500,000 users
  12. Large farm: Typically < 500,000 users
  13. SharePoint 2010 – Service orientée architecture SharePoint peut dorénavant utiliser beaucoup plus de services sur des serveurs d’applications .Concrètement là ou SharePoint 2007 ne pouvait exécutée que Excel ou l’indexation et le search. SharePoint 2010 attaquent un ensemble de service.
  14. L'infrastructure de Service fournit un isolement d’application complet: -. Chaque application de service peut utiliser des bases de données séparées -. Peut fonctionner sur des applications pool différente. …
  15. Maintenant on a une gestion des services granulaires avec les « Application Services » qui nous permettra d'activer ou de rendre disponible n'importe quel Service et n'importe quelle instance d'un service, en plus de permettre l'assignation d'un administrateur différent par service. Les services peuvent aussi être partagés avec d'autres batteries de serveurs.
  16. L’un des changements dans l’architecture logique de SharePoint 2010 est de ne plus retrouver les fournisseurs de services partagés que nous avions dans la version précédente La nouvelle architecture logique des applications de services dans SharePoint 2010 permet d’obtenir une granularité et une sécurité accrues vis à vis des applications web qui vont consommer ces services. Ainsi dorénavant, les nouveaux services permettent une flexibilité plus importante. Chaque applications de service peut-être consommer par une ou plusieurs applications web simultanément. Ce qui devrait permettre aux administrateurs de garantir la plus grande sécurité vis à vis des données accessibles entre les applications web. Ainsi, une application web ne pourra consommer que les services définis par l’administrateur.
Anúncio