<Insert Picture Here>

Oracle Mobile Client Overview

Oracle Tools Product Development

<Insert Picture Here>

Session Agenda

• Framework

• Demo

• Roadmap

• Questions and Answers

<Insert Picture Here>

“Extending Enterprise Application to

ADF Mobile

mobile users”

“Write once, and deploy to multiple

mobile platforms and channels”

“Declarative and Meta-data driven:

easy to develop and maintain”

Oracle Fusion Middleware

Extending Oracle Applications and

Technology to Mobile Clients Application Development Framework

JDeveloper

JDeveloperSingle, Integrated Enterprise IDE

DBMS DBMS

ModelingModeling

Java Dev.Java Dev. BPM Dev.BPM Dev.Java EE Java EE

Dev.Dev.

ESB Dev.ESB Dev. Business Business

RulesRules

Portal Dev.Portal Dev. Desktop & Desktop &

MobileMobile

Common Metadata ManagerCommon Metadata Manager

Common Application Lifecycle ManagementCommon Application Lifecycle Management

Common Business CatalogCommon Business Catalog

Common Modeling FrameworkCommon Modeling Framework

Common IDE FrameworkCommon IDE Framework

Application Development FrameworkMVC Development for the Enterprise

DeviceDevice ViewView ControllerController ModelModel

• Mobile Device

& Browser

Optimization

• JSF Components

• Mobile

Components

• Ajax & DHTML

• Flash

• JSF Page Flow

• JSR 227 Data

Binding

• O-R Mapping

• EJB 3, JPA

• WebServices

ADF and JDeveloperTarget Developers and Communities

• One development environment and platform

• For server/web-based and on-device applications

• Covering both desktop and mobile clients

• Used by developers to

• Build custom J2EE applications and modules• Build custom J2EE applications and modules

• Configure/develop/integrate Fusion Middleware components

• Extend integrated applications to end users

• Used by Internal Oracle teams to build products:

• Oracle Fusion Applications

• Oracle Applications Unlimited

• WebCenter Suite (Enterprise 2.0)

• Oracle Enterprise Manager

Oracle ADF Mobile PlatformRichness of User Interaction

Native

(Full Java Clients)

Make business data available regardless of network connectivity.

Deep integration with device services

Delivers a rich mobile web experiences through AJAX and Web 2.0 technologies.

UI rendering degrades gracefully to deliver HTML content to a wide set of consumer devices with basic

ADF Mobile Browser(Current Offerings)

ADF Mobile Client(New)

Richness of User Interaction

(Full Java Clients)

Device Service Access & Offline Support

AJAX

(Smartphone Mobile Browsers)

device services

HTML

(HTML Mobile Browser)

consumer devices with basic HTML browsers.

What is ADF Mobile Client?

• Extends enterprise applications to on-device

mobile clients

• Develop-once, deploy to multiple platforms

• Similar experience as developing a web

application

• Java-based runtime client

Java Client• Java-based runtime client

• Meta-data driven development paradigm (XML)

• Complete MVC stack on the device

• UI metadata rendered to native controls on-

device to provide a native user-interfaceModel

Controller

View

Client

Local DB

Server-side Components

• Oracle Database Lite (OpenSync) Mobile Server • Data Synchronization

• Server DB (Oracle) <-> Client (SQLite) DB

• ADF Mobile Transaction Replay Service (MTRS)Service (MTRS)• Automatically replays client-side application

transaction on server

• Complements Mobile Server Synchronization

BlackBerry Device

Desktop/Mobile Browser Clients

Mobile Server

PublicationsApplication Server

ADF Mobile Client Data Synchronization

SQLite

ADF MobileClient

mSync Base ADF App ADF BC/EO

Publications

Windows Mobile

mSync

Others

ServerDatabase

SQLite

ADF BC/VO/AM

Web Services

Synchronization Support

• Complete and Delta

• One-way and two-way

• User-invoked, background, and programmatic

ADF MobileClient

Breaking Through Common Mobile Platform

Limitations

Limitations of current solutions:

• Duplicating development efforts • Different tools and environment for different mobile

devices and channels (on-device vs. web)

• Different frameworks for native/on-device vs. web based mobile applicationsbased mobile applications

• Code-driven development paradigm• Java (ME and SE), Objective C, C++, etc.

• (Re)build all application services from the ground up• For application logic services, view services, etc.

• Proprietary frameworks and technologies

ADF Mobile Client Development Process

Application Server

App1

ADF Business Component

UI

Pages

JSR 227

Mobile Server

App2

T1

T2

T3

Tn

C

App1

T1

T2

T3

Tn

C

Transaction Replay Service

User1

Pub1

Pub2

PI1

PI2

PI6

PI7

User1

ServerDatabase

Mobile Device MSync

App1

T1’

T2’

DB Navigator

App Deploy

Mobile App Deploy

Mobile Data Deploy

Terminology:

• Publication Item (PI) = (ADF BC) Entity Object = DB Table/View

• Publication (Pub) = Application

ADF Mobile Client Development Process

1. Deploy Base ADF Application’s Business Component as ADF

Library

2. Generate ADF BC for Mobile Client from Base ADF

Application’s ADF Business Components

3. Add/update ADF Business Components for Mobile Client

applicationapplication

4. Create Mobile Client Task Flow

5. Define Mobile Client pages

6. Deploy Application Data and generate Oracle DB Lite Mobile

Server Synchronization Rules (Optional)

7. Deploy to Mobile Device or Device Package

8. Deploy Mobile Transaction Replay Service components

(Optional)

• Declarative and meta-data driven • WYSIWYG user interface designer

• Visual page flow editor

• Same developer experiences

• For both browser and on-

Developer Productivity

• For both browser and on-device applications

• Allows developer focus on meeting business requirements by providing• Complete enterprise application

framework

• Standards-based, hot-pluggable platform

ADF Mobile Browser vs. Native Clients Recommendations

• Mobile Browser is preferred when:

• Most or all data need to be accessed in

real time

• Basic integration with device native services

• Need to support users on a wide variety of mobile devices

• Need to develop and go-alive today

• Mobile Client (On-device) is recommended when:• Mobile Client (On-device) is recommended when:

• Data needs to be available while device is offline

• Extensive integration with on-device services such as integrated

barcode scanner

• Requires consistent client performance

• Targeted set of mobile devices by enterprise users

• Recommendation will change as technology and Platform

evolves

Roadmap – ADF Mobile Client

• ADF Mobile Client

• Technical Preview is now available

• Delivered as anExtension/Update

for JDeveloper 11g PatchSet 2

• Production Release planned for 2010

• Including:

• Developer feedback • Developer feedback

• Performance optimization

• Dependent on BlackBerry OS Updates

Resources and Technical Preview for ADF

Mobile

• ADF Mobile Client Resources:

• Product Information:

http://www.oracle.com/technology/tech/wireless/adf_mobile.

html

• Demo Site (Download Demo Client Apps from your Mobile

Device): http://stshld.oracle.com:8888/demo/faces/main.jspx

• ADF Mobile Client Technical Preview Availability• ADF Mobile Client Technical Preview Availability

• First download JDeveloper version 11.1.1.3.0 when available

• Download ADF Mobile Client extension from JDeveloper

update center