From Vision to Execution (and back) - Jim Colson, IBM

© copyright 2004 by OSGi Alliance All rights reserved.
OSGi Alliance
From Vision to Execution (and back)
Jim Colson, Distinguished Engineer
IBM
Vision Execution

A view of the market
Vision Execution

© copyright 2004 by OSGi Alliance. All rights reserved.
0
4
8
12
16
20
24
2003 2004 2005 2006 2007 2008
0
4
8
12
16
20
24
2003 2004 2005 2006 2007 2008
0
4
8
12
16
20
24
2003 2004 2005 2006 2007 2008
Other Devices
PC
Pervasive devices growing more than 10
times faster than PCs… 22 billion+ by 2008*
Nearly 70% of all enterprises will deploy a
mobility/pervasive solution by 2005**
75% of knowledge workers mobile at least
25% of the time are using "pervasive"
device (2005/2006)**
Pervasive devices growing more than 10
times faster than PCs… 22 billion+ by 2008*
Nearly 70% of all enterprises will deploy a
mobility/pervasive solution by 2005**
75% of knowledge workers mobile at least
25% of the time are using "pervasive"
device (2005/2006)**
Enable the mobile workforce
Integrate data from physical assets
Support multiple device types over
multiple networks seamlessly
Optimize business processes and asset
utilization
Enable the mobile workforce
Integrate data from physical assets
Support multiple device types over
multiple networks seamlessly
Optimize business processes and asset
utilization
Trends
Market Requirements
Billions
*Source: IDC 2004
**Source: Meta Group 2003
Market Dynamics

Device Types
Platform
Aftermarket, On Device Developer Community
Extensible networked data aware applications
High back end affinity
Platform
Connectable
Standalone
Connectable
Built in networked data aware applications
Remote management and content
Limited back end affinity
Standalone
Conventional Embedded Market
No data network connectivity
No back end (data) affinity

Device Platform – The challenge
OEMs,
ODMs,
Tier 1s
Enterprises
& Service
Providers
ISV’s,
Developers
NEED APPLICATIONS
that run on their devices
NEED APPLICATIONS that
run on MANY DEVICES
NEED to build their application to
support MANY DEVICES

Device Platform – Success measures
OEMs,
ODMs,
Tier 1s
Enterprises
& Service
Providers
ISV’s,
Developers
NEED APPLICATIONS
run on MANY DEVICES
Widespread device
deployment
Large ISV
Community
Low total cost of
ownership for devices,
services, and applications.
Devices that reuse existing
development skills
Apps & services
that run across
evolving devices
Common
requirements
vocabulary

Device Platform - OSGi as a catalyst
OEMs,
ODMs,
Tier 1s
Enterprises
& Service
Providers
ISV’s,
Developers
NEED APPLICATIONS
run on MANY DEVICES
Widespread device
deployment
Large ISV
Community
Low total cost of
ownership for devices,
services, and applications.
Devices that reuse existing
development skills
Apps & services
that run across
evolving devices
Common
requirements
vocabulary
Infrastructure
Portable
middleware
End-to-end
tooling
Enabled by
OSGi

What’s new since OSGi WC 2003?
Vision Execution

Creation of Mobile Expert Group (MEG)
• Created by OSGi Board of Directors on Friday, October 10, 2003.
Formation driven by 2 key industry players Motorola & Nokia,
with strong initial support by Deutsche Telekom, Espial, IBM &
ProSyst Software
Will define requirements and specifications to tailor and extend
the OSGi Service Platform for mobile devices that are data-
capable, and also capable of connecting to wireless networks
Starting with development of an OSGi specification for the
management of CDC Foundation based environments on mobile
digital handsets
Expands the number of industries adopting and enhancing the OSGi
Service Platform

Foundation: September 28, 2004
Founder Members: IBM Japan, Mitsubishi Electric, NEC, NTT, SHARP, TOSHIBA
Chairman: Prof. Hideyuki Tokuda (Keio University)
Objective: Cross industry business/technical information exchange fostering new services
Planned Activity: Regular workshops to drive a focus on promoting interoperability testing
by member companies
OSGi Users’ Forum Japan
Creation OSGi Users Forum (Japan)
ALPINE, Brainsellers.com, CLOUD
NINE, ECHELON Japan, Espial,
IBM Japan, Information Technology
One, JAPAN PROCESS
DEVELOPMENT, KAI Software,
KDDI R&D Laboratories, Kochikuya,
MAZDA, Melco Power Systems,
Mitsubishi Electric
NEC, NTT Advanced Technology,
NTT, NTT East, NTT Software, Oki
Electric Industry, SANYO Electric,
SEIKO EPSON, SHARP, System
Warehouse, TEPCO, TOSHIBA,
Toshiba Solution, Tostem Inax
Holding, YKK Corporation

