John B. Underwood Technical Evangelist, ThreeWill · 2017-06-01 · Benefits of SharePoint 2010 as a Product Platform John B. Underwood Technical Evangelist, ThreeWill Audio options

Benefits of SharePoint 2010 as

a Product Platform

John B. Underwood

Technical Evangelist,

ThreeWill

Audio options are available in your GoToWebinar control

panel. You may use computer speakers or you may choose

to connect to audio via phone.

Your Presenter

• John B. Underwood

– junderwood@threewill.com

– http://threewill.com/junderwood

• Technical Evangelist, ThreeWill

• Nearly 30 years of developer experience

• 13 years teaching experience

ThreeWill - SharePoint 2010 as a Product Platform 2

Housekeeping

• Your microphone/phone line is automatically

• Seminar is being recorded for later review

• Use Questio s featu e i GoToWebinar

control panel to submit questions

– May not be answered until the end in order to

cover all of the content

Audience

• Independent Software Vendor (ISV) looking

for new opportunities

• CIO, Architect, enterprise technology leader

seeking to fully utilize the capabilities of

SharePoint within the organization

Outline

• SharePoint Background

• Making the Case

• Platform Strategies

• Platform Capabilities

• Addressing Concerns

• Community Support and Tooling

• Next Steps/Questions/Answers

SharePoint Background

• History

• Capabilities

SharePoint Background

• 2001 – SharePoint Team Services

– SharePoint Portal Server

• 2003 – Windows SharePoint Services (WSS) v2

– SharePoint Portal Server 2003

• 2007 – Windows SharePoint Services (WSS) v3

– Microsoft Office SharePoint Server (MOSS) 2007

• 2010 – Microsoft SharePoint Foundation 2010

– Microsoft SharePoint Server 2010

SharePoint Background (cont.)

• Two parts to SharePoint

– Foundation (free with server OS)

– Server (purchased product)

• SharePoint developer story trends

– Little customization early (2001)

