MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm

®

Copyright 2008 Adobe Systems Incorporated. All rights reserved.

Delivering Collaborative Applications with AIR and LiveCycle Data ServicesAlistair McLeod

Xavier Agnetti

®


What we aim to cover in the next 45 minutes…

• Show how collaborative applications can be built with AIR and LCDS

• Explain the challenges in building such applications

• Provide some hints and tips for building your own collaborative applications

• Show some of the features of Adobe AIR

• Demonstrate the power of Data Management Services

• Show how a Wiimote and speech recognition can be used to control an AIR application

®


Agenda

• Collaborative Applications

• BlazeDS and LiveCycle Data Services

• Application Demo

• Building a Collaborative Application

• Deep Dive into Application Code

• Summary and Questions

®


Collaborative Applications

®


What do we mean by Collaborative Applications?

®


BlazeDS and LiveCycle Data

Services

®


BlazeDS Overview

Easily connects Flex & AIR applications to existing server logic

High performance data transfer for more responsive applications

Server push over standard HTTP Full pub/sub messaging that extends

existing messaging infrastructure Free and open source Publication of the Action Message Format

(AMF3) binary data protocol specification Certified builds, warranty protection and

enterprise support subscriptions available

BlazeDS is the remoting and HTTP-based messaging technology which Adobe is contributing to the community under LGPL

BlazeDS

Data Management

RPC Services

Messaging

ServiceAdapters

Data Synchronization

Off-line Applications

Data Paging

Web Service

HTTP Service

Remote Object Service

Publish & Subscribe

Collaboration

Real Time Data Push

Proxy Service

Web-tier Compiler

Portal Deployment

RIA-PDF Generation

LiveCycle

ColdFusion

Hibernate

SQL

JMS

Java

Custom

®


LiveCycle Data Services ES Overview

LiveCycle Data Services is a set of Java EE components and APIs used to:

Create data-intensive RIAs with less code, less risk, and accelerated time to market due to an innovative client-server programming model

Integrate RIAs with existing applications, back-end data, and JEE infrastructure

Easily integrate RIAs with LiveCycle document and process services

Enable collaboration, offline AIR and real-time data streaming applications to be built in a scalable and reliable manner with robust publish and subscribe messaging

Generate PDF documents from RIAs that include graphical assets

LiveCycle Data Services ES

Data Management

RPC Services

Messaging



Data Paging

Web Service

HTTP Service


Publish & Subscribe

Collaboration

Real Time Data Push

Proxy Service

Web-tier Compiler

Portal Deployment

RIA-PDF Generation

LiveCycle

ColdFusion

Hibernate

SQL

JMS

Java

Custom

ServiceAdapters

®


Feature Comparison

Feature BlazeDSLiveCycle Data

Services ES

Java Remoting √ √

Web Proxy √ √

JMS Adapter √ √

AJAX Client Libraries √ √

Administrative Console √ √

Clustered Messaging √ √

Pub/Sub Messaging √ √

Web container-based messaging service (100’s of clients/CPU) √ √

Dedicated messaging service (1000’s of clients/CPU) √

Per-client Quality of Service √

Data Management Service √

Data Paging √

Flex-LiveCycle Integration √

RIA-to-PDF Generation √

Offline Data Synchronization (AIR) √

WSRP/Portal Integration √

SiteMinder Integration √

®


Application Demo

®


Application Features

®


Application Demonstration

®


Building a Collaborative Application

• Application Architecture

• Technologies Used

• Challenges

®





• Challenges

®


Application Architecture

®


Application Structure

Client Layer

Adobe Integrated Runtime

Adobe Cairngorm

Alternativa 3D

WiiMoteKeyboard

Application Layer

FMSLCDS

DMS

Messaging

Persistence Layer

HSQL DB

Microphone

®





• Challenges

®


Use of Adobe AIR

®


Use of LiveCycle Data Services

Chat between the retailer and customer

Data push to retailer application Synchronization of views between

the retailer and customer Conflict resolution Store local changes while offline,

and commit them when back online Adapter architecture Paging large data sets Generate customer configuration as

PDF

LiveCycle Data Services ES

Data Management

RPC Services

Messaging



Data Paging

Web Service

HTTP Service


Publish & Subscribe

Collaboration

Real Time Data Push

Proxy Service

Web-tier Compiler

Portal Deployment

RIA-PDF Generation

LiveCycle

ColdFusion

Hibernate

SQL

JMS

Java

Custom

ServiceAdapters

®


Use of Flash Media Server

• Audio and video conferencing

• Very little development effort• No server side code

• Alternative solution: use CoCoMo• Hosted service

• Public beta now available

