Transcript Executive Overview of Moss

Microsoft Office
SharePoint Server 2007
As a Development
Platform
Peruri Srinivasulu
[email protected]
Sept 24 ,2009
Agenda
•
•
•
•
Typical Development Projects
Technology Overview of MOSS 2007
Platform Architecture
Understanding Customizations vs. Custom
Components (Applications)
• Development Life Cycle
• Deployment
• Q&A
Typical Web Application - Development Project Scenarios
•
•
•
•
Forms Applications – LOB with basic CRUD operations.
Event Driven and Workflow based Applications – Approvals, Reviews
Search / Retrieve – Data from LOB and Enterprise Systems.
Reporting data from LOB and Enterprise Systems.
Classifications
• Collaborative / Content Management /Forms
• OLTP – Transactional Systems (Financial, Orders, B2B) etc…
• Data warehouse
A typical Distributed Application – Logical Architecture
Typical Distributed applications – Quality of Service needs
o
o
o
o
Scalable
Secured
Reliable / Highly available
Manageable
• Monitoring , Patch management , etc…
Typical Distributed Applications - Deployment
o XCOPY, MSI’s
Overview of MOSS
Server-based
spreadsheets plus BI
portals built on SQL Server
Analysis Services
Server-based forms and
workflow with smart client
and browser interfaces
Next generation e-mail,
project management,
blog and wiki support
Business
Intelligence
Business
Process
Windows
SharePoint
Services
Content
Management
Integrated document,
records and Web
content management
Collaboration
Portal
Enhanced SharePoint
Portal aggregation and
personalization
Search
Great relevance with
rich search of people
and business data
SharePoint Development Platform
SDK – Software Development Kit
o Everything you see in previous slide is exposed through APIs –
• Rich Object Model, SOAP, Events.
o A well documented APIs and rich set of samples (How To’s).
o Extensible Object Model
o Key to the adoption by the Developer Community.
Customizable Elements in a SharePoint Web Application
o Site Collection
• Site
 Lists and Folders
– Document Folders (type of list)
– Images, Documents, Style Sheets, Java scripts, Templates, etc…
 List Items
– E.g. Pages, News, Tasks , Orders, Suppliers, Document
o
o
o
o
» Fields
» Properties /Metadata of List Items
Master Pages & Layouts
Content Types
Policies
• Auditing, Versioning, Archive etc…
Workflows
• Approvals , Reviews, Custom …..
o Features
SharePoint Page
o Controlled Layouts – Look & Feel, Styles, Fonts
Master Page
Web Part
Zone
Web Part
Zone
Page Layout
Web Parts
ASP.NET 2.0 Runtime
ASP Web
Web Parts
WSS
Parts
WSS V3 Runtime
ASP Web Parts
WSS V2 Runtime
WSS Web Parts
WSS Web Parts
Web Parts – When do I create one
o When Out-of-Box web parts not meeting the requirements.
o Need to retrieve/submit data to external data sources (data stored
outside of SharePoint).
• BDC to the rescue. – MOSS Enterprise
Edition.
Look into Developer Community before Creating one 
www.codeplex.com
What is Business Data Catalog?
• A catalog of business data
• Access to LOB Data in SharePoint
Business Data Catalog – Application Definition
o What is it?
• XML that connects LOB Data to SharePoint
o Contains
• Connection information / Security
• Entities (what exists)
• Methods (how to access it)
• Associations (relationships between entities)
• Actions (external interaction)
o Use SDK
Customization Options & Tools
Change Site Logo, Format, Parts
complexity
Browser
Change Colors, Backgrounds, Fonts
Edit CSS files
SharePoint
Designer
Change Page Layout and Content
Edit Master Pages
Edit Page Templates (MOSS only)
SPD +
Visual
Studio
Share Your Customization with Others
Build Themes and Site Definitions
Development Tools - Choices
Office SharePoint
Designer +
Browser
Web site
construction
Microsoft
Visual
Studio
Custom Coding
(if necessary)
Create lists and doclibs
Design Page Masters/ Page Layouts
No-code data view/forms
No-code workflows
Web part hookup
Web Controls and Parts
ASP.NET page coding
Workflow actions
Event handlers
Package Customizations for Deployment
o Features enhance modular provisioning
• Group logical elements into scenario-driven “features”
• New features can be activated in existing site to add
functionality.
• Features scoped at web, site, web application, farm
• Features can be add to and reused across site definitions.
• Staple Features to existing Site Definitions.
o Solutions
• SharePoint features, webparts, and files are deployed using a
solutions file with the extension wsp. The wsp files are actually
just a “.cab” file.
• Solutions can be deployed to the Farm using Central Admin or
STSADM.exe
Sample Features / Solutions
Application Templates for Windows SharePoint Services 3.0
o Application templates are out-of-the-box custom scenarios tailored to
address the needs and requirements of specific business processes or sets
of tasks in organizations of any size. They also provide a starting point for
partners and developers looking to build deeper SharePoint-based
solutions.
40 Application Templates
Board of Directors
Business Performance Reporting
Case Management for Government
Agencies
Classroom Management
Clinical Trial Initiation and Management
Competitive Analysis Site
Discussion Database
Disputed Invoice Management
Employee Activities Site
Employee Self-Service Benefits
Employee Training Scheduling and
Materials
Absence Request and Vacation Schedule
Management
Budgeting and Tracking Multiple Projects
Bug Database
Call Center
Change Request Management
Compliance Process Support Site
Contacts Management
Document Library and Review
Expense Reimbursement and Approval
Equity Research
Integrated Marketing Campaign Tracking
Manufacturing Process Management
New Store Opening
Product and Marketing Requirements
Planning
Request for Proposal
Sports League
Team Work Site
Timecard Management
Help Desk
Inventory Tracking
IT Team Workspace
Job Requisition and Interview Management
Knowledge Base
Lending Library
Physical Asset Tracking and Management
Project Tracking Workspace
Room and Equipment Reservations
Sales Lead Pipeline
Event Planning
Development Life Cycle for SharePoint Projects
o Requirements
o Build
• Source Control Management
o Testing
o Deploy
• Packaging Customizations into Features and Solutions.
Team Development for MOSS - Individual Developer
Visual Studio Extensions for SharePoint
Push Code from Build Servers to Integration
Promotion of Code and Content to Production
o Code - Assembly
o Content - Artifacts
For a large scale SharePoint custom application
Developer
Sandbox
Integration
Server
QA
Deploy .wsp files , Activate Features
Staging
Production
References
o http://www.microsoft.com/downloads/details.aspx?FamilyId=6D94E3
07-67D9-41AC-B2D6-0074D6286FA9
• MOSS SDK
o http://technet.microsoft.com/en-us/library/cc263199.aspx
• Lots of Visio – MOSS Architectures.
o http://www.codeplex.com
• Community Tools for SharePoint
 WSPBuilder , SharePoint Features
o http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B
28-06E2-4E87-9BAD-086E32185E68&displaylang=en
• Visual Studio Extensions for SharePoint
Q&A