What’s new with IBM and OSGi?
Vision Execution

IBM Strategic thrust
On Demand Operating Environment
OSGi is key to Access Services for Users and Business
Enterprise Service Bus
Business Connections
Mediation, Messaging, Events
Business
Function
Services
Business Process
Choreography
Services
Common
Services
Choreography
Personalization…
Reporting
Custom
Applications…
Packaged Applications
Business Rules… Acquired Services
User
Interaction
Services
Collaboration
Presentation…
Application Container
Utility Business Services
Resource Virtualization Services
Availability Services…Security Services
BillingRatingMetering Services
Server Storage Resource Mapping…Network
Service Level Automation & Orchestration
Workload Services Configuration Services
Peering Settlement…
Infrastructure Services
Problem Management
Metadata Services …
Information Integration
Information
Management
Services
Information Access
Analytics
Content
Business
Services
Business
Services
Business
Services
Business
Services
Business
Performance
Management
Business
Services
Access
Services
Adaptation...
Interaction…
Connectivity…
User
Business

Access - Extend the programming model
Connection Fidelity
Interaction Fidelity
Desktop
Laptop
Gizmos
(e.g. PDA)
Adaptation Fidelity
Current
Programming
Model
Mostly NeverAlways Sometimes
Request
&
Response
None
“Reactive”
Establish a “Client Side” Middleware Industry to enable “Server Managed Clients”

Programming Model
Client
Platform
Controller
Store
ModelView
Controller
Store
ModelView
Controller
Store
ModelView Server
Platform(s)
Dynamically manageable
Platform
Applications
Configuration
“Disconnectable” operations
Desktops and appliances
Preserve Roles
Development
Deployment
Richer experiences
Local Interactions
Alternate View/Control
choices
Mediator
Mediator
Mediator
Intermediate
Tiers
End Point
SOA is the composition model for the MVC patterns across topologies

Managed Client Middleware
Application Adapters
BUSINESS PROCESSES
Monitoring Workflows
Business Context
& Activities
Collaboration Services
Interaction &
Access Services
Managed Client
Services
Rich client
Browser
INFORMATION
Data &,
ContentIntegration
Search,
Analysis
Industrial Controller
Telematics Controller
Smart Phone/PDA
Smartcard
Banking ATM
Laptop
IBM WORKPLACE
Business Context & Activities
Interaction & Access Services
Managed Client Services
The power of one architectural model, one programming model, one consistent tool set
FRONT-END INTEGRATION BACK-END INTEGRATION

IBM Workplace Client Technologies
An architecture to enable the eco-system
Device Server
Access Services
Platform Management System
J2EE
Mobile
PlatformSolutions
Telematics Factory Home Office
Interaction
Services

Execution EnvironmentVirtual Machine
ModuleJava Class Library
Service
Framework
Lifecycle
Service Registry
• Value
Enable simultaneous execution of applications and services on “fit
for purpose” class libraries on a single JVM instance.
Independent life-cycle management of services and applications
on a single JVM instance
• Runtime (SMF + ….)
OSGi Minimum Execution Environment
J2ME (CDC based)
J2SE
• Standards
J2ME, J2SE, OSGi R3
Extension Services for WebSphere Everyplace
Access Services
Platform Management
Interaction
Services

Platform Management (push/pull)
Virtual Machine
Java Class Library
Framework
SyncML
Framework
OSGi Device
Agent
DMS
WAS
Server
Client
SyncML/DMProtocol
HTTP
HTTP Bundle B
Bundle A
Bundle B
Bundle A
depends
Plugins
Web Services
Interfaces
TPM,
WEA,
WEDM,
WES SPO
DMS
Notification
• Runtime
– Components
• Agent
Bundle
• DMS Server
• Standards
– OSGi,
– OMA (SyncML
DM)
• Value
– Enable “On Demand” management
of Applications ranging from
passive distribution to active,
intelligent management
Client
Access Services
Platform Management
Interaction
Services

