Day @ cio-gipfel 2007

Workshop:
Umsetzung einer erfolgreichen CMS
Strategie

David Nuescheler
CTO / Day Software
JSR-170 & JSR-283 Spec Lead
Member of the Apache Software Foundation

Content-Centric Infrastructure 1

Before I start:

David Nuescheler Chief Technology Officer
david.nuescheler@day.com


Core Business: WebCMS
Showcase: Mercedes-Benz


Customers
Automotive Industry Transport / Travel / Logistics Chemical / Healthcare

Financial Services Media / Telco Consumer / Services Public Services


Before I start:


David Nuescheler
Jackrabbit Committer / Member
uncled@apache.org


Apache Software Foundation
 One of the worlds most successful Open Source Initiatives

 Best known for the Apache Webserver:

“Apache WebServer has been the most popular web
server on the Internet since April 1996.”

#1 for over ten years and counting.


Before I start:

David Nuescheler
JSR-170 Spec Lead
jsr-170-comments@jcp.org

David Nuescheler
uncled@apache.org


Java Community Process
 Open Software Standards Organization

 Funded by Sun
 Extremely solid performance and track record in
defining and implementing standards


Before I start:

focus

David Nuescheler
JSR-170 Spec Lead
jsr-170-comments@jcp.org

David Nuescheler
uncled@apache.org


Sep-04-07

Agenda

ECM Today: Silos and Lock-in.
Standards, Standards, Standards...
Why should I care?
Tomorrow is Today: Demo
Q&A


Sep-04-07

Problem
Content Isolated in Silos

Accounting Marketing Legal HR R&D

Application A Application B Application C Application D Application E

Repository Repository Repository Repository Repository
A B C D E


Analysts & Reports
“So many to choose from”

So many
reports, so
little
agreemen
t!

Vendors “So many to choose from”

Exo Microsoft
Apache Jackrabbit Oracle XML DB OpenText Livelink
ECMS Platform Sharepoint

So many
vendRepository Alfresco ECM
Xythos or
s, so little
Day CRX IBM FileNet P8 Vignette V7

agreemen
t!
Interwoven +hund
IBM CM EMC Documentum
Repository reds m
ore

Reality Check!

Task

write a “code snippet” that lists all the
documents in a folder by “title”.

* ...Code Snippe
ts courtesy of
the
JSR170 Exp
- ert-Group.


