More Related Content
What's hot (18)
Similar to Managing Complexity in Mobile Application Deployment Using the OSGi Service Platform - Rafiul Ahad, Oracle (20)
More from mfrancis (20)
Recently uploaded (20)
Managing Complexity in Mobile Application Deployment Using the OSGi Service Platform - Rafiul Ahad, Oracle
- 1. © copyright 2004 by OSGi Alliance All rights reserved. Managing Complexity in Mobile Application Deployment Using the OSGi Service Platform Rafiul Ahad, Ph.D. Vice President, Mobile Products and Services Oracle Corporation
- 2. © copyright 2004 by OSGi Alliance. All rights reserved. Managing Complexity in Mobile Application Deployment Agenda • Mobile Application Architectures • Deployment Issues • Managing Mobile Application Deployment • Mobile Application Deployment Using the OSGi Platform • Conclusions
- 3. © copyright 2004 by OSGi Alliance. All rights reserved. Mobile Application Architectures • Browser • Managed code • Native code • Declarative (e.g., JSP, ASP) • Programmatic (e.g., Servlet, CGI) • Business objects (e.g. EJB, Corba) • Services (e.g. Web services) • Information Servers (e.g. Mail, Calendar) UI Rendering Presentation Logic Business Logic Data • Structured data (e.g., SQL data) • Unstructured data • Documents • Multimedia
- 4. © copyright 2004 by OSGi Alliance. All rights reserved. Online Web Mobile Application UI Rendering • Browser Presentation Logic • Declarative (e.g., JSP, ASP) • Programmatic (e.g., Servlet, CGI) Business Logic • Business objects (e.g., EJB) • Services (e.g., Web services) •Information Servers (e.g. Mail, Calendar) Data • Structured data (e.g., SQL data) • Unstructured data • Documents • Multimedia WirelessMedium Pros: • Easy to deploy; no client code • Full-featured applications and real time data • Better security due to well known protocols (wtls,https,..) Cons: • Network latency and coverage can impact usability • Devices may support different mark up languages • Limited capability user interface
- 5. © copyright 2004 by OSGi Alliance. All rights reserved. Online Native Mobile Application UI Rendering • Native Graphics Presentation Logic • J2ME/C# app • C/C++ app Business Logic • Business objects (e.g., EJB, Corba) • Services (e.g., Web services) •Information Servers (e.g. Mail, Calendar) Data • Structured data (e.g., SQL data) • Unstructured data • Documents • Multimedia WirelessMedium Pros: • Usually better user interface • Full-featured apps and real time data Cons: • Network latency and coverage can impact usability • Need to provision, install, update apps • Security of data in transit is a concern
- 6. © copyright 2004 by OSGi Alliance. All rights reserved. Offline Mobile Application UI Rendering • Native Graphics • Browser Presentation Logic • J2ME/C# app • C/C++ app • JSP/ASP Business Logic • Subset of business logic • Subset of data • cached • synchronized Data • Structured data (e.g., SQL data) • Unstructured data • Documents • Multimedia WirelessMedium Pros: • Usually better user interface • Less sensitive to network latency and coverage Cons: • Need to provision, install, and update apps • Data synchronization is difficult • Security of stored data and data in transit
- 7. © copyright 2004 by OSGi Alliance. All rights reserved. Mobile Application Deployment Issues System Issues • Scalable, secure, available system configuration Administrative Issues • Device provisioning – Data center or self service – Parameter, application, and data provisioning • Device Management – Application and data installation and update – Remote diagnostics and repair – Remote lockdown Usage Policy Training
- 8. © copyright 2004 by OSGi Alliance. All rights reserved. Managing Mobile Application Deployment • Understand your users and set the right expectations – Mobile experience is not the same as desktop experience • Understand your system behavior – Scalability • Publish expected response times during hours of operations – Device, network, and server capacities and limitations • Avoid OTA downloads of large amounts of data and apps – Security Vulnerabilities • Assume that the device will be lost or stolen • Centralize the administration as much as possible – The more the user does admin => the more the problems – Centralize application and data provisioning, install, update – Remote diagnostic, repair and lockdown • Consider a mix of mobile application architectures – Offline apps more usable but more difficult to manage
- 9. © copyright 2004 by OSGi Alliance. All rights reserved. Deployment Using the OSGi Platform OSGi Framework Mngt Bndl App Bndl any protocol OS JVM Mobile Device Issues with Current OSGi Deployment Technolog • Each enterprise or operator must write its own management bundle (programmatic); declarative approach needed. • Bundle upgrade is all or nothing; incremental update of bundle needed • Support needed for server initiated communication via SMS • API to collect pertinent device information; locking down devices Server
- 10. © copyright 2004 by OSGi Alliance. All rights reserved. Conclusions • Mobile experience is different from desktop – Design apps with device and network constraints in mind – Online apps are less usable but easier to deploy – Disconnected apps are more usable but difficult to deploy – Mobile applications create additional security challenges • Mobile applications deployment requires centralized – Parameter provisioning – Application and data provisioning – Application install and upgrade – Remote diagnostics, repair, and lockout • OSGi Spec is the only standard for deployment • OSGi MEG starting to address the deployment issues • JSR 232 and OMA DM protocol will lend credibility