Portal
Container
Portlet
Web Container
JSP Servlet
Access Services
• Value
– Extend backend programming model “out” to devices
• Runtime
– Web Container
• JSP 1.2 and Servlet 2.3
– Relational Data Access using JDBC
• DB2 Everyplace or Cloudscape with Data Synch
– Assured Messaging using JMS 1.1
• WebSphere MQ Everyplace
– Web Services
• Web Services Client (JSR 172) and Provider
– XML Parsing
• MicroXML a small footprint non-validating parser
• XML4J a full featured parser with validation
– Synchronization Services
• SyncML Framework (OMA SyncML)
– SCADA (Supervisory Control and Data Acquisition)
• WebSphere MQ Telemetry Transport
• Standards
– J2EE, J2ME, W3C,
– Web Services, OMA
Client
Access Services
Platform Management
Interaction
Services
DB2e Cloudscape
JDBC
MQe
JMS
Services
Web
Micro
XML
XML4J
XML JNDI
Transaction
Container
Business
Logic

MIDP
Container
Web Container
JSP Servlet
Portal
Container
Portlet
• Runtimes
– Components
• Browser (HTML, WML)
• Multi-modal browser (XHTML + VoiceXML (X+V))
• Graphics (AWT, SWT, lcdUI, others)
• JSPs/Servlets, Portlets
– Aggregators
• Enterprise Offering
• MIDP
• Browser
• Custom
• Portal
• Standards
– J2SE, J2ME, W3C, Eclipse
Interaction Services
Browser
Markup
Languages
Embedded
ViaVoice
X+V Plugin
(Opera/Access)
Eclipse
RCP
SWT
JFace
Workbench
Eclipse
eRCP
eSWT
eJFace
eWorkbench
AWT
Client
Access Services
Platform Management
Interaction
Services

Some Solution Patterns
Vision Execution

Local Web Application with replicated data
extend existing web based applications
WAS
ServerDevice
Java Virtual Machine
Java Class Library
Framework
Micro
XML
XML4J
XML
Web Container
JSP Servlet
Web Application
Presentation
Web Application
Data
Model
JDBC
DB2e
Controller
DB2 Sync Server
Browser
Browser

Embedded Gateway Data Collection
the “classic” OSGi solution pattern – with messaging
ServerDevice (Gateway)
Java Class Library
Framework
MQe
Gateway
WBI
Broker
Enterprise
Apps
SyncML
Framework
OSGi Device
Agent
MQe
JMS
Data
Collection
Service
QM
Data
Collection
Device
Data
Collection
Device
RFID
AIO
DIO
WAS
JDBC
DB2e
DB2 Sync Server

Client using Local/Global Web Services
begin movement to application level SOA
WAS
ServerClient
Java Class Library
Framework
HTTP Server
Global Address
Book Web Service
Web Services
Server Proxy
Local Address
Book Web Service
Data
Model
JDBC DB2e
Address Book
Application
Web Svcs
Client Stub

Workplace Client Technology
Micro Edition
Vision Execution

WCT ME – What is it?
• An integrated SDK containing runtimes and tools…
– Runtimes
• Pre-configured device middleware service platforms
• Components for (composition/extension) of (new/existing) platforms
– Tools
• Packaging tools - composition
• Development tools - creation
• Analysis tools - optimization
• Porting kits - movement
• … enabling an end to end ecosystem.
Business Context
& Activities
Interaction &
Access Services
Managed Client
Services
Business Context & Activities
Interaction & Access Services

WCT ME – How is it packaged?
LPP’s
WSDD LPP Local Sites
WEME Core
Core( s)
Tooling
3rd Party
Tooling
C
Tooling
UEI
Analyze
Link (JXE)
Compile (AOT)
Build &
Package
WM2003
MIDP LPP
Palm
MIDP LPP
WM2003
Foundation/PP
LPP
Sharp
Zaurus
Foundation/PP
LPP
WCTME 5.7.1 CD
Licenses
WSDD 5.7.1 (LPP)
Technologies
(Miscellaneous)
Micro Environment
Toolkit for
WebSphere Studio
Technologies
WECE
Micro Environment
Toolkit for
WebSphere Studio
QNX
WEME
WSDD
Update Sites
Update Sites
Forum Nokia
WECE
Core

WCT ME – Who is using it?
The value chain that enables the eco-system
Semiconduct
or & OS
Providers
Platform
& System
Integrators
Device
Manufacturers
Enterprises
Solution
Integrators,
ISVs
“Into” - Pre-Design / Embedded
“Onto” - Aftermarket / Download
Post install Platform, Apps & Data
Pre-enable new devices
Service
Providers
Solution
Integrators,
ISVs
“Onto” - Aftermarket / Download
Post install Apps & Data
Solutions
Solutions
Enablement Composition
Client
Platform
(into)
Client
Platform
(onto)
Applications
&
Services
Applications
&
Services
WCT ME
WCT ME

