1. Microsoft Office SharePoint Training Course
Presenter
Sherif Adel

2. Introducing MOSS 2007 What is MOSS 2007. SharePoint Version History.
MOSS 2007 vs. WSS 3.0.
Addressing collaborative challenges.

3. What is MOSS 2007.

4. Microsoft Office SharePoint
What is MOSS 2007 ?
Microsoft Office SharePoint
Microsoft Office SharePoint Server 2007 provides a single, integrated location where employees can efficiently collaborate with team members, find organizational resources, search for experts and corporate information, manage content and workflow, and leverage business insight to make better-informed decisions.
Microsoft Office SharePoint Server is a web-based collaboration & Document Management Platform.
IIS based .
Bus Logic (Application Server Component ).
Storage (Sql server ).

5. What is MOSS 2007 ? Collaboration
Allow teams to work together effectively, collaborate on and publish documents, maintain task lists, implement workflows, and share information through the use of wikis and blogs.

6. What is MOSS 2007 ?
Portals
Create a personal MySite portal to share information with others and personalize the user experience and content of an enterprise Web site based on the user’s profile.

7. What is MOSS 2007 ? Enterprise Search
Quickly and easily find people, expertise, and content in business applications.

8. Enterprise Content Management
What is MOSS 2007 ?
Enterprise Content Management
Create and manage documents, records, and Web content.

9. Business Process and Forms.
What is MOSS 2007 ?
Business Process and Forms.
Create workflows and electronic forms to automate and streamline your business processes.

10. Business Intelligence.
What is MOSS 2007 ?
Business Intelligence.
Allow information workers to easily access critical business information, analyze and view data, and publish reports to make better-informed decisions.

11. What is MOSS 2007 ? Extensibility 1st party components.
3rd party component.

12. SharePoint Version History
Free: STS Retail: SPS 2001
Free: WSS Retail: SPS 2003
Free: WSS 3.0 Retail: MOSS 2007

13. Differences Between MOSS and WSS

14. Addressing collaborative challenges.
Data Sharing.
“Reinventing the wheel.”
knowledgebase (FAQ, Help Desk, Wiki).
Keeping Employee current.
Outlook, Announcement, Alerts ,Calendar.
Team collaboration.
Task List, Blogs.

15. Planning for MOSS 2007 Administration Levels
Tier 1 Admins (Server Management ,Creating Web Apps, Windows , SQL Server , Backups ,IIS )
Tier 2 Admins (Shared Service Management, Searching, Indexing, Form, Excel Services )
Tier 3 Admins (Site, Content Management ,Permissions, Security)

16. Planning for MOSS 2007 MOSS Server Farm Topology
The Physical Arrangement for the MOSS services in a Three Tier Architecture.
First Tier: Web Front End (WFE) serves (IIS).
Second Tier: Application Server (Bus Logic) for Indexing , Searching InfoPath form services, Excel services.
Third Tier: SQL server.

17. Planning for MOSS 2007 MOSS Server Farm Topology cont…
Small Farm.
Standalone.
All tiers in one machine.
Limited to very small organizations.
Installs SQL server express.
1GB RAM,1CPU,4GB Storage.
Distributed Storage.
One server for SQL server database.
One server for MOSS and IIS.

18. Planning for MOSS 2007 MOSS Server Farm Topology cont…
Medium Farm.
Distributed WFE.
Database and Application in one server.
Two or more servers for IIS (WFE) using Network Load Balancing (NLB) OOB with windows server 2003 and a single IP address for All WFE servers.

19. Planning for MOSS 2007 MOSS Server Farm Topology cont…
Large Farm.
Distributed WFE and Storage.
One or More Server for SQL server database connected via Windows Clustering Service (WCE).
One or More Server for MOSS services you can assign one server for Searching and Indexing and One for Excel services and InfoPath form services.
One or More WFE server connected via Network Load Balancing (NLB).

20. Planning for MOSS 2007 MOSS 2007 Integration.
Other Microsoft Servers Integration.
Exchange Server.
Project Server.
Project Web Access (PWA)