• See other Max sessions for details

®


Displaying 3D model

• Straightforward API

• Better performance than PaperVision 3D

• Easier integration with 3DS MAX models

®


Using the Wii Remote as a Control Device

Wiimote

WiiFlash server

WiiFlash AS3 API

®


Speech recognition on AIR

Wiimote

WiiFlash server

WiiFlash AS3 API

®





• Challenges

®


Challenges in Building Collaborative Applications

®


Deep Dive into Application Code

• Presentation Model

• Data Management Services

• Large Data Sets

• Message Broker

®





• Large Data Sets

• Message Broker

®


What is a Presentation Model?

• A class that contains the state and logic required by a view.

• The general purpose of the Presentation Model is to separate concerns

• The view is responsible for rendering the presentation model

• The view hence holds a reference the presentation model

• The presentation model does not know anything about its view

• It can then be unit-tested in isolation

®


Domain Layer

Cairngorm and the Presentation Model

Integration TierView LayerPresentatio

n Layer

Arthur

[email protected]

Ford- [email protected]

Zaphod –

[email protected]

Arthur –

[email protected]

Tricia–

[email protected]

Marvin =

[email protected]

Add a Contact Contact list

Add a Contact

Add a Contact

Presentation Model+ contacts : ContactDomain+ addContact (name, email)

Presentation Model+ contacts : ContactDomain+ addContact (name, email)

CMDCMD CMDCMD CMD

BusinessDelegate

ContactVOContactVO

ServiceLocator

model.addContact(firstname, email)

Cairngorm

Event

Cairngorm

Event

Serv

ice

Serv

ice

Serv

ice

Serv

ice

Serv

ice

Serv

ice

Serv

ice

ContactVOContactVO

FrantController

ContactsDomain+ contacts : List

ContactsDomain+ contacts : List

®


Cairngorm and Presentation Models - Differences

®





• Large Data Sets

• Message Broker

®


Data Management Services (DMS)

DMS is data-driven (not request-response paradigm) The user gesture/command pair does fit well here

DataModel is responsible to talk to the DataService, and store the data retrieved from it

Ability to bind to DataService attributes like commitRequired.

®


Domain Layer

Cairngorm and Data Management Services

Integration TierView LayerPresentation

Layer

Arthur

[email protected]


Zaphod –

[email protected]

Arthur –

[email protected]

Tricia–

[email protected]

Marvin =

[email protected]


Add a Contact

Add a Contact

ServiceLocator

model.addContact(firstname, email)

Client DataServices

Serv

ice

Serv

ice

Data Model+ contacts : List+ addItem( item )


Presentation Model+ contacts : ContactDataModel+ addContact (name, email)


Zaphod –

[email protected]

Arthur –

[email protected]

Tricia–

[email protected]

Marvin =

[email protected]


Add a Contact

Add a Contact

ServiceLocator Client DataServices

Serv

ice

Serv

ice



Presentation Model+ contacts : ContactDataModel+ addContact (name, email)

Remote DataServices

Serv

ice

Serv

ice


Zaphod –

[email protected]

Tricia–

[email protected]

Marvin =

[email protected]


Add a Contact

Add a Contact

Arthur

[email protected]


Zaphod –

[email protected]

Tricia–

[email protected]

Marvin =

[email protected]


Add a Contact

Add a Contact

®





• Large Data Sets

• Message Broker

®


How to deal with large dataset?

®





• Large Data Sets

• Message Broker

®


Message Broker

Listeners are registered in the Broker singleton

Whenever a listener sends a message, the broker calls its producer and waits for a response in the consumer.

Then every listener is notified that a message is ready to be consumed

Listener /

Producer

Message Broker

Local Producer

Local Consum

er

Listener

Listener

Listener

Messaging

Destination

®


Miscellaneous tips

• Set different publisher names in order to launch several instances of the same AIR application

• MessagePerformanceUtils built-in LCDS 2.6 helps optimizing network round-trip for your application

• In Flex, in services-config.xml, the tokens are replaced by the app server

<endpoint url="http://{server.name}:{server.port}/{context.root}

• In AIR, either • you replace it directly by

<endpoint url="http://myserver:8080/myContextRoot

• Or you create new channels set in the client code, loading the endpoint URLs from a local file

®


Summary and Questions

®


Summary

• Show how collaborative applications can be built with AIR and LCDS

• Explain the challenges in building such applications

• Provide some hints and tips for building your own collaborative applications

• Show some of the features of Adobe AIR

• Demonstrate the power of Data Management Services

• Show how a Wiimote and speech recognition can be used to control an AIR application

®


Any Questions

Questions? (simple please)

Documents

MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm