Microsoft SharePoint Server 2007


Published on

Prezentacija "Microsoft SharePoint Server 2007" održana na ComTrade Fabrici Znanja.

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Microsoft SharePoint Server 2007

  1. 1. Challenges
  2. 2. Business Challenges • Islands of information and applications • Slow responsiveness to business and user needs • Costly custom development and maintenance • Poor sharing inside and outside the organization • Difficult to find the right content, data, and people • Increasing information management risk
  3. 3. Feature Drill-Down
  4. 4. Feature Drill-Down Overview • SharePoint Feature Areas • Collaboration • Portal • Search • Content Management • Business Processes • Business Intelligence
  5. 5. SharePoint Feature Areas Business Intelligence Collaboration Server-based Excel Outlook Integration spreadsheets and data Groove Integration visualization, Report Docs/Tasks/Calendars Center, BI Web Parts, Blogs and Wikis KPIs/Dashboards Project Manager lite Business Processes Enterprise Portal Rich and Web forms Templates, Site based front-ends, Directory, My Sites, LOB actions, social networking, pluggable SSO privacy control Content Management Integrated document Enterprise Search management, records Enterprise scalability, management, and Web contextual relevance, rich content management with people and business data search policies and workflow
  6. 6. Collaboration • Outlook and instant messaging integration • Groove integration • Documents, tasks and calendars • Blogs and Wikis • Basic project management
  7. 7. Portal • Enterprise Portal Template • Site Directory • My Sites • Social Networking • Privacy Control
  8. 8. Search • Enterprise scalability • Contextual relevance • Rich people search • Rich business data search
  9. 9. Content Management • Document management • Records management • Web content management • Policies and workflow
  10. 10. Business Processes • Rich Forms • Web Forms • Workflow
  11. 11. Business Intelligence • Server-based Excel • Report Center • Web Parts • Dashboards • Business Data Catalog
  12. 12. Deployment Planning
  13. 13. Planning Portals and Collaboration
  14. 14. Portals and Collaboration • Features of the greatest value to the organization • Web Applications Name and Purpose • Plan for the use of Site Collections and Subsites in the environment • Quotas and Site Expiration Plans • Management Plans for the Environment • Communication Plan
  15. 15. Features and Web App Names • What features match your organization’s needs? – Blogs – Wikis – Collaboration Workspaces – E-mail integration • How do you want to present this information to the users? – Web applications define URL names: starting suggestions include: • http://mysites – For individual Web applications • http://team – For all collaboration Web applications
  16. 16. Site Collections and Sub-Sites • How do you want to organize your information? – Site collections • Unique security permissions and ownership • Lowest level of granularity of quota is the site collection • Site usage tracked at the site collection level – Sub-Sites • Allow for security inheritance • Can re-use security groups created for the site collection
  17. 17. Site Quotas and Expirations • Quotas – Typical recommended start • 500 MB for My Sites • 2 GB for Team sites • Site expiration – Should this feature be enabled? – Notification timing – Timing for site deletion
  18. 18. Management and Communication • Who will manage the SharePoint environment and respond to requests? • How will sites be requested? – Centrally Administered - Manual process (request through help desk) – Site Self Creation Process – Individuals create sites automatically as required by using out-of-the-box site self creation feature • How will the service be communicated to users? – Lunch and Learns – E-mail communication – Other methods
  19. 19. Planning Search
  20. 20. Information Taxonomy • Crucial for intuitive and successful search experience • Taxonomy can be mapped to search scopes • Organization taxonomy defines – Information hierarchy – How main site collections will be laid out – How subsites structure looks – Main departmental Web sites – Project and Team Sites – My Sites
  21. 21. Content Crawling Definitions Term Definition Content Any item, such as: •Web page •Word document •Business data •E-mail message Crawling The process of accessing content Indexing •Parses content and its properties (the metadata) •Builds a content index Crawling + Indexing Makes content available to users Information gathered by •Type of content, such as Site or a file share crawling •Start address from which to start crawling •Behavior to use when crawling, such as how deep or how many hops to allow •Crawling schedule Content source Collection of similar types of content, such as URLs for SharePoint site or URLs for file shares
  22. 22. Three Source Scenarios You may want to: 1. Crawl all of your content 2. Crawl content that is external to the server farm 3. Exclude some sites
  23. 23. Defining Content Sources • Determine content location – Where – On what types of servers • SSP administrator creates one or more content sources • Content source provides information to the crawler – Type of content – Start address – Behavior – Crawling schedule
  24. 24. Content Sources • Default content source – Called Local Office SharePoint Server sites – Used to crawl and index content • Reasons for creating additional content sources include – To crawl different types of content – To crawl content on different schedules than other content – To limit or increase the quantity of content that is crawled
  25. 25. Types of Content Sources Type of Type of Content Content Source SharePoint sites •SharePoint sites from the same farm •Additional Office SharePoint Server 2007 sites, Windows SharePoint Services 3.0 sites •SharePoint sites from Office SharePoint Portal Server 2003 or Windows SharePoint Services 2.0 sites Web sites •Other Web content in your organization not found on SharePoint sites •Content on Web sites on the Internet File shares Content on file shares within your organization Exchange public folders Microsoft Exchange Server content Lotus Notes E-mail messages stored in Lotus Notes databases Business data Business data stored in LOB applications
  26. 26. Scheduling Considerations • Downtimes and peak usage – Coordinate your crawls with the server administrators – Ensure you avoid downtime or peak usage • Some sources of content are updated more frequently than others – Determine general high-level update times, such as • Monday to Friday • No Saturday or Sunday – Set up crawl schedules for each content source
  27. 27. File-Type Inclusions and IFilters • Content is only crawled if: – Relevant file name extension is included in the file-type inclusions list – An IFilter is installed on the index server that supports those file types • Additional IFilters generally required are PDF and Microsoft OneNote – Install Microsoft Office OneNote client on index server to index OneNote 2003 and OneNote 2007 files
  28. 28. Crawl Rules • Avoid crawling irrelevant content by excluding one or more URLs • Crawl links on the URL without crawling the URL itself • Enable complex URLs to be crawled • Enable content on SharePoint sites to be crawled as HTTP pages • Specify whether to use – The default content access account – A different content access account – A client certificate for crawling the specified URL
  29. 29. Search Experience • Enable users to quickly find the information they need • Consider and implement the following: – Search User Interface (UI) – Custom Scopes – Advanced Search and filtering search results based on managed properties – Keywords and best bets – Control of relevance ranking – Control of how links appear in search results – Search based alerts
  30. 30. Default Scopes Scope Purpose Level Customizable All Sites Search across all content in •Search Center Yes the index •Top-level site •Subsite •Lists and libraries People Search for people •Search Center Yes •Top-level site •Subsite •Lists and libraries This Site: Site name Search across the current site •Top-level site No and all of its subsites •Subsite •Lists and libraries This List: List name Search across the current list Lists and libraries No
  31. 31. Custom Scopes • Identify broad content sets on which users are likely to want to search – Can tie directly to your site or information architecture – May span the information architecture across • Many sites • Subsets of information within site collections • Decide whether to implement – Shared scopes – Site-collection-level scopes
  32. 32. Site Collection Scopes Possible Actions Shared Site-Collection-Level Choose how to display search scopes   (search drop-down, advanced search, or both) Create site collection level scopes  Copy and modify a shared scope to use as a scope  for the site collection Edit site collection level scopes  Add scope rules  Delete site collection level scopes  View the status  
  33. 33. Scope Rules • Add rules to the scope to define associations between content and scopes Available to Available to Site- Scope Rule Type Shared Collection-Level Tests content by Search Scopes Search Scopes Web address   Location (http://server/site) Property Query (Author =   Single property John Doe) Content Source   A particular content source All Content   All content in the content index
  34. 34. Advanced Search • Users can construct advanced search queries: – For example, to find content that contains the word quot;negotiate“ and authored by Bob Smith, type in “negotiate author:smith” • Most users not familiar with advanced query syntax • Advanced Search page helps users find content without using search syntax • Search results automatically filtered, based on the value of the property they select
  35. 35. Managed and Crawled Properties • Managed properties enable mapping to crawled properties Managed Metadata Scope rules Crawled properties • Author and queries properties • Title • E-mail Address
  36. 36. Properties in Queries • Crawled properties affect a search query – Keep a balance between number of properties and performance – Record initial set of planned properties
  37. 37. Keywords • Users type keywords into a search box when constructing a query • SharePoint administrators can create an entity, called a keyword, that relates directly to keyword phrases that are in the index • Keywords enable site Collection administrators to improve the relevance of end user queries • Keyword definition includes the keyword, description, best bets, and synonyms
  38. 38. Example Keyword Setup • To enable users to search for people out of office, the Administrator created a keyword named quot;oof“. Query Description Of Keywords Keyword Highlighting The Best Bet
  39. 39. Search Results Relevance • Relevance settings are assigned to indexed Web pages • Each relevance setting – Is associated with a particular Web page – Determines how close to the top the link appears • Pages that are assigned a relevance setting are known as authoritative pages • Four authoritative page levels: 1. Most authoritative 2. Second-level authoritative 3. Third-level authoritative 4. Sites to demote
  40. 40. Search-Based Alerts • Administrator controls activation of search-based alerts for a particular SSP • Users specify: – What kind of changes they want to be alerted to – How frequently they want to receive an e-mail alert • If search-based alerts deactivated, site owners should remove the Alert Me link
  41. 41. Planning Content Management
  42. 42. Content Management • Document management • Records management • Web content management
  43. 43. Document Management Collect And Organise Information Document Repository Document Property Managed Document panel In Office 2007 document repository programs template Sales Employment Claims Contracts Asia Pacific Region XML-based Metadata Check-in/Check-out, Management Major/Minor Versioning, and Roles Scanner or Microsoft Office Word Multi-function Device Team Sites File Share
  44. 44. Records Management Active Documents Digital media from client computers, Digital media from client computers, file servers, and e-mail systems file servers, and e-mail systems Records Management Application Collect Litigation Support Tools Destroy Hold Manage
  45. 45. Plan Web Content Management Publishing Web Content Separation of Built-in review/approval Site content and workflow Variations presentation Production Template Server Press PR Director ENGLISH Release GERMAN JAPANESE PR Manager Content Internet Sites
  46. 46. Planning Business Processes
  47. 47. Business Process • Forms – Templates – Template deployment – Supportability and maintenance • Workflows – Document management – Form templates – Content approval and scheduling
  48. 48. Form Templates XML data format Data analysis InfoPath form Browser rendering Data reporting
  49. 49. Form Deployment Site collection Site Published form in Content type document library
  50. 50. Form Support • Upgrading form templates • Retiring form templates • Version control • Mobile device access
  51. 51. Document Workflows Author Confirm Validate Authorize
  52. 52. Form Workflows Author Confirm Validate Authorize
  53. 53. Content Approval Export Web Server Import Web Server Staging Farm Production Farm Internal Network Perimeter Network
  54. 54. Planning Business Intelligence
  55. 55. Business Intelligence • Analyze current business data applications for BI • Identify existing data sources – LOB applications – Data warehouses • Excel Services requirements • Business data presentation • Business data search
  56. 56. Analyze Current Data Applications for BI
  57. 57. Identify Existing Data Sources
  58. 58. Excel Services
  59. 59. BI Presentation • Audiences • Digital Dashboards • Rendering Excel Data • Displaying Data from the Business Data Catalog • Searching Business Intelligence Data
  60. 60. BI Search
  61. 61. Physical Design Planning
  62. 62. Performance and Capacity • Plan for software boundaries • Estimate performance and capacity requirements • Plan scale actions based on performance and growth • Test solution for your environment • User response times
  63. 63. Estimate Performance and Capacity Requirements • Authentication, access control, and authorization • Associated directory • Both common (read) and complex (read/write) user operations • Data and site growth over time • User concurrency • Long-running asynchronous tasks
  64. 64. Hardware Recommendations Computer Role Recommended Hardware Web server Dual 2.5 GHz or faster processors (3 GHz or faster recommended) 2 GB RAM minimum recommended 3 GB of available disk space DVD drive, local or network accessible 1024x768 or higher resolution monitor Application server Dual 2.5 GHz or faster processors (3 GHz or faster recommended) 4 GB RAM minimum recommended 3 GB of available disk space DVD drive, local or network accessible 1024x768 or higher resolution monitor Database server Dual 2.5 GHz or faster processors (3 GHz or faster recommended) 4 GB RAM minimum recommended Hard disk space based on a 1:1.2 ratio of content to database capacity DVD drive, local or network accessible 1024x768 or higher resolution monitor
  65. 65. Estimating Disk Space Requirements Category Description Number Operating system files Disk space required for Windows Server 2003 Setup and system 4 GB files. Swap file The swap file size are the same as the physical memory size, by default. SQL Server installation files Disk space required for SQL Server Setup and program files. 425 MB Database log files Disk space for log files varies based on log settings and the number of databases. Configuration database The configuration database does not generally grow past this 1.5 GB size. This is an estimated maximum size, not a hard limit. Content databases Estimate the initial volume of content that is stored in content databases and also allow for future growth and free space: Future growth Future growth is a key characteristic of the collaboration scenario. Plan for twice the amount of data that you initially plan to experience. Free space Leave at least 25% free space for each hard disk or volume. Total
  66. 66. Index and Application Server Disk Space Requirements Category Description Number Operating system files Disk space required for Windows Server 2003 Setup and system 4 GB files. Paging file The paging file size is the same as the physical memory size, by default. Office SharePoint Server This number is an approximation based on a full installation of 1.3 GB 2007 installation files any Office SharePoint Server2007 edition. The Microsoft .NET 60 MB Framework version 3.0 Content index Add the amount of content in content databases that will be indexed by the index server. 30% of the resulting number is the maximum estimated size of the content index. Free space Leave at least 25% free space for each hard disk or volume. Total
  67. 67. Typical Farm Layouts
  68. 68. Single Server Physical Logical • Server 1: – Content Sites One Server which contains: – SSP • Web front end • SSP admin site • Application • Shared services • Database • Shared Web services – Central administration – All databases
  69. 69. Small Farm (Example) Physical Logical • Server 1 & 2: – Content Sites Load balanced servers: – SSP • Web front end • SSP admin site • Applications • Shared services • Shared web services – Central admin (only svr 1) Server 3 All databases Dedicated SQL server
  70. 70. Medium Farm (Example) Physical Logical • Servers 1 & 2: Load balanced servers: – Content Sites • Web front end – SSP • Applications • SSP admin site • Shared services • Shared web services Application server (Index) Server 3 • Applications SSP Shared service (Index) Shared web services Central Admin Clustered SQL server Server 4 & 5 All databases
  71. 71. Large Farm (Example) Physical Logical • WFEs: servers 1 - 4: – Content Sites – SSP • SSP admin site • Web front end App servers: servers 5 - 10: SSP Svr 5 - 6: Shared service (Index) Svr 7 - 8: Shared service (Search) Shared web services (Search) Application servers:• Index Svr 9 – 10: • Search Shared service (Excel) • Excel calculation Shared web services (Excel) Clustered SQL server Central Admin (server # 5) Server 11 and 12 All databases
  72. 72. Summary
  73. 73. Summary • Business challenges • Features • Deployment planning • Physical design planning • Typical farm layouts
  74. 74. For More Information • Plan for software boundaries (Office SharePoint Server 2007) us/library/6a13cd9f-4b44-40d6-85aa- c70a8e5c34fe1033.mspx • Estimate performance and capacity requirements (Office SharePoint Server 2007) us/library/054526b9-417e-4140-b251- 79b68e771c9a1033.mspx
  75. 75. © 2008 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Microsoft, Active Directory, MSN, Outlook, PowerPoint, SharePoint, Visual Studio, and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA
  76. 76. I više informacija na