21. Planning for MOSS 2007 MOSS 2007 Integration cont...
Office Integration.
Word
Excel
Access “Access List View”.
Power Point “Slide Library”.
Outlook “2 way”.
InfoPath “XML Form Library”.
SharePoint Designer.
Document Workspace.

22. Installing MOSS 2007 Installation Models. System Requirements.
Performing a clean Installation.
Running MOSS Configuration Wizard.

23. Installing MOSS 2007 Installation Models
Basic
Single server standalone.
Sql server 2005 express.
Advanced
Complete (All services local and can expand).
Web Front End (Clustered).
Standalone

24. Installing MOSS 2007 System Requirements.
Hardware
2.5 G.H CPU
1 GB RAM
NTFS
Software
Windows server 2003 sp1 … now windows 7
IIS 6 + SMTP
.NET Framework 3.0 and ASP.NET 2.0
Domain Controller is preferred with one service account for MOSS use in Application Pool and SQL server database as dbcreator,securiyadmin.

25. Installing MOSS 2007 Running MOSS Configuration Wizard.
Installs the configuration Database
Installs and configure the Central Administration Web Application.
NTLM vs. Kerberos
NTLM easy to configure.
Kerberos: More complicated. More Secure. Enhanced Performance through caching. Delegation.

26. Building MOSS Sites SharePoint Terminology. Post-Installation Tasks.
Building SSP and port 80 site.
Creating Subsites and Site Collection.
Deleting Sites.

27. Building MOSS Sites SharePoint Terminology.
Web Application CA
SSP
My Site
Port 80
TLS
Site Collection
Sharing Templates
Site Columns
Content Types
Navigation
Security
Backup
Sub site

28. Building MOSS Sites Post Installation Tasks
Investigating CA site.
Running Services on Servers.
Building Shared Service Provider (SSP) used to manage features that should be centrally managed.
Building port 80 Web Application
Building SSP Web Application
Building My Site

29. Building MOSS Sites Site collection vs. Sub Sites.
Sub sites shares: Permissions Inheritance, Navigation and backup).
Site Collection: are logical containers that are separated by managed paths.
Changing TLS look & Feel (Logo, Welcome Image, and Theme) .
Creating Team Site.
Creating blank Site.
Creating Site Directory Site (Activating Publishing Feature)
Deleting Sub Site.
Adding Site to the Top Navigation bar.
Creating Managed Paths (What is? URL Namespace used for site collection). Types of Managed Paths (Explicit vs Wildcard)

30. Managing MOSS Security
MOSS 2007 Security Model “Rule Based Access Security”(RBAS).
Local/Domain
User/Group Accounts
SharePoint Groups
Owners
Members
Visitors
Permissions Levels Cats
List
Site
Personal
Permission Level
Full Control
Design
Approve

31. Managing MOSS Security
User Permissions for Web Application.
Site collection administrators.
Peoples and Groups.
Adding and Removing Groups from SharePoint Groups.
Site Permissions and Permissions Levels.
Permission Inheritance.
Create a new permission Level.

32. Administrating MOSS 2007 Sites
Personalization.
Personal Features
Personal Views
Web Parts
Personal Sites
My Site (Self Study How to Configure My Site Feature?)
User Profile (Self Study How to Configure My Site Feature?)
Managed Paths and Site Collections
Creating new managed path.
Creating new site collection under new MP.
Explicit Vs. Wildcard MP.

33. Working With Lists And Libraries
Investigating Most Common List Templates.
Navigating Views ,Settings , Alerts and Actions.
Workshop Creating FAQ List and Adding it to My Links List.
(Self Study Creating Wikis and Blogs)

34. Managing Content Types Understanding Content Types ECB
What are content types?
Reusable objects to describe data
Lists
Libraries
Content Type Scope
Site Collection
Site
List or Library
Content Type Usage.
Document Template
Columns
Workflow

35. Managing Content Types Creating New Content Types
Creating new “Change Request” Host Document Library
Creating Site Columns for “CRID” and “Project Name” and New Group
Creating new Content Type Inherit from Document Base Content type
Attaching our new content type to doc library

