SharePoint 2010's Killer App

SharePoint 2010 Killer App Who Let The Content Out?
Perth SharePoint User Group – Session 1, Thurs 15th April 2010
Mike Stringfellow
IT Consultant
Seven Sigma Business Solutions
mike.stringfellow@sevensigma.com.au

SharePointer or Serial Killer?
© Seven Sigma Business Solutions. www.sevensigma.com.au

SharePointer or Serial Killer –Results
For the record, here are my answers (draw your own conclusions!):
1.e (but fail so go with a), 2.c, 3.b, 4.d.
This might work for a presentation, but alternatively for teams a 'key learning styles' and 'dominant personality trait' survey will suffice, plus help you build a well balanced team!
Maybe those should be an OOtB site survey template?

About
Mike ‘ MOSSuMS’ Stringfellow
Seven Sigma Business Solutions
www.sevensigma.com.au
mike.stringfellow@sevensigma.com.au
20 years of IT in Perth, Sydney Dublin and the UK
IS Consultant, SharePoint specialist, .net programmer
Geek in denial: Do not have an Android or iPhone. Yet.
Blogs and rants on G’DayMOSSuMS

Session Agenda
Setting the SceneA more useful survey and what users hate
The UnveilingWho is that masked killer app?
Why Do we need it and what does it do for us?
Its Apps and Details What it is, and what it isn’t
A Calm Oasis Suck it up and get your JABS here
Care-factor Who does, and The Luddites
MicroSofty 2010 Why it’s a winner, but don’t forget 2007
The Timetable For MS and the REST of them
What it Looks Like Where to pigeonhole it
Get Ready What should we do about it
Further Resources Where to find out more
Questions And even maybe some answers

A More Useful Survey
To set the scene, ask yourself these questions:
How many content stores (silos!) do you have?
Do you have one interface to access them?
Can you search across them?
How do you intend to upgrade or change them?
Are you considering buying new tools to help with these issues?
Do you have a policy or architectural standard to guide these IM decisions?

The Vendors view
ECM
where information lives

The Users View
ECM
where documents go to die

What is that masked killer App?
OASIS CMIS
Organisation for the Advancement of Structured Information Standards
Content Management Interoperability Services
(not a punchy Manchester band)

(WHAT’S THE STORY) MORNING GLORY ?
Initiated, backed & driven by MS, EMC and IBM
– small suppliers then
Sorry, it’s actually an interface standard 
– a snappy name as usual
How would they name an e-book like the Kindle?
– Advanced Personal Productivity Leveraging Enterprise’s Information Publishing Access Device
APP LEIP AD?

“The last major enabler required for enterprise-wide
content and knowledge management” - Me
EMC CTO
“The SQL of content”
IBM Architect Al Brown
Standardisation grew RDB market 10 - 20 times. CMIS is this for ECM.
Targets core (“good enough”) DMS functionality
– a domain model over service and web style protocols
A Vendor standard
– can be added to for product ‘differentiation’
Open source vendor early adopters
– also iPhone, Android, Adobe AIR and browser plug-ins
Forward looking integrators and ecosystem suppliers
– they can see the opportunities

Why do we need it?
Nuxeo CMIS Overview (slide 8)

What will it do for you?
No more vendor lock-in
Maybe! As a vendor standard they are free to extend it, and there are some optional elements...
Easier upgrades and migrations
Content stored everywhere, accessed anywhere.
No more silos?
Probably not, as this depends on YOU. E.g. No central meta data definition, no directory/discovery service, no central policy/rule enforcement, no events…

What else will it do for you?
Language Agnostic & more than File Management
Addresses DMS to DMS, some Web content needs
Consumption in mash-ups, and search access
Can be bolted on to any existing app, or store.
CMIS already exists for files systems
How long before we see CMIS servers? Remember Pick, Oracle Internet FS, WinFS (ok, bad examples!)
May be added to browsers ‘OOtB’
Even if it only impacts ECM, that’s huge for all of us