WCT ME – How do you get it?
Development
Working Solution
My Device(s)
My Device
Application
And
Middleware
Shipping Solutions
+
Runtime License
(either LPP or OEM)
Distribution
2
Evaluation
License
1
Download from:
www.ibm.com ->
trials and betas ->
wireless-voice-pervasive
Built in support:
20+ Operating Systems and
5 Instruction Sets including
Windows and Linux for desktop
3
Development
License

WCT
(JDBC)
DB2e or
Cloudscape
JMS (MQe)
SyncML
Libraries
Application
(MDBs)
WEDM
(Tivoli DM)
Application
(Web Services)
OSGi Device
Agent
WECM WECM
ServerClient
Managed
Services
Web
Services
Consume and publish Web Services
Synchronize relational data
Send and receive
secure transactions
Install, configure, maintain and add software
Operate over secure, optimized,
roaming network connections
WCT ME – How does it connect?
WebSphere App
Server
DB2e
Sync Server
MQe
Gateway
MQ
Server
DB
SyncML
Libraries
Synchronize objects

WCT ME – Enterprise Offering
Managed Client
Services
Access/Platform
Services
(Eclipse RCP+)
EO
Components
Java Virtual Machine (IBM J2SE 1.4.2 with J9 Technology)
Java Class Library
Framework
JMS
MQe
JDBC XML Parsing Web Services
OSGi Service
Implementations
DB2e w/
ISync
Web Container
Servlet/JSP
OSGi Device
Agent
SyncML
Framework
bridge
Core Extension Point Framework
JFace SWT
Generic
UI frame
Update
Manager
Help UI
(with Lucene)
Workbench UI
Web Application View
with SWT Browser Component Desktop (Perspective) Preference
Pages
Enterprise and ISV Applications

A few examples
Vision Execution

Some testimonies from the eco-system

WCT ME – How does Lotus use it?
Workplace Client for Lotus Workplace Messaging and Documents
Java Class Library
Framework
Managed Client
Services
Access/Platform
Services
Workplace
Portal
Others Cloudscape
xAction
Container
OSGi Device
Agent
SyncML
Framework
bridge
Core Extension Point Framework
JFace SWT Generic UI frame
Workbench based
aggregator and other
UI Components:
Rich text editors,
embedded browser Lotus RCP (common platform services)
SWT UI
Components
WSRP
Consumer
WSRP
Producer
SWT
Java apps
Lotus Workplace Applications

Gateway type deployments
Intelligent Industrial
Network Gateways
Telemetry Devices
SCADA* Systems
Enterprise Portals
Mobile Devices
WebSphere
integration brokers
Enterprise
Applications
(ERP, SCM, CRM...)
Remote offshore drillingRealtime pipeline flow
Pay as you drive insurance
Remote UI/data collection

Example ISV: Blue Mart
Blue Martini Components
Blue Martini Components
Blue Martini CRM applications
Leverage the IBM Workplace
Client Technology Micro
Edition
Deploy on intermittently
connected mobile devices
Enables mobile, guided
selling interactions for
increased productivity
> Configurations
> Quotes
> Proposals
> etc.
Provide same UI and function
as the web-connected
applications
Local DB
Interactive
Selling Mobile
Config Pricing Quote
Oppty &
Leads Proposals Sync
Agent
Messaging
Engine
Data
Engine
HTTP
Interactive
Selling Web
IBM WebSphere
Application Server
Database Mgmt.
Transaction Mgmt.
Platform Mgmt.
Enterprise Middleware
IBM Workplace Client
Technology
Micro Edition
Database Mgmt.
Transaction Mgmt.
Platform Mgmt.
Enterprise Access
Embedded JVM
HTTP

Example Enterprise: a
Who: Nissay (Nippon Life Insurance Company) is
Japan’s #1 insurance company
Why: Extend their Insurance Adjustor application
for their mobile field force (70,000+ employees)
increasing productivity and customer satisfaction
What: Allow Nissay’s mobile adjustors to input
policy data when offline and seamlessly offer quotes
or search for policies when connected
How: IBM Workplace Client Technology Micro
Edition is used to enable a “sometimes connected”
environment (runtime and tools)
When: Complete and in rollout.

