Authors/presenters in chronological order: (1) Roy Fielding; (2) David Nuescheler; (3) Craig Randall

1. Strengthening Adobe’s Enterprise Platform
with Day Software and Open Development
Roy Fielding | Chief Scientist, Day Software | @fielding
David Nuescheler | CTO, Day Software | @davidnuescheler
Craig Randall | Principal Scientist, Adobe | @craigsmusings

2. ©2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Topics
2
1
Open Development
Open Source, Open Standards,
Open Architecture
32
Web Content Management
Architecture, Product & Highlights Demo
CEM
Apps meet Content

3. ©2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Topics
3
1
Open Development
Open Source, Open Standards,
Open Architecture
32
Web Content Management
Architecture, Product & Highlights Demo
CEM
Apps meet Content

4. 5
The Open Development Triad
OPEN
SOURCE
OPEN
STANDARDS
OPEN
ARCHITECTURE

5. Effective Collaboration
6
✴ (One) Shared Goal
✴ Agree how to
disagree & decide
✴ Shared Workspace
✴ Dynamic Awareness
✴ Parallelization

6. Open Source Infrastructure
7
OPEN
SOURCE

7. Apache is BIG
8
> 2359 committers
84 projects (+ 36 incubating)
No offices
almost no f2f meetings
all decisions on mailing listsHundreds of releases
ASF members: 330 3 TB/day www traffic
The
Apache
Software Foundation
h t t p : / / w w w . a p a c h e . o r g /

8. Apache already has rules for decision-making
9
+1

9. Apache already has a shared workspace
10
revision control system
mailing lists + archives IRC
Wikis
blogs
issue tracker
automated builds
httpd (of course)

10. Apache already supports dynamic awareness
11
Collaboration hub!
code
issues
tests
decisions
RSS feeds
email events
subscriptions

11. Leadership in Open Source
12
OPEN
SOURCE
dev@httpd.apache.org
dev@jackrabbit.apache.org
dev@sling.apache.org
dev@felix.apache.org

12. Leadership in Open Standards
13
OPEN
SOURCE
OPEN
STANDARDS
URI
HTTP
CMIS
JSOP
JCR
URI Templates
HTML

13. Leadership in Open Architecture
14
OPEN
SOURCE
OPEN
STANDARDS
OPEN
ARCHITECTURE
REST OSGi

14. Why Open Architecture?
15
Open Development
Collaborative open source development
> emphasizes community
> takes advantage of the scalability
obtainable through Internet-based
virtual organizations
> adapts to the volunteer nature of
developers

15. Why Open Architecture?
16
Open Development
+
Conway’s Law
Any organization that designs a system
(defined broadly) will produce a design
whose structure is a copy of the
organization's communication structure.
Melvin E. Conway, Datamation, April 1968
http://www.melconway.com/law/
index.html

16. Why Open Architecture?
17
True open development
(a.k.a, Community-driven Design)
will only occur when the design of
your system reflects the organizational
structure of open development!
Open Development
+
Conway’s Law

17. Why Open Architecture?
18
Open Development
+
Conway’s Law
+
Change is inevitable!
Decentralized Software Evolution
(or rapid obsolescence)

18. Challenges
19
✴ Trade-off: Adaptability vs Consistency
✴ what changes are possible?
✴ what assurances are provided?
✴ Where to place the open points
✴ behavioral junctions (APIs, callback hooks)
✴ virtual machines (command tables, scripting)
✴ data flow (filters, plug-ins)

19. Closed Source Examples
20
✴ Adobe

20. ✴ Apple iPhone Ecosystem
Closed Source Examples
21

21. Open Source Examples
22
✴ What is common to the largest and
most successful open source projects?
✴ a software architecture
✴ designed to promote anarchic collaboration
✴ through extensions
✴ while preserving control over the core interfaces

22. Apache httpd: modules
23
[Apache Modeling Project, f-m-c.org]
Modules
• simplify core
• enable
independent
development
• promote
experiments
Project improves
• reduced friction
• anarchic growth
• more features
• less communication

23. Apache httpd: I/O filters
24
[Apache Modeling Project, f-m-c.org]
Filters provide more extensibility
• protocol replacement
• httpd, ftpd, nntpd, …
• stackable content manipulation
• extensions that can extend other extensions

24. Linux Kernel Modules
25
Modules
• simplify core
• enable
independent
development
• promote
experiments
Project improves
• reduced friction
• anarchic growth
• more features
• less communication
[diagram from Ivan T. Bowman, 1998]

25. Mozilla Firefox
26
Open Source
Extensible
Architecture
Plug-in Tools
Layered CSS
Editor Platform

26. 27
Architecting
It’s all about
Open
Development
for

27. Representational State Transfer
28
The REST architectural style is
1 a model of ideal Web application behavior
2 a guide for optimizing Web architecture
3 a pattern for communicating
‣ architectural constraints
‣ induced properties
‣ resulting trade-offs
4 a new software industry buzzword