36. Implementing MOSS 2007 Search
Understand Search Arc.
Configuring Search Parameters.
Creating Search Center.
Monitoring Search.

37. Understanding MOSS 2007 Search
Content Sources.
SharePoint Sites.
External Web Sites.
File Shares.
Exchange Public Folders
BDC
Scopes.
Managed Properties.
Usage Reports.
Content Sources are the places that MOSS can crawl for search results.
WSS only include SharePoint sites as a content source.
Crawling and Indexing are search engine related keywords
A search engine operates, in the following order: 1) Crawling; 2) Deep Crawling Depth-first search (DFS); 3) Fresh Crawling Breadth-first search (BFS); 4) Indexing; 5) Searching.
Crawling means sucking content without processing the results.
Indexing means making sense out of the retrieved contents, storing the processing results in a (more or less complex) document index. Link analysis is a way to measure URI importance, popularity, trustworthiness and so on.
Security Trimming
Is the process of excluding and including search results based on user privileges.
Search scopes are a simple and effective way to control the amount of information that the search utility queries in order to resolve a search request. They allow users to easily define an area of the site that may be applicable to what they are seeking.

38. Assembly-Based Solutions.
MOSS 2007 Development
Installing Visual Studio 2008
Integration SharePoint and .NET
What You Develop for Windows SharePoint Services.
Assembly-Based Solutions
ASP.NET Resources
Schemas
MOSS 2007 Object Model
Server and Site Architecture: Object Model Overview.
CAML query.
Site Navigator Application.
MOSS web services.
Querying List Using Web Services.
Assembly-Based Solutions.
Building blocks for a SharePoint Web Part Page that deliver specific functionality to the visitor of the site. Web Parts can deliver data from stores that are not based on Windows SharePoint Services (such as Microsoft SQL Server and Oracle stores); capture data to drive business processes; aggregate or roll up information that is available in the SharePoint sites, or perform many other functions. Many Web Parts are available by default with both Windows SharePoint Services 3.0 and MOSS 2007.
Web Parts
Event handlers
A .NET assembly containing one or more classes that encapsulate code that is executed when certain events (such as adding an item to a list, creating a column for a document library, deleting a site, and so on) occur in SharePoint sites.
Workflow Activities and templates
workflow is a collection of activities Windows SharePoint Services or the information workers involved in the workflow must take. Numerous activities are available; however, you can create custom activities compiled in a .NET assembly and deploy them so that experienced users creating workflows in Microsoft Office SharePoint Designer 2007 can use them. Developers can also create workflow templates by using the workflow extensions for Visual Studio 2005 and deploy these as .NET assemblies to the SharePoint servers.
Timer Jobs
Assemblies containing code that can be scheduled and executed by the SharePoint Timer Service. An example is a job scheduled to create a report every evening for the administrator about documents that have been checked out for more than a week.
ASP.NET Resources.
Application page
A physical ASP.NET page stored in the \12\Template\Layouts folder. This folder is commonly shared by all Windows SharePoint Services sites that are hosted on the Web server. Application pages are ideal for creating additional administration features for SharePoint sites. Because they are not part of the database, inline code is allowed.
Style sheets and master pages
Together, these define the look and feel of a site, as well as the common functionality that is used by all the pages of a site.
User control
ASP.NET user control (.ascx file) that can deliver common functionality to the pages in SharePoint sites. Windows SharePoint Services provides several controls in the \12\Template\ControlTemplates folder. Create additional custom user controls, and for example, visualize them within the master pages. User controls can deliver a particular editing experience to the user, such as custom information management policies or custom fields.
Schemas are XML-based solutions that use the Collaborative Application Markup Language (CAML). Table 3 describes the features whose delivery you can drive by using schemas.
Schemas
Site definition
A custom template for sites that are deployed in the \12\Template\SiteTemplate folder. The core file for a custom site definition is Onet.xml, which contains the global definitions for the site along with the possible configurations.
Features
Introduced in Windows SharePoint Services 3.0, a modular approach for delivering custom schemas and functionality to SharePoint sites. Features can activate what you build and deploy. Many of the previously mentioned types of solutions are made available by using Feature definitions. You can find the list of deployed Feature definitions in the \12\Template\Features folder
Custom Lists
The schemas for custom lists and document libraries are also defined via CAML-based files, many times as part of a Feature definition. However, they can also be part of a custom site definition.
Site Columns and Content Types
Schema for re-usable packaged definitions of content that can be stored and managed in SharePoint containers (lists and document libraries). Site columns and content types are delivered through Feature definitions most of the time.
Custom Field Definitions
These CAML-based files, together with a .NET assembly that contains the code-behind, deliver additional field types that users can select from when creating custom metadata in a document library, for example

