sharepoint 2010 integration and interoperability: what you need to know

70
SharePoint 2010 Integration and Interoperability: What You Need to Know @rharbridge #SPSVB Presented By: Richard Harbridge

Upload: richard-harbridge

Post on 02-Jul-2015

4.001 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: SharePoint 2010 Integration and Interoperability: What you need to know

SharePoint 2010Integration and Interoperability:What You Need to Know

@rharbridge #SPSVB

Presented By: Richard Harbridge

Page 2: SharePoint 2010 Integration and Interoperability: What you need to know

Who am I?

Page 3: SharePoint 2010 Integration and Interoperability: What you need to know

Our Goal Today…

From Here To Here

Page 4: SharePoint 2010 Integration and Interoperability: What you need to know

What we will be talking about…1. Business Data Challenges2. SharePoint’s Important Interoperability3. What is the BCS?

• External Content Types• External Columns• External Lists• Extensibility and Tooling

5. Limitations of BCS

4. Demonstration

Bonus!

Page 5: SharePoint 2010 Integration and Interoperability: What you need to know

Business Data Challenges

Page 6: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Business Data in an Enterprise

Customers FinancialQuality OperationsSuppliersCustomers FinancialQuality OperationsSuppliers

Users

IT

High Overhead (Maintenance, Security)High Integration Costs (Custom)

High Training CostsHigh Dissatisfaction

Redundant Data and Processes!

Page 7: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Challenges with Business DataChallenge IT End User

Higher Overhead for IT to Service User Requests

Multiple Places to Search

Multiple Places to Administer and Maintain

Multiple Places to Manage Content

Multiple Places to Secure Information

High Data Integration Costs (Often 100% Custom and One Offs)

Silos/Islands of Data Lead to Redundant Data or Processes

Multiple Interfaces; Dissatisfaction and Higher Training Costs

Higher Operational and Compliance Risk

Direct ImpactIndirect Impact

Page 8: SharePoint 2010 Integration and Interoperability: What you need to know

The Outcome

There are challenges that disparate and disconnected business data systems cause.

Page 9: SharePoint 2010 Integration and Interoperability: What you need to know

What to watch out for…

No system, product or application can completely solve business data

challenges.

People

Process

Technology

Page 10: SharePoint 2010 Integration and Interoperability: What you need to know

SharePoint’s Important Interoperability

Page 11: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

“Interoperability is the ability of a system.. to work with other systems.. without special effort on the part of the customer.”

What the heck is Interoperability?

(IHN-tuhr-AHP-uhr-uh-BIHL-ih-tee)

How?

Page 12: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

How do we achieveInteroperability?

2. By making use of a "broker" of services that can convert one system’s interface into another system’s interface "on the fly".

1. By adhering to published interface standards. Does SharePoint do this?

What about this one?

SPOILER ALERT!

Page 13: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

SharePoint Interoperability

Page 14: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Is it a UI Platform?

Page 15: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Why would we use SharePoint as a User Interface Platform?

Page 16: SharePoint 2010 Integration and Interoperability: What you need to know

Consistent User Experience Across Browsers

Well.. Almost.

Page 17: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

It’s a UI Platform1. By adhering to published interface standards.

Page 18: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

A UI Platform Bonus?Bonus!

Page 19: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Leverage Office and SharePointInterface Familiarity

Page 20: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Is it an Identity Platform?

Page 21: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Why would we use SharePoint as an Identity Platform?

Page 22: SharePoint 2010 Integration and Interoperability: What you need to know

Because Claims is Awesome

Connect with 3rd Party Authentication ProvidersConnecting with a Non Windows Integrated Authentication driven web site.

Delegation with Back-End SystemsShowing data from another server on a SharePoint web page.

Page 23: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Claims UsesConsistent Standards

*Doesn’t actually support SAML Protocol (SAMLP)

1. By adhering to published interface standards.

Page 24: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

It’s an Identity Platform

Page 25: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Is it a Search Platform?

Page 26: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Why would we use SharePoint as a Search Platform?

Page 27: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Query a 3rd Party Search Engine Using SharePoint UI

Federate Queries to Multiple Search Systems…

Page 28: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Index Content from a Range of Content Repositories

What does all of these?

Indexes Databases, Web Services or Custom Repositories

Provides Consistent Access to External Content

Has SharePoint Designer and Visual Studio Plug-ins

B

C

S

_ _ _B C S

Page 29: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

A Search Platform Bonus!Bonus!

Page 30: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Have you heard of OpenSearch?• Standard (Creative Commons) for syndication and

aggregation of search results• Syntax for executing queries• Results returned in RSS/ATOM + extensions• Supported by Microsoft Search Server 2008