Example: IBM Retail Store Integration
Framework (SIF)
New “anywhere”
touch points
Cart-mounted
“personal
shopping”
devices
KiosksDigital
multimedia
displays
Electronic
signs
Electronic
shelf
labels
PDAs
Cell
phones
Electronic
scales
RFID
readers
Web
tablets
Enterprise Web
Web channelEnterprise applications
Web application platform
IBM Store Integration Framework
Business
Integration
Enterpri
se
StoreIntegrationFrameworkEnterprise
Smart card
reader
Self
checkout
Point of
sale
Biometric
payment system
RFID payment
system
POS
server
Application
server/Premise
Server
Advanced POS
technologies
IBM Store Integration Framework supports both wired and
wireless devices

Design: The Personal Shopping Assistant
hardware
• Key design requirements
– Consumer-friendly
• Pick up & put away
• Easy to see
• Encourage self-scanning
• Fun for the whole family
– Mobile
• Weight vs. battery life balance
• Battery life shouldn’t be a shopper concern
– Retail environment hardened
• Hardened
• Spill proof
– Location sensitive
• Precision: 4-6 feet
• Easy to install and maintain

Banking Opportunity
Architecturally, it looks like the retail store topology
Central Site
Teller
Platform
Centralized
Servers
Branch
Internet Call Center
Financial Adviser
Backend
Systems
Branch Server
ATMs

OSGi WC 2004 IBM demonstrations
• Mobile Insurance Adjuster Application
– One application across the Nokia 9500, PocketPC, and Windows Laptop
• Developer tooling
– OSGi, Web Services, Eclipse, Extension Services
• RFID Solutions
– TCG Trusted Platform Module
– Integrated with WCT ME (OSGi) via partner Arcom hardware
• Telematics Solutions
– Telematics Reference Implementation
• Cross-device stateful relocation of applications
– Research enabling greater degrees of mobility and multi-device interaction
• Device Management (OMA DM and Mobile Expert Group direction)
– WebSphere Everyplace Device Manager managing a Nokia 9500
• xCP
– AACS rights management via OSGi bundles (includes trusted framework)

Looking forward…
Vision Execution

What makes a complete device specification?
Device
Platform
Connectable
Standalone
Data Support
Protocol Support
Platform
Connectable
Standalone
PhysicalDevice
UserExperience
O
n
Device
Program
m
ing
Interfaces
Connections
InfrastructureInfrastructure

Platform specifications
0
ConnectionDevice(S)(A) PIProtocolData
1
ConstraintsSpecifications
2
…
N

Client side middleware industry
standards
• Technical completeness requires specification of the following:
– Data Formats
– Communication Protocols that deliver and consume those Data Formats
– Programming Interfaces
– declarative "Service" interfaces
– imperative bindings
• Interoperability completeness requires the following:
– Control (fair and transparent multi-lateral governance)
– Completeness (see above)
– Compliance (uniform adherence to the specs that maximizes
interoperation)
– Cost (equitable licensing of essential IPR; brand value flows equally to all
"members")
SOA requires “Client” side middleware industry standards

An example – one view of the mobile
constellation
Eclipse.org
(API, Data, Protocol)
org.eclipse.*
TCG
(Data, Protocol)
Netscape
JCP
(static API)
java.* ; javax.*
W3C
(API, Data,
Protocol)
SOAP
HTML
DOM (org.w3c.dom.java.*)
HTTP
XML
VoiceXML
X+V
SAX
(API)
org.sax.*
230
185
135
120
75
172
218.219
232
SSL
TCG
Mobile
WG
TCG
Infrastructure
WG
IETF
(Data, Protocol)
TCP IP
OSGi Alliance
(Data, Protocol,
SPI, dynamic API, service interface)
org.osgi.*
Mobile Expert Group
CPEG
Execution
Environment
MIDP
Container
Service
Programming
Interfaces
Service
Framework
Other
Services
Application
Model
UI
Service
SWT jFace
OMA
(Data, Protocol)
Device
Mgmt
Data
Sync
LocationDRM
RCP

Platform Specifications – What is the
role of OSGi going forward?
• How do we manage the relationship between
the constituent bodies of a platform ?
• Does dynamic platform composition affect
licensing models for component specifications ?
• Open Source versus Open Standards ?
• How “Open” does the standard need to be ?
• Should OSGi specify other bindings for
declarative services ?
• Should we begin new verticals ?
Lots done… Lots to do!

Questions?

From Vision to Execution (and back) - Jim Colson, IBM

More Related Content

What's hot (20)

Viewers also liked (13)

Similar to From Vision to Execution (and back) - Jim Colson, IBM (20)

More from mfrancis (20)

Recently uploaded (20)

From Vision to Execution (and back) - Jim Colson, IBM