strengthening adobe’s enterprise platform with day software and open development

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

Topics

2

1

Open DevelopmentOpen Source, Open Standards, Open Architecture

32

Web Content ManagementArchitecture, Product & Highlights Demo

CEMApps meet Content


Topics

3

1


32



5

The Open Development Triad

OPENSOURCE

OPENSTANDARDS

OPENARCHITECTURE

Effective Collaboration

6

✴ (One) Shared Goal

✴ Agree how to disagree & decide

✴ Shared Workspace

✴ Dynamic Awareness

✴ Parallelization

Open Source Infrastructure

7

OPENSOURCE

Apache is BIG

8

> 2359 committers

84 projects (+ 36 incubating)

No officesalmost no f2f meetings

all decisions on mailing listsHundreds of releases

ASF members: 330 3 TB/day www traffic

TheApacheSoftware Foundationh t t p : / / w w w . a p a c h e . o r g /

Apache already has rules for decision-making

9

+1

Apache already has a shared workspace

10

revision control system

mailing lists + archives IRC

Wikis

blogs

issue trackerautomated builds

httpd (of course)

Apache already supports dynamic awareness

11

Collaboration hub!

code

issues

tests

decisionsRSS feeds

email events

subscriptions

Leadership in Open Source

12

OPENSOURCE

[email protected]

[email protected]

[email protected]

[email protected]

Leadership in Open Standards

13

OPENSOURCE

OPENSTANDARDS

URI

HTTP

CMIS

JSOP

JCR

URI Templates

HTML

Leadership in Open Architecture

14

OPENSOURCE

OPENSTANDARDS

OPENARCHITECTURE

REST OSGi

Why Open Architecture?

15

Open Development

Collaborative open source development> emphasizes community> takes advantage of the scalability

obtainable through Internet-basedvirtual organizations

> adapts to the volunteer nature of developers


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 1968http://www.melconway.com/law/index.html

http://www.melconway.com/law/index.html





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


18

Open Development+

Conway’s Law+

Change is inevitable!

Decentralized Software Evolution(or rapid obsolescence)

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)

Closed Source Examples

20

✴ Adobe

✴ Apple iPhone Ecosystem

Closed Source Examples

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

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

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

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]

Mozilla Firefox

26

Open Source

Extensible

Architecture

Plug-in Tools

Layered CSS

Editor Platform

27

ArchitectingIt’s all about

Open Development

for

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

REST on a slide

29

85

the disadvantages) of the optional constraints when they are known to be in effect for some

realm of the overall system. For example, if all of the client software within an

organization is known to support Java applets [45], then services within that organization

can be constructed such that they gain the benefit of enhanced functionality via

downloadable Java classes. At the same time, however, the organization’s firewall may

prevent the transfer of Java applets from external sources, and thus to the rest of the Web

it will appear as if those clients do not support code-on-demand. An optional constraint

allows us to design an architecture that supports the desired behavior in the general case,

but with the understanding that it may be disabled within some contexts.

5.1.8 Style Derivation Summary

REST consists of a set of architectural constraints chosen for the properties they induce on

candidate architectures. Although each of these constraints can be considered in isolation,

describing them in terms of their derivation from common architectural styles makes it

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

33

OSGi

[Birsan, ACM Queue, Mar 2005]

Taking modular extensibility to the next level OSGi

34

Eclipse Platform

35

Eclipse Platform

Apache Sling

36

Drop-in

Extensibility

usingOSGi Bundles

jsp

rubyscala

groovyesp...

JCR backedContent-orientedWebDAV-ableREST-based

+

OSGi REST

The Answer to Effective Collaboration

37

✴ (One) Shared Goal

✴ Agree how to disagree & decide

✴ Shared Workspace

✴ Dynamic Awareness

✴ Parallelization

➡ Open Standards

➡ Apache-styleVoting

➡ Apache Workspace

➡ Apache Notifications

➡ Open Architecture


Topics

38

1


32



© 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

HG

K

A

L

C F

B

I

J

E


Day + Adobe

41


Global Brands Trust in Day

42


Powered by CQ5

43


Industry Standards

170

283


Re-architecting

45

Roy David

Web Content

Blueprints and Roadmap for the Next Generation EnterpriseWeb Content System

2001


WCM Target Audiences

46

CMOBUSINESS

CIOIT

25%25%

25% 25%

Authors

SiteOwner

Developer

Systems

AB

CD


CQ5 re-architected - initial release in 2008

47

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

Platform

Standardized Content Infrastructure

WCM

CRXJCR CompliantContent Repository

connector

connector

connector

connector

DAMSocialCollab

+ Portal

+ Search

+ BPM


CRX Architecture

49

Content Repository(Development, Packages)

Apache Sling

Tagging, Workflow, Widgets, Internationalization

CR

XC

Qpl

atfo

rm

JCR

OSGI

CC

A P

latformREST


CRXCQ5

For Production - 100% Cloud or

Hybrid On-Premises / Cloud Cluster