Clients: Windows 7, IE, FireFox, Chrome, SharePoint …Providers: Amazon, Flickr, Wikipedia, SharePoint…

1. By adhering to published interface standards.

Page 31: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

It is a Search Platform

Page 32: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Is it a Data Access Platform?

Page 33: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

SharePoint Does a Great Job of Accessing SharePoint Content!

Page 34: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

What about External Systems and Content?

_ _ _B C S

Page 35: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

A Data Access Platform Bonus!Bonus! x 2

Page 36: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Content Management Interoperability Services

CMIS specification provides a Web services interface that: Is designed to work over existing repositories enabling

customers to build and leverage applications against multiple repositories—unlocking content they already have

Decouples Web services and content from the content management repository, enabling customers to manage content independently

Provides common Web services and Web 2.0 interfaces to dramatically simplify application development

Is development platform and language agnostic Supports composite application development and mash-up by

the business or IT analyst

A platform that allows you to build against multiple technologies without knowing anything about how all the API’s work. (If you know CMIS.)

Microsoft has been implementing this from both a client and provider perspective.

Not available “in the box”. Available via SharePoint Admin Toolkit

Page 37: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

And then there’s RESTAccess to SharePoint Lists and Document Libraries…

• RESTful interface over HTTP • Uses the ADO.NET Data Services interface conventions• Feature rich: retrieve, update, browse data using

just URLs and XML/JSON• Low barrier of entry. If you have an HTTP stack

you can use it.

Visual Studio Integration…• Entirely built on top of the open RESTful interface• No client is required• Visual Studio creates proxies, visualizes schemas,

provides LINQ support etc.

Page 38: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

SharePoint has Interoperability

Some might even say it has storage interoperability or that OData is a standard… But the coolest part of interoperability?

2. By making use of a "broker" of services that can convert one system’s interface into another system’s interface "on the fly".

Page 39: SharePoint 2010 Integration and Interoperability: What you need to know

The Outcome

SharePoint is a growing Interoperable UI, Identity,

Search, and Data Access Platform.

Page 40: SharePoint 2010 Integration and Interoperability: What you need to know

What to watch out for…

Remember this?“Interoperability is the ability of a system to work with other systems without special effort on the part of the customer.”

without special effort

Page 41: SharePoint 2010 Integration and Interoperability: What you need to know

What is the BCS?

Page 42: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

BCS in Office Client

Persistence

Store

Data

Cubes

SAP ORACLE SiebelSQL

Custom .NET

assembly

Identity Federation

serviceBCS in SharePoint

BCS MetaData Store

External data

AS Custom

Connector

Client to Backend

Direct Connection

Client DataCache

DB

Connector

WCF /WS

Connector

.NET

Assembly

Connector

SharePoint Client

You could look at this diagram…

Page 43: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

Or this simplified one…

Page 44: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

External Content Types

Describes:• Structure of the external

system (Fields, Methods, Connection)• How this data behaves within

SharePoint and Office

Added to the BCS Service Through:• SharePoint Designer• Visual Studio 2010• Via an Import into the Business Data

Connectivity Service as part of a model

Manage and Re-Use from a Central Location

Page 45: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

External Lists

The external content type is leveraged in a variety of ways…

Such as for Exposing External Data as an External SharePoint List

Full CRUD capability Familiar UI and NavigationSort, Filter, GroupProgrammatic Access via SPList OMProfile Page for Each ItemFormAuto-generated OOBUpsize to InfoPath

Can be Taken “Offline”

Page 46: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

Offline Lists

External Lists also be leveraged as Offline “Lists”

Or Connected to Outlook as Contacts, Tasks, Calendars and Posts

Page 47: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

Office Applications and Search

w/ Code

External Content Types can also be leveraged in…

Many other Office Applications (or Custom Applications)

Or Leveraged to allow for External Data Searching or Filtering

Page 48: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External Data

External Content Types

External ListsSharePoint

Workspace w/ InfoPath Forms

Outlook Forms and Task Panes

Office Applications

Search Results

Bonus! Integration Webparts

w/ Code

Bonus!

Web PartsExternal Data ListExternal Data ItemExternal Data Item BuilderExternal Data Related ListExternal Data Connectivity FilterChart Web Part (New)

Integration Webparts

Page 49: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Didn’t those webparts work with the BDC?

Page 50: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

So what’s different? (Besides the Chart Control?)

Read/Write CapabilityClaims AwareConnect via ADO/SQL, WCF/WS, .Net Assembly and Custom ConnectorsBatch and Bulk Operation Support

BDC is still used for search indexing connectors in 2010 they added blob, incremental crawl and item level security.

They added symmetrical server and client runtimes. Allowing them to connect from client or server directly to external data.