CMIS – its applications
Can be Repository to Repository, App to Repository
For thin clients and browser mash-ups
Or migrations and transformations
Nuxeo CMIS Overview (slide 14)

CMIS – more applications
Or Vertical Content apps
Or maybe Web Content Publishing…
Word of Pie - The Point of CMIS slide deck (slide 9)

CMIS – even more applications
Or Enterprise-wide Federated Content and Search…
Word of Pie - The Point of CMIS slide deck (slide 23)

CMIS – in fact, content everywhere
Alfresco BPMS & ECM pdf (page 16)

CMIS – details
Version 1.0 voting closes on 30th April
Needs 49 yes and 0 no votes. Watch the votes here:
http://www.oasis-open.org/committees/ballot.php?id=1864
Don’t worry, I’m not going to open up the standard!
Once again, only if you have insomnia
Initial DMS and SOAP history shows in design details i.e. don’t expect web content bells and whistles
Includes an extension of SQL for search access.
But missing search result ranking when federating

CMIS – more details
Domain model has four primary data types
Documents, folders, relationships, policies, & collections.
Supports eight channels (aka web services)
Repository, Navigation, Object, Multi-Filing, Discovery, Relationship, Policies and ACL.
WCF delivers
MTOM, WS-I Basic Profile 1.1, Basic Security Profile 1.0 & WS-Security 1.1.
CMIS 2.0 requirements already being collated

What it isn’t (yet)
The interface provides the basics only.
That’s why CMIS 2.0 is a real opportunity.
It’s not complete for full ECM, Web Content Management, Source Control or Web 2
But it is already being co-opted & extended in these roles.
A magic bullet.
The integrators have recognised that it will give them access to a huge ecosystem, but the decisions around discovery, what the meta data means and where that data should go will still be their bread and butter.
Not the only game in town.

An OASIS , or get JABS here?
Just Another Bloody Standard?
Yes, but soon to be ubiquitous plumbing you just use
New technology?
Nothing new to see here – all proven and working today.
Vendor Support?
From the smallest to largest across many markets they are there, or will be soon. I’ll cover timelines &laggards later.
Alternatives?
There are other standards that will stay relevant & overlap, such as JCR, WebDav & ODMA, but they are different.

An OASIS , or get JABS here?
Obsolescence?
Eventually as CMIS 2 takes off. But V1 gets us most of the way there, which is a million miles from now. Is SQL dead?
An old problem who’s days have passed?
EMC CTO: estimates 80% of information is unstructured, but only 20-30% of that lives in organisations’ CM systems.
The problem is growing.
Of course, 87.3% of statistics are made up on the spot

CMIS 2.0
Areas for Improvement
Records
Process
Digital Asset
Web Content
Source Control
Collaboration
Social
Project Info
Specific Requests
Meta Data Model Customisations
Semantic and Web 2
WebDavand JSON
Event Model
Multiple Content Streams
Relationship Searches
Composite Support
http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10021&fixfor=10023
(Google: oasis issues cmis “proposals for 2.0”)

They Care
The 3 original CMIS proposers are ALL in the Gartner magic quadrant
EVERYONE in that quadrant is a sponsoring member (not my phrase!)

We Should Too
Oasis CMIS Contributing Organisations:
Adobe, Adullact, AIIM, Alfresco, Amdocs, Anakeen, ASG Software Solutions, Booz Allen Hamilton, Capgemini, Citytech, Content Technologies, Day Software, dotCMS, Ektron, EMC, ESoCE-NET, Exalead, FatWire, Fidelity, Flatirons, fme AG, Genus Technologies, Greenbytes GmbH, Harris, IBM, KnowledgeTree, Lexmark, Liferay, Magnolia, Mekon, Microsoft, Nuxeo, Open Text, Oracle, Pearson, Quark, RSD, SAP, Saperion, Structured Software Systems (3SL), Sun Microsystems, Tanner AG, TIBCO Software, Vamosa, and Vignette.
Are your vendors there? If not, why not?

