successful cms & ecm strategies

Technology Presentation 1

Successful CMS Strategies

08-may-2008


David Nuescheler Chief Technology [email protected]

mailto:[email protected]


3

Day Software “Content pure-play” specialist

Headquarters – Basel, Switzerland & Newport Beach, CA

Founded 1993 in Basel, Switzerland

Publicly Traded - SWX:DAYN, OTC:DYIHY

Global Support Centers

+120 highly specialized employees

Fast, organic and healthy growth


Core BusinessWCMS high-profile websites

6

250+ Brand Name Customers



David NueschelerJackrabbit Committer / [email protected]





Technology Presentation

Apache Software Foundation

One of the worlds most successful Open Source Initiatives Well-known for the Apache WebServer:

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

#1 for over twelve years and counting.

8




David NueschelerJSR-170 Spec [email protected]








Java Community Process

Open Software Standards Organization

Funded by Sun Very solid performance and track record in

defining and implementing standards

10




David NueschelerJSR-170 Spec [email protected]

focus








1

Agenda: Successful CMS Strategies

2 3

cms today: silos & lock-in.

successful cmsstrategies

why should I care?


1


2 3



why should I care?

Content-Centric Infrastructure 14

Sep-04-07

Application EApplication DApplication CApplication B

Today: “The Content Problem” Content Isolated in Silos

Application A

Repository E

Repository D

Repository C

Repository B

Repository A

Accounting Marketing Legal HR R&D

Content-Centric Infrastructure

“The Content Market”

15

“The Content Market”

16

Apache Jackrabbit Oracle XML DBExo

ECMS PlatformMicrosoft

Sharepoint OpenText Livelink

Day CRX IBM FileNet P8 Xythos Repository Alfresco ECM Vignette V7

Interwoven Repository IBM CM / Domino EMC Documentum

+hundreds moreregisteredSaperionArchive

So many

Vendors to

choose from...


Reality Check!

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

Task

Reality CheckList all documents in a folder

18

<%childCount = node.getContentCount();for(int i=0;i<childCount;i++) { IContent child = node.getContent(i); Property title = child.getPropertyByName("Title"); %><%= title.getValue() %> <%}%>

<%LAPI_DOCUMENTS documents

= new LAPI_DOCUMENTS(session);

LLValue childTable = new LLValue();

documents.ListObjects(volumeID, folderID,

null, null, LAPI_DOCUMENTS.PERM_SEE, chi

ldTable);

Enumeration children = childTable.enumerateValue

s();

while(children.hasMoreElements()) {

LLValue child = (LLValue)e.nextElement()

;

String title = child.toString("Name");

%><%= title %> <%

}%>

<%fndocs = new IFnObjSetDualProxy(

fnfolder.getContents(idmFolderContent.idmFolderContentDocument));

int numDocs = fndocs.getCount();for (int i = 1; i <= numDocs; i++) {

IFnDocumentDual fndoc = new IFnDocumentDualProxy(fndocs.getItem(new Integer(i)));

IFnPropertiesDual propset = fndoc.getProperties();

IFnPropertyDual idmTitleProp = propset.getItem("Title");

String title = idmTitleProp.getValue();

%><%= title %> <% if (comCleanup) { cleaner.release(fndoc); }}%>

<%IDocuments documents =

new IDocumentsProxy(binder.getDocuments());

documents.cache();

int documentCount = documents.getCount();

for (int i = 0; i<documentCount; i++) {

document = new IDocumentProxy(docume

nts.getItemByIndex(i));

String title = document.getTitle()

%><%= title %> <%

}%>

<%PageIterator children = page.getPages();while (children.hasNext()) { Page child = children.nextPage(); Container toplevel = child.getContent(); Atom title = toplevel.getAtom("Title"); %><%= title %> <%}%>

+800


CMS Market


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

21


Bottom line:

22


1


2 3



why should I care?

Everything is Content.1

Content is forever!


Vision

Data


Successful CMS Strategies:

25

soft-factors:people& process

hard-factors:technology selection,

architecture!