SQL CE database is used to cache external data which allows for “cached mode” behavior on external data basically creating a rich client cache.

Page 51: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

How do I actually build it out?

Page 52: SharePoint 2010 Integration and Interoperability: What you need to know

Intermediate AdvancedSimple

• Create Reusable Components (UI parts, ECTs, Actions)

Out-of-box• Surface data in

External Lists

• Connect those lists to Outlook, SPW

• External Data Columns

DeveloperPower User

NO CODE

Advanced Developer

CODE

Where things fit.

“NO CODE”

Page 53: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

1. Discover your Data Source• Database

• Web services

• .NET type

2. Map Operations to Data Source• Create, read, update, delete, lookup

3. Connect to SharePoint and/or Office • External List

• Contact

• Task

• Appointment

• Post

SharePoint Designer Process

Page 54: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Visual Studio Process

w/ Code

Page 55: SharePoint 2010 Integration and Interoperability: What you need to know

The Outcome

The BCS has a bunch of new capabilities bundled with some old enhanced BDC ones.

Page 56: SharePoint 2010 Integration and Interoperability: What you need to know

What to watch out for…

Selecting the right tool is important. Practice makes perfect.

Page 57: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

That’s a lot of information!

Page 58: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

Page 59: SharePoint 2010 Integration and Interoperability: What you need to know

Demo!

Page 60: SharePoint 2010 Integration and Interoperability: What you need to know

The Outcome

You saw how the BCS can be leveraged in SharePoint Designer and in the SharePoint

UI.

Page 61: SharePoint 2010 Integration and Interoperability: What you need to know

What to watch out for…

Don’t assume the tools will significantly reduce the time it takes

to ‘integrate’. It typically reduces time to ‘interface’.

Page 62: SharePoint 2010 Integration and Interoperability: What you need to know

What are BCSLimitations?

Page 63: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

General BCS Limitations

• No Write support for BLOB• You cannot write back to BLOB fields using BCS

unless you write your own method.• You can access BLOB columns by defining a

StreamAccessor method and presenting the external data via the BCS Data List web part by checking the Display stream fields property.

Page 64: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External List Limitations• Workflows cannot be associated with external lists

• Workaround: You can use the external data columns and manipulate it that way.

• No RSS feed support for external lists• No REST based access for external lists

• http://sharepoint/_vti_bin/ListData.svc does not support external lists• LINQ to SharePoint spmetal.exe does not support external lists• Cannot configure alerts for external lists• Cannot export external list items to Excel (using the Export to Excel

feature), Create Visio Diagram, Open with Access or Open with Project• Versioning cannot be configured on external lists• Version History is not available on external lists• Datasheet view cannot be used in external lists

• XSLT is Supported (So you can basically make your own.)

External Lists

Page 65: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

External List Limitations Continued…

• Ratings feature is not supported for external lists• Information policies cannot be configured on external lists• Item-Level permissions are not available for external lists• No item or field level validation (without InfoPath)• Lookups don’t work on any column but ID• No attachments.

External Lists

Page 66: SharePoint 2010 Integration and Interoperability: What you need to know

@rharbridge #SPSVB

• You cannot create a site column of type ‘External Data Column’• External data columns can be created only as list based

columns and cannot be consumed in site level content types

Bonus! External Column Limitations

Bonus!

Page 67: SharePoint 2010 Integration and Interoperability: What you need to know

The Outcome

You now know more about the limitations of BCS and will make fewer

assumptions.

Page 68: SharePoint 2010 Integration and Interoperability: What you need to know

What to watch out for…

Some of the many limitations mentioned make sense. Think

carefully before you build a ‘workaround’.

Page 69: SharePoint 2010 Integration and Interoperability: What you need to know

1. Business Data Challenges2. SharePoint’s Important Interoperability3. What is the BCS?

External Content TypesExternal ColumnsExternal ListsExtensibility and Tooling

4. Limitations of BCS

1. The Challenges Aren’t All Technology Challenges2. Interface, Identity, Search and Data Access Platform3. A Set of Powerful Connection Capabilities

Structured Types of External ContentLeveraging External Content with Internal ContentInteract Like SharePoint ListsExtensibility/Tool Range from UI to SPD to VS 2010

4. Good Enough and Better than Most Options

What we talked about…

Page 70: SharePoint 2010 Integration and Interoperability: What you need to know

Thank You!Thanks to Organizers, Sponsors and You for Making this Possible.

Questions? Ideas? Feedback? Contact me:

Twitter: @rharbridge

Blog: www.rharbridge.com

LinkedIn: www.linkedin.com/in/rharbridge

Email me at: [email protected]

My company: www.Allin.com