39. MOSS 2007 Development Server Architecture
Namespace: Microsoft.SharePoint.Administration Assembly: Microsoft.SharePoint (in microsoft.sharepoint.dll)
The SPFarm object is the highest object within the Windows SharePoint Services object model hierarchy. The Servers property gets a collection representing all the servers in the deployment, and the Services property gets a collection representing all the services.
Each SPServer object represents a physical server computer. The ServiceInstances property provides access to the set of individual service instances that run on the individual computer.
Each SPService object represents a logical service or application installed in the server farm. A service object provides access to server farm-wide settings of the load-balanced service that a respective service instance implements. Derived types of the SPService class include, for example, objects for Windows services, such as the timer service, search, Microsoft SQL Server, the database service, etc. and also objects for Web services, such as Windows SharePoint Services or services in the Microsoft Office system.
An SPWebService object provides access to configuration settings for a specific logical service or application. The WebApplications property gets the collection of Web applications that run the service.
An SPDatabaseServiceInstance object represents a single instance of a database service running on the server computer. The SPDatabaseServiceInstance class derives from the SPServiceInstance class and thus inherits the Service property, which provides access to the service or application that the instance implements. The Databases property gets the collection of content databases used in the service.
Each SPWebApplication object represents a load-balanced Web application based in Internet Information Services (IIS). The SPWebApplication object provides access to credentials and other server farm wide application settings. The Sites property gets the collection of site collections within the Web application, and the ContentDatabases property collection of content databases used in the Web application. The SPWebApplication class replaces the obsolete SPVirtualServer class; but it can still be helpful to think of a SPWebApplication object as a virtual server; that is, a set of one or more physical servers that appear as a single server to users.
An SPContentDatabase object inherits from the SPDatabase class and represents a database that contains user data for a SharePoint Web application. The Sites property gets the collection of site collections for which the content database stores data, and the WebApplication property gets the parent Web application.
An SPSiteCollection object represents the collection of site collections within the Web application. The Item property or indexer gets a specified site collection from the collection, and the Add method creates a site collection within the collection.

40. MOSS 2007 Development Site Architecture
Namespace: Microsoft.SharePoint Assembly: Microsoft.SharePoint (in microsoft.sharepoint.dll)
Each SPSite object, despite its singular name, represents a set of logically related SPWeb objects (see below). Such a set is commonly called a
"site collection," but SPSite is not a standard Microsoft .NET collection class, in contrast to SPWebCollection. Rather, it has members that can be used to manage the site collection. The AllWebs property provides access to the SPWebCollection object that represents the collection of all Web sites within the site collection, including the top-level site. The Microsoft.SharePoint.SPSite.OpenWeb method of the SPSite class returns a specific Web site.
Each site collection includes any number of SPWeb objects, and each object has members that can be used to manage a site, including its template and theme, as well as to access files and folders on the site. The Webs property returns an SPWebCollection object that represents all the subsites of a specified site, and the Lists property returns an SPListCollection object that represents all the lists in the site.
Each SPList object has members that are used to manage the list or access items in the list. The GetItems method can be used to perform queries that return specific items. The Fields property returns an SPFieldCollection object that represents all the fields, or columns, in the list, and the Items property returns an SPListItemCollection object that represents all the items, or rows, in the list.
Each SPField object has members that contain settings for the field.
Each SPListItem object represents a single row in the list.