The Luddites
Previous list shows only those actively contributing
Most customer responsive firms have announced support
Rage Against the Machine? There are areas that don’t get it. Yet.
The vertical market doesn’t see itself playing in this space – e.g. Coreworx.
Some ecosystem guys don’t see opportunity of bigger market, or focus on 1 supplier so miss the necessity.

The Laggards
And even one of the Big Boys
Last I asked, HP TRIM didn’t know about CMIS. I’ll let Jeremy Thake enlighten us, but here is confirmation from elsewhere:
http://wordofpie.com/2009/10/29:
<SNIP>“HP: Every year, I grow more disappointed. Tower TRIM was a fairly solid product. Even after the acquisition, it still is, but it feels static. While other vendors have taken their roots and made them an application on the ECM foundation, HP has kept RM as the foundation. This is fine for an Enterprise-class RM system, but not for an ECM system. Also, as of September, their field people did not even know what CMIS was.”</SNIP>

Gartner: SharePoint 2010 Steps Up to ECM Plate
Feb report: “Wait for SP 1”!
IM “policy-based information management” enterprises love
“Microsoft evolves SharePoint to include richer content management functionality. Gartner expects it to compete increasingly in the traditional high-end content management market”

Microsoft announced they will Support CMIS 1.0
The spec says they MUST support REST/AtomPub & SOAP
CMIS 1.0 in SP Admin Toolkit by “end of June 2010”
With V1 at end of April, they missed SP2010 release
Although stable, CMIS awaits ratification of V 1.0
SP2010 RTM, 16th April
On MSDN, 22nd April
Enterprise Agreement Customers, 27th April
Release date, 12th May
General Availability, 16th June

Who Wins?
SP2010 plays in ALL the markets / use cases
No other vendor does this in one product
Mash-ups, WCM, Publishing, DMS, Enterprise portals...
As ecosystem suppliers adopt CMIS, all those must have scanning, renditions and document control tools become available to SharePoint
It’s open interface + CMIS won’t loose it market share.
Big enterprise loves to reduce the number of suppliers.

Who Wins?
SP2010 is more useable and familiar
They might not love it, but they get it and are ‘empowered’
Whereas DMS/ECM systems are heavily controlled
Office integration (whether oData, CMISed or custom) is a major seller.

SP2010 Wins
SP2010 had made a big step into ECM territory
But the big ECM guys still think REST is a quick nap.
With SP as the front end to content & data, why keep moving it elsewhere?
But have to admit things like document sets and rendering abilities aren’t BOB, so the fight will continue.

SP 2007 & Others
SharePoint 2007
No Microsoft news if they will provide a pack to enable CMIS here
The issue is how much of the new SP2010 capabilities are used
Don’t expect it soon, &will have major implementation differences
Who else in SP 2007 and .net?
You can do it yourself . Use WCF and be selective
CodePlex has NCMIS and CMIS4SharePoint. Leverage them.
But they are immature and incomplete, and need to work together!
Microsoft’s CMIS in SP2007 demo was a half baked Silverlight webpart.
Therefore not representative of 2010 approach, and don’t copy them!
Others?
Open source (xCMIS, Apache Chem) have frameworks in Java, PHP, Python…

When for the REST of them?
2010
2011
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
JAN
FEB
oData 1 & 2
eZPublish 4.2 WCM
EntropySoft Connectors
SP2010 with oData on MSDN, 22/4
Oracle?
SAP?
OASIS CMIS v1.0 30/4
Alfresco 3.3
SeeUnity?
Vorsite?
Documentum CMIS support
Nuxeo (Apache Chemistry)
Open Text Lib Services & ECM 10
KnowledgeTree
SP2010 Admin Toolkit with CMIS 1.0
IBM Filenet P8 and Content Services
key
SharePoint
Competitors
Standards
Integrators and ecosystem products

What does it look like?
Services
Regardless of the binding, a repository must provide these sets of services:
• Repository Services
• Navigation Services
• Object Services
• Multi-filing Services
• Discovery Services
• Versioning Services
• Relationship Services
• Policy Services
• ACL Services

