This document provides an agenda and overview of CQ WCM and Connectors. It discusses upcoming releases of CQ WCM that will include features like author clustering, faceted search, and theme support. It also outlines Day's connector architecture, which uses JCR connectors to enable access to legacy content repositories via the JCR API and integrate them into the Day content infrastructure. A demo will show CQ WCM and connector capabilities.

1. CQ WCM and Connectors
Architecture and Demo
Jean-Michel Pittet, SVP Engineering, jmp@day.com
1

2. Jun-4-08
Agenda
Communiqé WCM update
WCM Demo
Connector Architecture
WCM & Connector Demo
Content-Centric Infrastructure 2

3. Day Product Portfolio
Web Frontend
CQ Delivery (Portal)
CQ CQ CQ SDK
CQ
WCM DAM
Collaboration Custom
Applications
JSR 170 API
Content
Connectors
CRX Apache
Jackrabbit
JCR Repository
Product Roadmap 3

4. Communiqué WCM 4.2:
Author clustering
Active Active, cluster
read and write,
cluster
in addition to
other options
Load
balancer
Characteristics: Shared:
Shared perisistence (Clustered) Journal
Pessimistic Locking Layer: RDBMS
Transactional
Product Roadmap 4

5. Communiqué WCM 4.2:
Japanese User Interface
Product Roadmap 5

6. Communiqué WCM 4.3:
Themes
 More Author Clustering: TarPM
 More Search: Faceted Search
 Permission sensitive caching
 Rollout Manager
 Include / sync connectors
 Bug fixes & Maintenance
June 4, 08 6

7. Communiqué WCM 4.3:
Author clustering
Active Active, cluster
read and write,
cluster
in addition to
other options
Load
balancer
Characteristics: Shared:
Shared perisistence (Clustered) Journal
Pessimistic Locking Layer: RDBMS
Transactional TarPM
Product Roadmap 7

8. Tar PM Clustering
Content-Centric Infrastructure 8

9. Communiqué WCM 4.3: Faceted Search
June 4, 08 9

10. Communiqué WCM 4.3: Faceted Search
Content-Centric Infrastructure 10

11. Jun-4-08
Agenda
Communiqé WCM update
WCM Demo
Connector Architecture
WCM & Connector Demo
Content-Centric Infrastructure 11

12. Jun-4-08
Agenda
Communiqé WCM update
WCM Demo
Connector Architecture
WCM & Connector Demo
Content-Centric Infrastructure 12

13. Day Product Portfolio
Web Frontend
CQ Delivery (Portal)
CQ CQ CQ SDK
CQ CQ
WCM DAM
Collaboration DMS Custom
Applications
JSR 170 API
CRX Content
Apache
Connectors
Jackrabbit
JCR Repository
Content-Centric Infrastructure 13

14. Jun-4-08
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
Content-Centric Infrastructure 14

15. Jun-4-08
Strategy
Enterprise 2.0 & the Future of ECM
Accounting Marketing Legal HR R&D
Web Frontend
Application A Application B Application C Application D Application E
JSR-170 API
Repository Repository Repository Repository Repository
A B C D E
Content-Centric Infrastructure 15

16. Jun-4-08
Product Portfolio
CQ Content Infrastructure Products
Day Virtual Repository
Day JCR Connectors
Currently available for: OpenText Livelink, EMC Documentum,

FileNet P8, IBM Lotus Notes, Microsoft SharePoint, Vignette
VCM, Interwoven TeamSite
Day Content Repository Extreme (CRX)
CRX Developer Edition

CRX Enterprise Edition

Content-Centric Infrastructure 16

17. Day’s Product Stack
Applications & Infrastructure
CQ Delivery (Portal)
CQ CQ CQ CQ CQ SDK
WCM DAM Collaboration WF Custom
Applications
JCR API (JSR 170 API)
Virtual Repository Layer
JCR JCR JCR
Connector Connector Connector
for... for... for...
CRX: Native JCR Repository
Legacy Repositories
Content-Centric Infrastructure 17

18. Communiqué WCM 4.2:
Connector Integration: JCR & Components
Product Roadmap 18

19. Jun-4-08
Day Virtual Repository
Based on ContentBus Architecture
Unifying and Consolidating Repositories
Single Point of Truth - Distributed Information, Unified Access
Embrace and/or Replace - Leverage Existing and/or Consolidate
Common Services for ALL Content
Content-Centric Infrastructure 19

20. Product and Technology Roadmap June 4, 08
What is a Virtualization?
Application
JCR API (JSR 170 API)
Virtual Repository Layer
Standard “Inter-workspace” communication using clone, update, merge, …
CRX
Workspace C
Workspace B
Workspace A
JCR
JCR
Native store
Connector
Connector
Legacy
Legacy
Data Repository
Data Repository
C
B
Content-Centric Infrastructure 20

21. Jun-4-08
JCR Connectors
JCR-Enabling Legacy Repositories
Unlocking content residing in proprietary repositories
and minimizing repository integration work
Content-Centric Infrastructure 21

22. Jun-4-08
What is a JCR Connector?
 A connector is a component “JCR-
enabling” an existing legacy data
source or repository without native
JCR API
JCR support.
JCR
 Thanks to the connector a legacy
Connector
data source or repository will be
accessible via the standard JCR
API and fit into a customer’s
standard-based infrastructure.
Legacy
Data Source
or Repository
Content-Centric Infrastructure 22

23. Jun-4-08
Connector Overview: Level 1+
Observation
Optional
Query (SQL)
Unstructured
Level 2
Access Control
Read Hierarchical Finegrained
Level 1
Query (XPath) Structured Export
Binary, Text, Date, Numbers
Content-Centric Infrastructure 23

24. Jun-4-08
JCR Connector Capabilities
 Read content, metadata, users, groups, group memberships
 Execute queries against repository
 Apply Access Control Lists (ACLs) to extracted content
 Observe content, metadata, users, groups, group
memberships
 Support full scans efficiently
 Incremental Updates
Content-Centric Infrastructure 24

25. Jun-4-08
JCR Connector Portfolio
Available JCR Connectors
 EMC Documentum v5.2.5 / v5.3
 FileNet P8 Content Mgr V3.5, 4.x
 Microsoft SharePoint 2003 – (MOSS 2007 planned)
 Vignette V7.3.0.5 (V7.3.1 planned)
 OpenText LiveLink v9.5 / v9.6 / v9.7
 Interwoven TeamSite V6.5
 IBM Lotus Notes v6.5 / v7.0
 WebDAV File System Client
 Day ContentBus
Content-Centric Infrastructure 25

26. Jun-4-08
Use Case Examples
Display and browse content stored in

different repositories using a single
user interface
Federated Search

3rd Party
CQ Apps
Content Virtualization

Products
or
(e.g. BEA,
Custom Apps Repository unification, sychronization

Oracle, FAST)
and consolidation
Repository Migration

JCR API (JSR 170 API)
Populate “Content Warehouse“

Multi-Repository development

Virtual Repository Layer environment with a single API
JCR JCR JCR
Connector Connector Connector
for... for... for...
Content-Centric Infrastructure 26

27. JCR view of IWOV
Jun-4-08 27

28. JSR-170 Connectors
e.g. Documentum Connector
Jun-4-08 28

29. Jun-4-08
Agenda
Communiqé WCM update
WCM Demo
Connector Architecture
WCM & Connector Demo
Content-Centric Infrastructure 29

30. Thank you
More questions:
jmp@day.com
Content-Centric Infrastructure 30