240 likes | 339 Views
First Steps With SharePoint Technologies. David Cattanach, Microsoft Limited. What we’ll cover. Common things WSS/SPS customers do Install Customise the look and feel Create some funky web parts Connect one or more web parts together Deploy them onto another server
E N D
First Steps With SharePoint Technologies David Cattanach, Microsoft Limited
What we’ll cover • Common things WSS/SPS customers do • Install • Customise the look and feel • Create some funky web parts • Connect one or more web parts together • Deploy them onto another server • Monitor what people are doing with SPS • Take advantage of events • Pull/push remote data using Web Services • Set up multiple sites • Size the servers • SharePoint Bingo - 86
Session Prerequisites • Overview knowledge of SharePoint Portal Server (e.g. previous session) • Good personal hygiene • An idea about some sort of dev stuff such as C# being a programming language or you once owned a Sinclair Spectrum or Commodore 64
Architecure Recap Office 2003 HTTP IIS 6.0 (Reqd) FrontPage ISAPI ASP.Net SPS WSS OLEDB • Windows Server 2003 (required) • NTFS drive WSMDE (Reqd)
78 – Installation • FrontPage Server Extensions • Required by VS.Net web projects • Cannot exist on any virtual servers you wish to extend with WSS
28 – SQL vs MSDE vs WMSDE • SQL Server 2000 SP3a • Full RDBMS Server product • Personal, Standard, Enterprise versions • Plus BI, Reporting, etc… • MSDE • Ships with various products such as Access, SPS • Limited to 2Gb RAM and 2GB DB size • Throttled to 5 concurrent users • Can upgrade or migrate to full SQL Server • WMSDE • Specifically for Windows Server 2003 • Installed with products such as WSS and UDDI • Slight differences above MSDE • Can upgrade or migrate to full SQL Server
14 - Customising your Site • Browser-based Editing • Creating lists, libraries, surveys, etc • Placing web parts • Personal vs public views • FrontPage 2003 • Earlier versions of FP may be incompatible • Radical look and feel alterations • More granular modifications to web parts • Useage reports
92– Build a web part in VS.Net • Similar to Custom Web Controls • Download the Web Part Templates • Add the UI controls and Functionality • Render the HTML • Mark as Safe • Extensible UI through tool parts & menus • Emphasis on Safety • A Bad Web Part Can Destroy a Site
74 – Connected Web Parts • Allows Web Parts to Send & Receive Basic Types of Data • 6 Connection Interfaces • Connection Chain Must be Homogenous • No Circular Connections • Can Set Maximum Connections • Connecting Private Parts • Cross-page Connections • Cell, Row, List, Filter, ParameterIn, ParameterOut
52 - Package and Deploy it • Can be Located in \bin or the GAC • Wpresources • Build a Web Part Package (.cab) • Manifest.xml (mandatory) • Web Part assemblies (optional) • Class resource files (optional) • DWP files (optional) • Deploy Using stsadm.exe
90 - Monitoring SPS 2003 • Site Usage Data • Must be configured via the admin page • Must have rights to view usage data • Stored in system32 \LogFiles\STS and the Webs table (for 31 days/months) • Data Viewed through WSS or FrontPage • Other tools • Diagnostic logs • Event viewer • IIS log files
84 - Monitoring SPS 2003 • Microsoft Usage Analysis • Total Number of Sites: 148,457 • Total Number of In-Use Sites: 81,634 • Total Number of Unused Sites (never modified): 66,823 • Total Number of Large Sites (250MB+): 1,710 • Total Number of Medium Sites (5-250MB): 23,875 • Total Number of Small Sites (5MB-): 56,049 • Total Number of In-Use Lists: 308,007 • Total Size: 2099499MB (2.1 TB) • Average Size of a Site: 26MB • Most prolific SharePoint World Wide File Types: .doc, 711,834, 31% of total documents, average size 361Kb • Total Number of personal sites: 31,001 • Total Number of In-Use Team Sites: 24,625 • Total Number of In-Use Meeting Workspace Sites: 8,805
68 – Handling SPS Events • Server-side/Client-side Events • SPS Specific Events • Build Class to Implement IListEventSink • Strongly Name and Place in the GAC • Attach the Event Class to Doc Library
88 – Writing a Custom Web Service for SPS • Consume existing web WSS/SPS services • Usergroups, webs, lists, meetings, views, subscription, portal, userprofileservice, areaservice, search, etc • Create custom web services
58 – Setting Up Multiple Sites • Scalable Hosting Mode www.company1.com www.company2.com www.company3.com • No Need to use Host Headers in IIS • Populate Hosts file • Config db must be created with the –hh switch • Cannot use IP-bound virtual servers (Q830342)
36 – Sizing Recommendations Single server • Specification • 1Gb+ RAM • 100Gb+ free hard disk space • A 2 GHz+ P4 processor • Capacity • Process 20 Web pages per second • Process two search queries per second • Index five documents per second • Store more than 100,000 documents • Include more than 1 million documents in indexes • Host more than 10,000 team and personal sites
For More Information… • SharePoint Developer Centermsdn.microsoft.com/SharePoint • Web Component Directorywww.microsoft.com/SharePoint/webparts • Training • 2014: Customizing Microsoft SharePoint Products and Technologies 2003 • 1881-X: Microsoft SharePoint Products and Technologies Resource Kit • Capacity Planning (WSS, SPS) • www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsb07.mspx • www.microsoft.com/technet/prodtechnol/office/sps2003/plan/cappisps.mspx • Technet website www.microsoft.com/technet