Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (15)
Similaire à SharePoint best practices
Similaire à SharePoint best practices (20)
Plus de Dinusha Kumarasiri
Plus de Dinusha Kumarasiri (16)
Dernier
Dernier (20)
SharePoint best practices
- 2. • Solution lifecycle • SharePoint implementations • SharePoint customizations
- 3. • Applicable for – SharePoint implementations – Customizations • Capacity Management Model Model Design Pilot, Test & Optimize Deploy Monitor & Maintain Plan Build Operate
- 5. • Plan – What & Why Sites Communities Content Search Insights Composites Sponsor BA SharePoint Consultant Information Architect
- 6. • Plan – Capacity planning • Plan the farm (e.g.: concurrent users, RPS, etc..) • Site collections • Document management • Service applications • Business continuity Capacity Planning Document
- 7. • Plan – Analyze the impact • Hardware changes • Software changes • Process changes Gaps Identified Risk List Project Plan Quality Plan Initial Architecture
- 8. • Plan – Governance Governance Site creation Permission Management Allowed Customization Application development Manage Information Architecture Local Support Training
- 9. • Build – Implement a POC • Identify limitations – Network, hardware, organizational policies • Refine user requirements
- 10. • Build – Use adequate hardware • Use gigabit network adapters • WFE & Application servers use dual network adapters • Pay attention to what each role require – WFE – RAM – SQL – RAM / Storage – Index – CPU – Excel Services – CPU
- 11. • Build – Use farm installation instead standalone installation – Use proper user accounts e.g.: • SharePoint admin (<domain>/sp_admin) • Farm admin (<domain>/sp_farm) • Service application (<domain>/sp_serviceapp)
- 12. • Operate – User management • Recommended to use AD groups • Break permission inheritance with caution • Do we provide administrator access to business user?
- 13. • Operate – Regular monitoring • Health analyzer rules • SharePoint diagnostic studio • Microsoft performance counters • Microsoft System Center Operations Manager
- 14. • Operate – Regular maintenance • Periodic backup of farm/ site collections • Test backups regularly in a test environment • Check storage • Database maintenance plan – Check integrity – Defrag and rebuild indices – Shrink content databases
- 15. • Operate – Patch management Check risk assessment (Severity rating) Plan test deployment with test cases Protect production environment with recommended workarounds issues? Deploy in production environment Deploy in Test environment Verify & Document the change Check MS KB and/or get MS support Recommended changes Notes • The process should begin as soon as Microsoft release patch/service pack/vulnerability • Input should be taken from MS Security Bulletin & Get vulnerabilities from Security team(s) • Microsoft release cumulative update for each 2 months and hotfix whenever MS encounter vulnerability/issue No Yes End
- 17. • Plan – Categorize types of customization – Provide standards for each type • e.g.: Who can use SharePoint designer? Who approves custom solutions? Standard Standard Custom Custom
- 18. • Plan – Formulate a development process Local dev TFS Staging environment Production environment QA
- 19. • Plan – Plan custom solutions • Execution
- 20. • Build – Get help from • Microsoft Visual Studio 2010 SharePoint Power tools • SharePoint guidance library – Application settings manager – SharePoint service locator – SharePoint logger
- 21. • Build – Sample project structure Business Logic Layer Presentation Layer Data Access Layer Data Source Web Service Full Trust Proxy
- 22. • Build – Good practices • Dispose SPSite and SPWeb objects after using • Query lists instead of looping • SPSiteDataQuery to aggregate data instead of looping • Close connections to external system after use
Notes de l'éditeur
- Composites – custom solutions Insight -BI
- Information architecture – how information flows Metadata management, content types