Reality Check
List all documents in a folder
ession);
new LAPI_DOCUMENTS(s
<%
OCUMENTS documents =
LAPI_D
new LLValue();
LLValue childTable = ,
s(volumeID, folderID
documents.ListObject ERM_SEE, childTable);
UMENTS.P
<%
null, null, LAPI_DOC lues();
ildTable.enumerateVa
childCount = node.getContent
eration children = ch
Count(); Enum
reElements()) {
for(int i=0;i<childCount;i
while(children.hasMo
++) { ;
alue)e.nextElement()
LLValue child = (LLV
IContent child = node.getC
ontent(i);
toString(quot;Namequot;);
String title = child.
Property title = child.get
PropertyByName(quot;Titlequot;);
%
%><%= title.getValue() %><
%><%= title %> <%
}
}
%>
%>
<% <%
fndocs PageIterator children
= new = page.getPages();
IFnObj while (children.hasNex
SetDua t()) {
lProxy
Page child = children
(
fnfold .nextPage();
er.get
int nu Conten Container toplevel =
mDocs ts(idm child.getContent();
=
for (i
nt i = fndocs.getCo Folder Atom title = toplevel
Conten .getAtom(quot;Titlequot;);
unt(
1; t.idmF
IFnDoc i <= numDocs ); %><%= title %> <%
olderC
ontent
umentD ; i++) }
Docume
ua {
new IF
nDocum l fndoc = nt));
%>
entDua
IFnPro lProxy
pertie (fndoc
sD
IFnPro
pertyD ual propset s.ge
= fndo tItem(new In
ual id
String mTi c.g te
title
= idmT tleProp = pr etProperties ger(i)));
%><%=
ti ;
i
if (co tle %> < tleProp.getV opset<% etIte (); er.getDocuments())
.g
m(quot;Tit cuments = new IDocumentsProxy(bind
mClean % alue()
; ocuments dolequot;);
up)
cleane ID
r.rele {
documents.cache();
} ase(fn ();
documents.getCount
doc);
}
t documentCount =
in {
documentCount; i++)
%> ByIndex(i));
for (int i = 0; i< (documents.getItem
ocumentProxy
document = new ID
ment.getTitle()
String title = docu

+800
><%
%><%= title %><br/
}
%>

Is there any agreement?

Yes, Real-life architecture!


Is there any agreement?
Yes, Real-life architecture!

Content Management
Applications
wcms

???m

????

????
??m
dam
dms

bpm

rm
Existence of
Proprietary
a “ ontent rep
c
Interface
ository”
.
Content ...and f
eatureset
Repository


Bottom-line:

CMS is still a very young,
fast evolving market!
many ven
dors,
frequent c
hanges
in the ma
rket,
proprieta
ry!


Sep-04-07

Agenda

Why should I care?
Q&A



Andrew S. Tanenbaum, Computer Networks

The nice thing about standards is that
there are so many of them to choose from.

Not in CM
S!


Standards, Standards, ...
 In CMS and content repositories there is currently only
one relevant open standard:

called

JSR-170 == JCR

 JCR focusses on the Content Repository.


What is a content repository?
Best of both worlds

filesystem
database
hier-
archi
integ
es
re
rity structu
read streams

tx access
write locking
query control

multi-
value ning
un-
versio
obser-
“full-
structured
sort vation
text” order
content repository
content
Content-Centric Infrastructure

What is JSR-170?
from the JSR-170 submission

“The API should be a
standard, implementation
independent, way to access
content bi-directionally on a
granular level within a
content repository.”
submitted in
jan- 001
2


Level 1 : Features

Read only
Simple & Covers a large number of usecases

Level1
Fine & Coarsegrained
Content Items Small to Large

Hierarchical
Parent child relationships, Sort order

Structured
Strong typed information

PropertyTypes
String, Binary, Numbers, Calendar, ...

L1
NodeTypes
Introspect complex Content Structures

Query (XPath)
Search and query

Export
XML Content Export


Level 1: Applications
 Typical Level-1 only Applications:
 CMS-Templates, Content Delivery
 Display Portlets
 Repository Export
 Reporting Applications
 Federated Repositories

 Overwhelming Majority of Application Source
te+
Wri Code is written using Level-1 calls

Read
Sear &
ch


Level 2 : Features
Level 2

Write
Save changes to a repository

Unstructured
Support for weakly or unstructured Content

L2
Import
Standardized Finegrained Content Import

Referencial Integrity
Reference Tracking and Integrity

AccessControl
Introspection


Level 2: Applications
 Typical Level-2 Applications:
 Entry Level Content Management
 Entry Level Document Management
 Workflow
 Collaboration
 Content Aggregation (Content Warehouse)
…


Advanced Features

Versioning
Workspaces, Merge, Update, Label, ...

JTA Support
(XA) Transactions

Observation
Monitor changes in the Repository

Adv
Query (SQL)
Search the Content Repeository using SQL

Locking
Session based and persistant


Sep-04-07

Functional Overview
Compliance Levels

Versioning Locking

Optional
Transactions Query (SQL) Observation

Unstructured Access Control

Level 2
Write Import Referencial Integrity

Read Hierarchical Finegrained

Query (XPath) Structured Export
Level 1
Binary, Text, Date, Numbers


Industry Standards

170

283


Industry Standards
JSR-170 Progress

sed:5
relea200
pproval Ballot
JSR-170 Final A mid

ed
ov
pr
ap


JCR Adoption
Tracking success


Known Compliant Repositories
(* using 3rd party connectors)

* *
Exo Microsoft
Apache Jackrabbit Oracle XML DB OpenText Livelink
ECMS Platform Sharepoint

*
Day CRX IBM FileNet P8 Xythos Repository Alfresco ECM Vignette V7

any ors
ow mvendd?
HSe
* DBMou ne
R do y
+hund
*
Interwoven rs
regiede of TCKs
IBM CM EMC Documentum
Repository st red

Some known JCR Applications

Fast
BEA Portal Oracle Portal Enterprise Search
Sun JBoss Portal Interface 21
OpenPortal
Day Communique Spring Framework
DAM
magnolia WCMS Day Communique
Apache Sling
Collab
Mindquarry
Alfresco ECMS
Collaboration Apache Tapestry
QSLabs
Apache Day Communiqué
Compliance
Cocoon WCMS IBM FileNet
medic-2-medic WebSiteManager
Artifactory
Apache James mapofmedicine
Maven Proxy
Exo
TYPO3
ECMS Platform
GX WebManager v5.0 WCM
InfoQ Hippo Liferay
Nuxeo ECM Online Community CMS Enterprise Portal
Jahia Sakai
Framework E-learning
Percussion QuickWCM
Rhythmix Sourcemix
WCMS Lutece Sourcemix
Portal

JCR - Weatherforcast
-5° -8° -12°
2009 2010
2008

Sep-04-07

Problem



A B C D E


Sep-04-07

Strategy
Enterprise 2.0 & the Future of ECM


Web Frontend


JSR-170 API

A B C D E


Enterprise Software
Market Evolution
Operating Systems

WebServers

Relational Databases

J2EE Application Servers

Commodity
Infrastructure
Content Industry
Standard
Chaos


Sep-04-07

Agenda

Why should I care?
Q&A


Why should I care?
Two killer Showcases!

1
Java vs. Microsoft Sharepoint

2
Repository Consolidation


Java vs. Sharepoint

We are using or
We develop custom
plan to use Microsoft
Applications in Java /
Sharepoint in our
J2EE.
organization.


Java vs. Sharepoint

Mission Critical Applications Mission Critical Information

Java J2EE Business Microsoft
Applications Sharepoint


Java vs. Sharepoint

Mission Critical Applications Mission Critical Information

JCR Connector
for Sharepoint

Java J2EE Business Microsoft
Applications Sharepoint


Why should I care?
Two killer Showcases!

1
Java vs. Microsoft Sharepoint

2


Reality Check
List all documents in a folder
ession);
new LAPI_DOCUMENTS(s
<%
OCUMENTS documents =
LAPI_D
new LLValue();
LLValue childTable = ,
s(volumeID, folderID
documents.ListObject ERM_SEE, childTable);
UMENTS.P
<%
null, null, LAPI_DOC lues();
ildTable.enumerateVa
childCount = node.getContent
eration children = ch
Count(); Enum
reElements()) {
for(int i=0;i<childCount;i
while(children.hasMo
++) { ;
alue)e.nextElement()
LLValue child = (LLV
IContent child = node.getC

JCR API
ontent(i);
toString(quot;Namequot;);
String title = child.
Property title = child.get
PropertyByName(quot;Titlequot;);
%
%><%= title.getValue() %><
%><%= title %> <%
<%
}
}
%>
NodeIterator children = node.getNodes();
%>
<% <%
while (children.hasNext()) { ile erator children = page.getPages();
fndocs PageIt
= new
IFnObj wh (chi
Node child = children.nextNode();ldren.hasNext()) extPage();
SetDua {
lProxy
Page child = children
(
fnfold .n
er.get
int nu
Folder Property title = child.getProperty(quot;Titlequot;);
Conten Container toplevel =
mDocs ts(idm child.getContent();
= fndo
for (i Atom title = toplevel
cs.get
nt i = Conten .getAtom(quot;Titlequot;);
Count(
%><%=mtitle %> <% } %><%= title %> <%
1; t.id F
IFnDoc i <= numDocs ); olderC
ontent
umentD
ual fn ; i++) { Docume
}
new IF nt));
doc =
nDocum %>
entDua
IFnPro lProxy
pertie
= %> tItem(new I
(fndoc
sD
IFnPro
pertyD ual propset s.ge
ual id
Stri fndo
ng tit
le = i mTitleProp = c.getPropert nteger(i)));
%><%= dmTi ies
pr
ti ;
if (co tle %> < tleProp.getV opset<% etIte (); er.getDocuments())
.g
m(quot;Tit cuments = new IDocumentsProxy(bind
mClean % alue()
; ocuments dolequot;);
up)
cleane ID
r.rele {
documents.cache();
} ase(fn ();

+800
documents.getCount
doc);
}
t documentCount =
in {
documentCount; i++)
%> ByIndex(i));
for (int i = 0; i< (documents.getItem
ocumentProxy
document = new ID
ment.getTitle()
String title = docu
><%
%><%= title %><br/
}
%>

Sep-04-07

Problem



A B C D E


Sep-04-07

Strategy
Enterprise 2.0 & the Future of ECM


Web Frontend


JSR-170 API

CIO:
y?
wh
A B C D E


Sep-04-07

Solution
Standards-Based Content Repository


Web Frontend


JSR-170 API

Java Content Repository



1 Unify
Access all your repository through a standardized API

2 Synchronize
Keep your repositories in sync

Consolidate
3 Turn off legacy Repositories


Situation Today

“The Content Silos”

DMS DMS
CMS
Vendor (C)
Vendor (A) Vendor (B)


Unification

1 JSR-170
Connectors,
AppA AppB AppC AppD …
Level 1 +
JSR-170 API From
Day Software, Native
or Third Party

DMS DMS
CMS
Vendor (C)


Synchronization

2
AppA AppB AppC AppD …

JSR-170 API

JSR-170
DMS DMS
CMS Repo
Vendor (C)


Consolidate

3 AppA AppB AppC AppD …

JSR-170 API

JSR-170
DMS DMS
CMS Repo
Vendor (C)


Consolidate


JSR-170 API

JSR-170
DMS DMS
CMS Repo
Vendor (C)


Sep-04-07

Agenda

Why should I care?
Q&A


Day Content Management

-2001
1998


Proprietary
Interface

ContentBus
Repository

-2005
2002


Industry
Standard (JCR)

connector
connector
CRX
JCR Compliant
Content Repository
connector
connector

-xxxx
2005

Day Content
DAM
Management

Industry
Standard (JCR)

connector
connector
CRX
JCR Compliant
Content Repository
connector
connector

xxxx
2007-

Day Content
DAM Collab
Management

Industry
Standard (JCR)

connector
connector
CRX
JCR Compliant
Content Repository
connector
connector

xxxx
2007-

Setup: “Holy Grail of Integration”

WCMS DAM Collab

tive
na R
JC s
Industry
Standard (JCR)
App
connector
connector
CRX
JCR Compliant
Content Repository
connector
connector
all the
apps share
the same
repository

If you remember one thing!

1 Standards-based CMS.
No Ve Long-term dation
ndor onsoli tegy
Lock- investment Ca
Str
in protection


Sep-04-07

Agenda

Why should I care?
Q&A


Day @ cio-gipfel 2007

Recommended

Recommended

More Related Content

What's hot

What's hot (13)

Similar to Day @ cio-gipfel 2007

Similar to Day @ cio-gipfel 2007 (20)

More from David Nuescheler

More from David Nuescheler (20)

Recently uploaded

Recently uploaded (20)

Day @ cio-gipfel 2007