“Best Advice”:

Standards, Standards, Standards


Now what!?

26

based on the

previously

established

consensus...


Now what!?

27

An"ew S. Tanenbaum, Computer Networks

The nice thing about standards is that there are so many of them

to choose from.

...not in CMS


Industry Standards

170

283


Industry StandardsJSR-170 Progress

JSR-170 Final Approval Ballot

approved

released:

mid 2005


JCR AdoptionTracking success

Known Compliant Repositories(* partially using 3rd party connectors)

31

Apache Jackrabbit Oracle XML DBExo

ECMS PlatformMicrosoft

Sharepoint OpenText Livelink

Day CRX IBM FileNet P8 Xythos Repository Alfresco ECM Vignette V7

Interwoven Repository IBM CM / Domino EMC Documentum

+hundreds of TCKsregisteredSaperionArchive

Sourcemix Sourcemix

Percussion Rhythmix Lutece

Portal

QuickWCM WCMS

Jahia Framework

Hippo CMS

InfoQ Online CommunityNuxeo ECM

Sakai E-learning

TYPO3 v5.0 WCMGX WebManager

Exo ECMS Platform

Liferay Enterprise Portal

Artifactory Maven Proxy

IBM FileNet WebSiteManagerApache James

medic-2-medic mapofmedicine

Day Communiqué WCMS

Apache Tapestry

Day Communique Collab

QSLabs ComplianceApache

Cocoon

Alfresco ECMSApache Sling

Mindquarry Collaboration

Day Communique DAM


magnolia WCMS

JBoss Portal

Some known JCR Applications...

Sun OpenPortal Interface 21

Spring Framework

Fast Enterprise SearchOracle PortalBEA Portal

JCR - Weatherforcast-5°

2008 2009-8°

2010-12°

Commodity Infrastructure

StandardChaos


Enterprise SoftwareMarket Evolution

34

Operating Systems

WebServers

Relational Databases

J2EE Application Servers

Content Industry


Free your content... and put it to work.

35

proprietarysilos:Liabilities

open standard

repositories:

Assets

NO INTEGRATION


WCM

JCR CompliantContent Repository

IndustryStandard (JCR)

connector

connector

connector

connector

DAM Collab

36

The Content Warehouse.

Portal

JCR

Applications

JCR Infrastructure



1


2 3


why should I care?


Why should I care?Two killer Use Cases.

38


Java vs. Sharepoint

39


Java vs. Sharepoint

40


Java vs. Sharepoint

41


Why should I care?Two killer Use Cases.

42


Sep-04-07

Application EApplication DApplication CApplication B

Problem Content Isolated in Silos

Application A

Repository E

Repository D

Repository C

Repository B

Repository A



Sep-04-07

Strategy Enterprise 2.0 & the Future of ECM

Application EApplication DApplication CApplication BApplication A

JSR-170 API

Web Frontend

Repository E

Repository D

Repository C

Repository B

Repository A


CIO: why?


Sep-04-07

SolutionStandards-Based Content Repository

Java Content Repository

Web Frontend

Application EApplication DApplication CApplication BApplication A

JSR-170 API



Repository Consolidation

ConsolidateTurn off legacy Repositories

SynchronizeKeep your repositories in sync

UnifyAccess all your repository through a standardized API1

2

33


Situation Today

CMS Vendor (A)

DMSVendor (B)

DMSVendor (C)

“The Content Silos”


Unification

1

CMS Vendor (A)

DMSVendor (B)

DMSVendor (C)

JSR-170 API

AppA AppB AppC AppD …

JSR-170 Connectors, Level 1 +From Day Software, Native or Third Party


Synchronization

CMS Vendor (A)

DMSVendor (B)

DMSVendor (C)

JSR-170 API


JSR-170Repo

2


Consolidate

CMS Vendor (A)

DMSVendor (B)

DMSVendor (C)

JSR-170 API


JSR-170Repo

33



1


2 3


why should I care?


1


2 3


why should I care?


If you remember only one thing.

54

Do not create new information silos.1

proprietary

this is

“2008”