For Demos, Trials, POCsFor

Development and Test


Flashy Web 2.0

51

JavaScriptdirect full access


Flashy Web 2.0

52

ActionScriptdirect full access


Flashy Web 2.0

53

ActionScriptdirect full access


WEB 2.0

HTML5

54


HTML5 Video

55


Multi-Channel

Web & Mobile Push!56

The bad news...

UserAgentRadical: nokia6170colors: 65536fall_back: nokia_generic_series40_dp20j2me_amr: TRUEj2me_cldc_1_1: TRUEj2me_h263: TRUEj2me_mpeg4: TRUEj2me_screen_height: 160max_data_rate: 200max_deck_size: 4194304max_image_height: 115max_image_width: 122mms_3gpp: TRUEmms_max_height: 480mms_max_size: 100000

mms_max_width: 640mms_mp4: TRUEmms_vcalendar: TRUEmms_video: TRUEmodel_name: 6170mp3: TRUEphysical_screen_height: 40physical_screen_width: 32playback_3gpp: TRUEplayback_acodec_amr: nbplayback_mp4: TRUEplayback_vcodec_h263_0: 10resolution_height: 160ringtone_amr: TRUEringtone_mp3: TRUE

ringtone_voices: 40streaming_3gpp: TRUEstreaming_real_media: nonestreaming_video: TRUEstreaming_video_acodec_amr: TRUEuaprof: http://nds1.nds.nokia.com/uap....user_agent: Nokia6170video: TRUEvideo_3gpp: TRUEvideo_3gpp2: FALSEvideo_max_height: 96video_max_width: 128video_mp4: TRUEvideo_preferred_height: 96video_preferred_width: 128

Detecting over

17k Devices(...and coun

ting)


Device Groups

1 32

Feature Phone Smart Phone Touch Phoneextensible

58


demo

http://localhost:4502/

http://localhost:4502/


Topics

60

1


32




Adobe CEM revolutionizes

how enterprises engage with customers

and how customer experience is

delivered


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


Current customer experience online…It’s real jungle


Customer interaction with an enterprise

65

Websites

Customer

Call Center Apps

Point of Sale

Loyalty SiteWeb

Applications

Social Media

Mobile Apps

Customer Service

ApplicationMicrosites

Statements

Email


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


What the customer wants

Personalized, responsive experiences

Right experience for right task for the right device

Multi-channel communication



Tablet


PDF formsGuided navigation

Rich, engaging experience



Multi-channel context aware

Print


Mobile

Tablet

Desktop / offline





Multi-channel context aware

Online Call Center Branch Agent /

FieldMail &

Fax Email Mobile


Context flow across apps and channels


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

PortalsMobile appsRIAWeb appsCommerceBusiness apps

WebsitesMicrositesMobile SitesWCMDAMCampaigns

Context flow

Content integration

Analytics Application integration


Adobe’s Customer Experience Management (CEM) vision

PUBLIC CLOUD

Services

USER EXPERIENCE

Multiple Channels

MultiplePlatforms

TOOLS

CreativeSuite

FlashCatalyst

FlashBuilder

LiveCycleWorkbench Foundation

CUSTOMER EXPERIENCE MANAGEMENT PLATFORM

EXISTING APPLICATIONS & SYSTEMS

Legacy Systems

Enterprise Information

SystemsDatabasesDirectoriesMessage

QueuesECM

Repository

Modules

Dynamic Content Enterprise RIA Business

Process

Solution Accelerators

Online Mobile Branch Agent/ Field

Mail &Fax Email Call

CenterSocial

Analytics Document Services


Content + applications

PUBLIC CLOUD

Services

USER EXPERIENCE

Multiple Channels

MultiplePlatforms

TOOLS

CreativeSuite

FlashCatalyst

FlashBuilder

LiveCycleWorkbench Foundation

CUSTOMER EXPERIENCE MANAGEMENT PLATFORM

EXISTING APPLICATIONS & SYSTEMS

Legacy Systems

Enterprise Information

SystemsDatabasesDirectoriesMessage

QueuesECM

Repository

Modules

Dynamic Content Enterprise RIA Business

Process

Solution Accelerators

Online Mobile Branch Agent/ Field

Mail &Fax Email Call

CenterSocial

Analytics Document Services


• 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

Dat

a Se

rvic

es

LiveCycle “ES Next” Solution Application(e.g. Field Force Automation)

Security Guides more…


LiveCycle RIA component patterns

74

RIA Component

Domain & ServicePresentation

View

PresentationModel

Events

Data Binding

{View State}{Operations}{Events}

DomainModel

Foo getFoo()

IServiceoperation()

ServiceImploperation()

IPresentationModel

Infrastructure UtilityClasses

Live

Cycl

e “E

S N

ext”

RIA

Ser

ver

Client Server

IDomainModelFoo getFoo()


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

strengthening adobe’s enterprise platform with day software and open development

Technology

open development open

open source examples

open source infrastructure

true open development

software architecture

web architecture

independent development

apache httpd