– Customization, but lacking tool support (2003,

– First-class support for Visual Studio (2010)

Making the Case

• Sites

• Communities

• Content

• Search

• Insights

• Composites Any application that needs to provide these services can leverage the SharePoint 2010 platform

Making the Case (cont.)

• Would your application benefit from

SharePoint capabilities?

– Less ti e uildi g plu i g

• Does your target customer already have

SharePoint installed?

– Customer eager to maximize SharePoint

investment

F o a st ategi sta dpoi t, o e ti g to Sha ePoi t p o ides a u e of benefits to both ISVs and customers:

1. Bridging teams – When it comes to collaboration software, teams within an organization tend to select the tools that suit their style of work. For example, the marketing team may use SharePoint for collaborating on documents while the engineering team may use a wiki for this. Connecting your applications to SharePoint allows individuals to collaborate across team boundaries while giving teams the flexibility to choose the tool best suited for them.

2. Eliminating content silos – the Hol G ail of k o ledge a age e t fo any organization is to attain a unified, organized and searchable knowledge repository for all employees to access. Connecting your applications to SharePoint through content embedding, search and single sign-on brings ou lose to a hie i g a sha ed ai ithi ou organization.

3. SharePoint as a corporate standard – For many large organizations, SharePoint is becoming the corporate standard for collaboration, document

a age e t a d o te t a age e t. A ISV’s looki g to sell i to these o ga izatio s should o side a pla s ell with SharePoint st ateg i o de to satisf ou usto e s’ e ui e e ts. ISV’s ithout this st ateg may find themselves eliminated from sales opportunities the ’ e othe ise qualified to win.

Bill Arconati, Product Marketing Manager at Atlassian

Platform Strategies

• Connect

• Extend

• Build-on

Connect

• Integrate existing product(s) with SharePoint

• Common for non-Microsoft platforms (Java,

• Connected servers on same network, separate

networks, in the cloud

• Information can flow in both directions

• Examples: content embedding, search, single

sign-on

Demonstration

• Connect strategy: Integration between

SharePoint 2010 and Jive

Extend

• Building blocks that developers and users can

employ to create solutions

• Enhancing existing SharePoint capabilities

• Examples: custom web parts, custom

workflow actions, out-of-the-box workflows,

custom field and content types

Demonstration

• Extend strategy: supporting rich media types

with Informative Graphics Brava and Redact-It

for SharePoint 2010

Build-On

• Product based entirely on SharePoint platform

• Useful for applications that require a similar

technology stack (ASP .NET, IIS, SQL Server,

web services)

• Ma e plo o e t a d e te d • Examples: vertical business solutions, project

management, help desk application

Platform Capabilities

• Infrastructure

• Content Management

• User Interface

Infrastructure

• Request/Response Pipeline

– Common for web applications

– Built on ASP .NET

• Application Security

– Login credentials stored in Active Directory, LDAP,

SQL Server

– Claims-based authentication

Infrastructure (cont.)

• Service Applications

– se i es i the loud

– Examples: Project Server, Office Web Applications

• Package and Deployment

– Solution package file (WSP)

– Scoped to farm, web application, site collection,

– Content deployment and versioning

Infrastructure (cont.)

Content Management

• External data

– Business Connectivity Services (BCS)

– Open Data Protocol (oData)

– Offline access via Microsoft Office client applications

• Business Intelligence

– PerformancePoint services: dashboards, scorecards,

Key Performance Indicators

– PowerPivot for SharePoint: presentation, integration

with Excel

Content Management (cont.)

• Search

– Simple crawl model or custom code for complex

(i.e. hierarchical) data

– Custom search results user interface

– Federated (each app maintains own index) or

single index in SharePoint

– Connector Framework for custom search and

trimming (SharePoint search and FAST search)

• Workflow

– Out-of-the-box SharePoint workflows (i.e. Approval)

– Custom workflows using Windows Workflow Foundation

– Workflow activities can be created with SharePoint Designer or Visual Studio 2010

– Associate workflow with list/library or create independently for reuse across lists/libraries (the former is new for SharePoint 2010)

• Standard CRUD (Create, Read, Update, Delete) forms

• Custom Views (columns, sorting, filtering) may be created by developers or users

– ASP .NET application pages

– InfoPath forms (supports offline editing via SharePoint Workspaces)

• ISVs may further extend with Custom Actions, rendered columns, custom view types, custom field types

• Othe …

– Event Receivers (triggered from a change to list)

– Governance of data (version history, expiration,

auditing, policies)

– Data tagging: hierarchical term store (taxonomy)

or community-generated tags (folksonomy)

– SharePoint Workspace (formerly Groove) for

collaboration and offline work

Enterprise Perspective

Sha ePoi t can also be used as an underlying CMS to feed into other portal technologies. At McKesson, we use Vignette as our portal today and SharePoint as our collaboration platform. RSS and other technologies have allowed us to start taking advantage of the easy SharePoint CMS capabilities but the content is available in the company wide portal.

Our SharePoint CMS strategy in the initial phase was to use out of the box capabilities. Now that users understand the product and the needs of their Team/Department/Business Units they are taking SharePoint to the next level with data integration, creative redesigns and heavy process

automation projects.

Aaron Rafus, Technology Evangelist, McKesson Corporation

User Interface

• Built upon ASP .NET infrastructure

– Master Pages, Web Parts, Custom Controls, User Controls

– Custom administrative pages, with tight integration to Actions menu

• Non-web user interface

– Silverlight, Windows Forms, Windows Presentation Foundation

User Interface (cont.)

• Custo ize Sha ePoi t i o

Addressing Concerns

• Developer Skillset

• Platform Capabilities

• Systems Management

Developer Skillset

Concern: SharePoint development is a unique

skill set that doesn’t fit ith existing de eloper team

– Legitimate concern in early versions of SharePoint

– Tight integration with ASP .NET and .NET

Framework

– Tight integration with Visual Studio 2010

Platform Capabilities

Concern: SharePoint is a closed or restrictive platform

– Flexible authentication model (no lock-in to Active Directory)

– Support for standards (XHTML, REST, SOAP/web services, AJAX)

– Support for Windows platform services (WCF, WF, LINQ, PowerShell)

– Extension model for core or base services (replaceable p o ide s

Platform Capabilities (cont.)

Concern: SharePoint lacks proper integration

with external or relational data sources

– Business Connectivity Services (BCS)

– Read capabilities for external data

– Improved write capabilities with moderate effort

– Support for offline work via Microsoft Office

integration & SharePoint Workspaces (formerly

Groove)

Platform Capabilities (cont.)

Concern: SharePoint is only a document

repository

– Sha ePoi t heel Sites, Co u ities, Co te t, Search, Insights, Composites)

– Sha ePoi t as a usi ess ope ati g s ste - a

collection of services analogous to file system,

database, etc.

– Extend capabilities

Systems Management

Concern: SharePoint lacks Application Lifecycle

Management (ALM) and Code Isolation tools

– Tight integration with Visual Studio 2010

– Guidance from Microsoft on use of Source Code

Control (SCC), including non-Microsoft tools

– Package and Deployment via WSP

• Throttling, sandboxing, Code Access Security used

fo e a t ode that follo s p ope p o edu e

Systems Management (cont.)

Concern: SharePoint cannot be used to run line

of business applications

– Scalability, reliability, single point of

backup/restore

– Familiarity for IT staff already using SharePoint

– Gua ds agai st shado IT

Getting Started with

SharePoint 2010

• Community Support

• Tooling

• SharePoint ISV Ecosystem

Community Support

• 180+ SharePoint MVPs worldwide

• MSDN SharePoint Products and Technologies

• TechNet

• CodePlex

• Stack Overflow, Server Fault, other public

community sites

Tooling

• Visual Studio 2010

– SharePoint 2010 project templates

– F5 deployment

• Debugging

– F5 support in Visual Studio

– SharePoint Central Administration

– SharePoint Developer Dashboard

– Custom monitoring code

Tooling (cont.)

• SharePoint Designer

– Developers, power users

– Customizing pages, input forms, lists, content types

– Export to SharePoint Solution Package (WSP) for

deployment

• InfoPath

– Forms creation for developers and power users

• Third Party Tools

– CorasWorks, Bamboo Solutions, Nintex, Quest

Next Steps

• Feature Mapping

• Market Analysis

• Bake-off

• Pilot Project

• Consultation

Next Steps

• Feature mapping

– Map a product roadmap to SharePoint features

– Worth investing in a resource that has deep

knowledge of the SharePoint platform

• Market analysis

– Which of your current and future customers are

using SharePoint?

– Building SharePoint application vs. connector for

integration

Next Steps (cont.)

• Bake-off

– Build two similar projects; one based on

SharePoint, another based on other tools

– SharePoint sharpens focus on business problem

• Pilot Project

– Short (1-3 month) exploration

– Clarify Connect, Extend, Build-on strategies

Next Steps (cont.)

• Consultation

– Non-competing ISVs, IT departments, etc.

• ThreeWill SharePoint Development Services

• http://www.threewill.com/spds

Conclusion

• SharePoint 2010 development represents an opportunity for ISVs to reach new customers

• SharePoint 2010 development permits IT shops to make the most of their investment

• ThreeWill can provide the expertise to get you started on SharePoint 2010 development

• Download the accompanying whitepaper from http://www.threewill.com/whitepaper

Wrap-up

• Q & A

• Fill out post-event evaluation for chance to win an iPad - winner will be announced later today on Facebook and Twitter (go to www.threewill.com and click on icons)

• Thanks to Rover Apps!

Thank you for attending!

John B. Underwood Technical Evangelist, ThreeWill · 2017-06-01 · Benefits of SharePoint 2010 as a Product Platform John B. Underwood Technical Evangelist, ThreeWill Audio options

Documents

COL Paula Underwood

LUIS PALAU Evangelist Author m.sslon YORK MOORE Evangelist.....

Grover Underwood

Underwood Tidings - April 2010

Culture By Dalton Underwood

Underwood Repair Manual

UNDERWOOD THE SPRITZ

Underwood - GDM

Carrie Underwood

How to Use the Underwood Standard Portable...

Underwood Letterpress Wedding Lookbook

Underwood Leg190

Underwood esri serug

Steve Underwood - Harvard University

How to Use the Underwood Standard Portable...

Carrie Underwood - Play On