What does it look like?
Repository Services
getRepositories
getRepositoryInfo
getTypeChildren
getTypeDescendants
getTypeDefinition
Navigation Services
getChildren
getDescendants
getFolderTree
getFolderParent
getObjectParents
getCheckedOutDocs
Multi-filing Services
addObjectToFolder
removeObjectFromFolder
Object Services
createDocument
createDocumentFromSource
createFolder
createRelationship
createPolicy
getAllowableActions
getObject
getProperties
getObjectByPath
getContentStream
getRenditions
updateProperties
moveObject
deleteObject
deleteTree
setContentStream
deleteContentStream
Discovery Services
query
getContentChanges
Versioning Services
checkOut
cancelCheckOut
checkIn
getObjectOfLatestVersion
getPropertiesOfLatestVersion
getAllVersions
Relationship Services
getObjectRelationships
Policy Services
applyPolicy
removePolicy
getAppliedPolicies
ACL Services
getACL
applyACL
Common Service Elements
Paging, Change Tokens, Exceptions, ACLs, Retrieving additional info on objects in CMIS calls

What does its OM look like?
Jeff Potts: Getting Started with CMIS pdf (page 4)

What does it really look like?
ATOM pub example
GET:
http://localhost:8080/myRepository/someCo/marketing?
includeAllowableActions=true
RESPONSE:
…SNIP…
<cmis:allowableActions>
<cmis:canDeleteObject>false</cmis:canDeleteObject>
<cmis:canUpdateProperties>false</cmis:canUpdateProperties>
<cmis:canGetFolderTree>true</cmis:canGetFolderTree>
<cmis:canRemovePolicy>false</cmis:canRemovePolicy>
…
<cmis:canGetACL>false</cmis:canGetACL>
<cmis:canApplyACL>false</cmis:canApplyACL>
</cmis:allowableActions>
…SNIP…

Where it Sits
http://jonontech.com/2009/11/26/cmis-jcr-and-osgi-for-idiots

Where it Sits
“OData is a defined set of open extensions / conventions to AtomPub, documented and released under the OSP (Open Specification Promise)”
http://www.slideshare.net/uncled/content-management-standards

Get ReadyWhat should we do about it?
Pester your vendors
Demand it.
Get your procurers/purchasers on board
Make your IM guys aware
It could make their lives easier
Make your Architecture guys aware
It’s http, RESTful/SOAP, so they’ll be nice
But plumbing needs to be in - Kerberos
Explain the use-cases, and prepare for it.
Talk about SOA, Security, Directory...
What you might have to plan for
Your legacy stores (CMISify or migrate?)
Map meta-data definitions and ids
Policies/rules about routing documents
Code for it?
Its no fun. ‘Borrow’ from others.
Or use the best integration supplier.

Resources
OASIS
http://xml.coverpages.org/ni2009-10-30-a.html
Microsoft ECM Blog
http://blogs.msdn.com/ecm
http://wordofpie.com/2009/04/20/the-challenge-of-cmis/
http://wordofpie.com/2009/12/08/looking-at-cmis-1-0-thinking-of-2-0/
CMIS Developer Resources
http://www.cmisdev.org/cmis/
Alfresco’s CMIS Wiki
http://wiki.alfresco.com/wiki/CMIS
EMC’s early view – not JAS
http://chucksblog.typepad.com/chucks_blog/2008/09/cmis----its-not.html
Nuxeo CMIS Overview and Open Source ECM Home Page
http://www.slideshare.net/nuxeo/cmis-overview
http://www.nuxeo.com
DAY on Content Management Standards
http://www.slideshare.net/uncled/content-management-standards
CMIS 2.0 Proposals
http://tools.oasis-open.org/issues/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10021&fixfor=10023
Wikipaedia
http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services

Thankyou! Questions?

http://www.sevensigma.com.au	127
http://www.slideshare.net	44
http://115.112.206.131	1

SharePoint 2010's Killer App

by Mike Stringfellow on Apr 22, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 172

Statistics

SharePoint 2010’s Killer App — Presentation Transcript