41. MOSS 2007 Development Web Parts Development
Building blocks for custom SharePoint web parts.

42. MOSS 2007 Development Web Parts Development
Creating simple “Quote of The Day” web part.
Using SPGridView control.
Using SPView.RenderAsHTML() Methos
Understanding web part connections.
Creating filter consumer/filter provider web parts.
Leveraging built-in some web parts.

43. MOSS 2007 Development MOSS Event Handlers.
Creating MOSS Log Event Handler Sample.
MOSS Timer Jobs.
Creating Tasks Monitoring Timer Job Sample.
Introducing List Definitions.
1- Event Handlers
Using WSP project template on visual studio add new item of type Event Handler

44. MOSS 2007 Development MOSS 2007 Workflows
Introducing Windows Workflow Foundation WWF.
SharePoint As Hosting Environment .
Creating Vacation Request SharePoint Sequential Workflow Template.
Using Custom New and Display forms in the Vacation Requests custom list using List Item Content Type and ASPX pages.
Customizing the Task Edit form by applying a new Content Type based on Workflow Task and ASPX Pages.

45. MOSS 2007 Development MOSS 2007 Workflows Cont….
Creating Vacation Request SharePoint State Machine Workflow Template.
Building the Vacation Requests as a InfoPath form library based on the Vacation Request Content Type inherited from Form Content Type.
Using InfoPath to create the Task Edit Form and integrate it with the workflow.
Open Visual Studio and Add a new project based on SharePoint State Machine Workflow
Open the workflow designer and add Four State Activities.
The First one name it ManagerStateActivity, Second ApprovalStateActivity, RejectionStateActivity, And The Last set it as the termination Activity.
Inside the ManagerState add an Intialtion State and Add CreateTask Activity for the Mangaer inside it.
Inside the ManagerState Add EventDriven Activity and Add OnTaskChanged Acivity Inside it then correlate it with the previous Task.
Inside each of ApproveState and RejectState add Initialization State to add code activity inside it.
Open Visual Studio to Create an InfoPath Project for the Vacation Request form.
Inside the form design add a contact selector control to choose the manager.
To configure the contact selector add data source item of type group inside the main data source name it manager then inside it add another Group Name it Person and make it repeating.
Then add Three Another Fields DisplayName,AccountId,AccountType case sensitive.
Add loading event to get the logged user programmatically from Insert->Loading Event.
From Tools use property Promotion to make your fields visible with the content type for the form.
Add the submit button which uses a submit data source to the Vacation Requests Form Library.
Once you finished build your form then publish it to a network location.
Using Central Administration Upload your form then activate it to our Site Collection
From your Form Library make it to allow content type. Then Add a new content type then choose your newly uploaded content type.
To Create the workflow task form add a new project based on InfoPath
Add your controls then to populate these controls from data passed from the workflow
Add a new recive data source based on xml file called ItemMeteaData
The structurte of this file looks like the following
<?xml version="1.0" encoding="utf-8" ?>
<z:row xmlns:z="#RowsetSchema"
ows_userName=""
ows_reason=""
ows_from=""
ows_to=""
/>
Then make your controls to read from these fields.
Finally add your submit button with submit data source which submits to the hosting environment (SharePoint Site)

46. MOSS 2007 Development MOSS 2007 Workflows Cont….
Manually deploy a workflow template.
Workflow Association.
Workflow Instance
Programmatically add a workflow association.
SPWorkflowAssociation class.
Programmatically Start a workflow instance on a list item.
SPWorkflowManager class.

47. MOSS 2007 Development Branding and Customization
Introducing SharePoint Designer.
SharePoint Master Pages.
Ghosting (Uncustomized) vs. Unghosting (Customized)
Designer Pros and Conc.
Deploying and Applying Master Page.
Master Page Feature (Moss Only using Publishing Infrastructure Feature).
SharePoint Designer (Wss and Moss).
Site Definition and List Definition (Wss and Moss).
Useful Links
Developing Master Page
Minimal Master Page
Deploying Master Page as A Feature