28. REST on a slide
29
the disadvantages) of the optional constraints when they are known to be in effect for some
Figure 5-9. REST Derivation by Style Constraints
RR CS LS VM U
CSS LCS COD$
C$SS LC$SS LCODC$SS REST
replicated
on-demand
separated
layered
mobile
uniform interface
stateless
shared
intermediate
processing
cacheable
extensible
simple
reusable
scalable
reliable
multi-
org.
visible
programmable

32. 33
OSGi
[Birsan, ACM Queue, Mar 2005]
Taking modular extensibility to the next level
OSGi

33. 34
Eclipse Platform

34. 35
Eclipse Platform

35. Apache Sling
36
Drop-in
Extensibility
using
OSGi Bundles
jsp
rubyscala
groovy
esp...
JCR backed
Content-oriented
WebDAV-able
REST-based
+
OSGi REST

36. The Answer to Effective Collaboration
37
✴ (One) Shared Goal
✴ Agree how to
disagree & decide
✴ Shared Workspace
✴ Dynamic Awareness
✴ Parallelization
➡ Open Standards
➡ Apache-style
Voting
➡ Apache Workspace
➡ Apache Notifications
➡ Open Architecture

37. ©2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Topics
38
1
Open Development
Open Source, Open Standards,
Open Architecture
32
Web Content Management
Architecture, Product & Highlights Demo
CEM
Apps meet Content

38. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Introducing Day Software
40
Global WCM Leader
Headquartered Basel, Switzerland and Boston, Massachusetts
Support Offices: California, Basel, Singapore
International Offices: Switzerland, Germany, France, Italy, UK, Singapore
Healthy, organically growing public company
H
G
K
A
L
C F
B
I
J
E

39. ©2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Day + Adobe
41

40. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Global Brands Trust in Day
42

41. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Powered by CQ5
43

42. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Industry Standards
170
283

43. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Re-architecting
45
Roy
David
Web Content
Blueprints and Roadmap for the
Next Generation Enterprise
Web Content System
2001

44. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
WCM Target Audiences
46
CMO
BUSINESS
CIO
IT
25%25%
25% 25%
Authors
Site
Owner
Developer
Systems
A
B
C
D

45. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
CQ5 re-architected - initial release in 2008
47

46. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 48
Platform
Standardized Content Infrastructure
WCM
CRX
JCR Compliant
Content Repository
connector
connector
connector
connector
DAM
Social
Collab
+Portal
+Search
+BPM

47. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
CRX Architecture
49
Content Repository
(Development, Packages)
Apache Sling
Tagging, Workflow, Widgets,
Internationalization
CRXCQplatform
JCR
OSGI
CCAPlatform
REST

48. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 50
CRX
CQ5
ForProduction-
100%Cloudor
HybridOn-Premises/
CloudCluster
ForDemos,Trials,POCs
For
Development
andTest

49. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Flashy Web 2.0
51
JavaScript
directfull
access

50. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Flashy Web 2.0
52
ActionScript
directfull
access

51. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Flashy Web 2.0
53
ActionScript
directfull
access

52. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
WEB2.0
HTML5
54

53. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
HTML5 Video
55

54. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Multi-Channel
Web & Mobile Push!
56

55. The bad news...
UserAgentRadical: nokia6170
colors: 65536
fall_back: nokia_generic_series40_dp20
j2me_amr: TRUE
j2me_cldc_1_1: TRUE
j2me_h263: TRUE
j2me_mpeg4: TRUE
j2me_screen_height: 160
max_data_rate: 200
max_deck_size: 4194304
max_image_height: 115
max_image_width: 122
mms_3gpp: TRUE
mms_max_height: 480
mms_max_size: 100000
mms_max_width: 640
mms_mp4: TRUE
mms_vcalendar: TRUE
mms_video: TRUE
model_name: 6170
mp3: TRUE
physical_screen_height: 40
physical_screen_width: 32
playback_3gpp: TRUE
playback_acodec_amr: nb
playback_mp4: TRUE
playback_vcodec_h263_0: 10
resolution_height: 160
ringtone_amr: TRUE
ringtone_mp3: TRUE
ringtone_voices: 40
streaming_3gpp: TRUE
streaming_real_media: none
streaming_video: TRUE
streaming_video_acodec_amr: TRUE
uaprof: http://nds1.nds.nokia.com/uap....
user_agent: Nokia6170
video: TRUE
video_3gpp: TRUE
video_3gpp2: FALSE
video_max_height: 96
video_max_width: 128
video_mp4: TRUE
video_preferred_height: 96
video_preferred_width: 128
Detectingover
17kDevices
(...andcounting)

56. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Device Groups
1 32
Feature Phone Smart Phone Touch Phone
extensible
58

57. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 59
demo

58. ©2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Topics
60
1
Open Development
Open Source, Open Standards,
Open Architecture
32
Web Content Management
Architecture, Product & Highlights Demo
CEM
Apps meet Content

59. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Adobe CEM
revolutionizes
how enterprises
engage with
customers
and how customer
experience is
delivered

60. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 63
Transactional Systems (ERP, CRM, ECM, PLM, Banking Systems )
Customer Experience Management
Customers
Adobe + Day =
Global Web
Social
Collaboration
Interactive
Applications
Interactive
Documents
Content Process Analytics
AdobeDay

61. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 64
Current customer experience online…
It’s real jungle

62. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Customer interaction with an enterprise
65
Websites
Customer
Call Center
Apps
Point of Sale
Loyalty Site
Web
Applications
Social Media
Mobile Apps
Customer
Service
ApplicationMicrosites
Statements
Email

63. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Challenges
 Non-intuitive experience
 Inconsistency across channels
 Not contextual
Impact on organization
 Low conversion rates
 Lost revenues
 High cost-to-service
 Brand deterioration
Customer /
Citizen /
Partner

64. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
What the customer wants
 Personalized, responsive experiences
 Right experience for right task for the right device
 Multi-channel communication
Customer /
Citizen /
Partner

65. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Tablet
What the customer wants
PDF forms
Guided navigation
Rich, engaging
experience
 Personalized, responsive experiences
 Right experience for right task for the right device
 Multi-channel context aware
Print
Customer /
Citizen /
Partner
Mobile
Tablet
Desktop / offline

66. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
What the customer wants
 Personalized, responsive experiences
 Right experience for right task for the right device
 Multi-channel context aware
Online
Call
Center
Branch
Agent /
Field
Mail &
Fax
Email Mobile
Customer /
Citizen /
Partner
Context flow across apps and channels

67. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Challenges
 Content, application and context problem
 Multiple stacks and project silos
 High cycle time for change
 Multiple systems to scale, manage and
administer – high TCO
IT Team
Websites ApplicationsGAP
Portals
Mobile apps
RIA
Web apps
Commerce
Business apps
Websites
Microsites
Mobile Sites
WCM
DAM
Campaigns
Context
flow
Content
integration
Analytics
Application
integration

68. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Adobe’s Customer Experience Management (CEM) vision
PUBLIC CLOUD
Services
USER EXPERIENCE
Multiple
Channels
Multiple
Platforms
TOOLS
Creative
Suite
Flash
Catalyst
Flash
Builder
LiveCycle
Workbench
Foundation
CUSTOMER EXPERIENCE MANAGEMENT PLATFORM
EXISTING APPLICATIONS & SYSTEMS
Legacy
Systems
Enterprise
Information
Systems
DatabasesDirectories
Message
Queues
ECM
Repository
Modules
Dynamic
Content
Enterprise RIA
Business
Process
Solution Accelerators
Online Mobile Branch
Agent/
Field
Mail &
Fax
Email
Call
Center
Social
Analytics
Document
Services

69. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Content + applications
PUBLIC CLOUD
Services
USER EXPERIENCE
Multiple
Channels
Multiple
Platforms
TOOLS
Creative
Suite
Flash
Catalyst
Flash
Builder
LiveCycle
Workbench
Foundation
CUSTOMER EXPERIENCE MANAGEMENT PLATFORM
EXISTING APPLICATIONS & SYSTEMS
Legacy
Systems
Enterprise
Information
Systems
DatabasesDirectories
Message
Queues
ECM
Repository
Modules
Dynamic
Content
Enterprise RIA
Business
Process
Solution Accelerators
Online Mobile Branch
Agent/
Field
Mail &
Fax
Email
Call
Center
Social
Analytics
Document
Services

70. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
• Custom web apps
• RIA services
• Mosaic server
• Data Services
• Collab Service
• Content (CRX)
• Common libraries
• Caching
• Logging
• User management integration
(LiveCycle ES)
• Spring-based
• OSGi-ready
LiveCycle RIA anatomy – client stack
73
Gravity
Flash Player
SWF/Module Loading
Dependency Injection Messaging
RIA Core Services
LoggingAuthentication
Configuration
Context
Persistence
more …
LC RIA
Server
RIA Component Libraries
Content Collab Mosaic
DataServices
LiveCycle “ES Next” Solution Application
(e.g. Field Force Automation)
Security Guides more…

71. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
LiveCycle RIA component patterns
74
RIA Component
Domain & Service
Presentation
View
PresentationModel
Events
Data Binding
{View State}
{Operations}
{Events}
DomainModel
Foo getFoo()
IService
operation()
ServiceImpl
operation()
IPresentationModel
Infrastructure UtilityClasses
LiveCycle“ESNext”RIAServer
Client Server
IDomainModel
Foo getFoo()

72. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Content-centric RIA with CRX (future product vision)
 Common underlying repository for both content and application data/metadata
 Day CRX
 LiveCycle’s emerging enterprise RIA platform
 Mosaic catalog based on CRX
 Contextually agile applications (tile compositions) alongside contextually agile content (WCM, etc.)
 Consistent composition model
 Ability to leverage a common Package Share model for content + applications
 Common delivery platform for applications—both composite content apps (CCA) and rich
Internet apps (RIA)
 AIR, Flex, Mobile, HTML5
 Integrated tooling
 Simplify content-centric RIA building via Fiber modeling of CRX (LCDS leverage)
 Highly extensible and agile (easy to add new fields, etc. vs. traditional RDBMS)
 Single workflow model for updating site content, application content/criteria/configuration
75

73. © 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.