Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Enterprise Mobility with Mobile OSGi

It is evident that the market for mobile enterprise solutions grows rapidley. A lot less obvious are the technological trends on which mobile enterprise solutions are going to be built upon. Mobile OSGi technology (i.e. JSR 232, Eclipse eRCP, Sprint Titan) is one of the platforms that enters the market and thus competition against other platform concepts such as MIDP, native applications, Google Android, etc. What is it that mobile OSGi technology has to offer?

Terry, thanks for your interest in Mobile OSGi. OSGi can easily control the lifecycle of a native app (Win Mobile, Android, etc.) meaning install, uninstall, start or stop an application. This can be done via a remote management server talking to the OSGi stack on the device. If some specific communication with native app is required (invoking its APIs) then a Java/OSGi module is required to proxy such requests

While normally the target systems and applications of a Remote Admin service should/are usually OSGi based/OSGi apps, they don't necessarily have to be - Your native non-OSGi application can still be managed remotely via a client OSGi framework using JNI (Java Native Interface), which provides/receives calls from native, non-java/osgi applications. This assumes your native application has this interfacing capabilities included in order to provide a streamline interoperability between the OSGi (the agent) and the native application (client).

It is true though that you gain more advantages/features by using also OSGi based applications, which they all can be precisely managed remotely with a larger set of capabilities than for native applications (due to the inherent advantages of the OSGi model).

I am not highly tech person but more on it marketing. ^^ and need your help on the following question. Am I correct to understand that Mobile OSGI (Enterprise) remote admin can control App (let's say Native Win Mobile developed in C++)? or do we still need to develop an app in Java to be controlled or to communicate with OSGI remote admin? this has been debate among none tech persons around me for some time. would Appreciate your answer.

Enterprise Mobility with Mobile OSGi

2.
<ul><li>Explain how Mobile OSGi is positioned in the market of mobile application platforms </li></ul><ul><li>Explain how mobile enterprise developers benefit from using Mobile OSGi </li></ul><ul><li>Provide overview of market uptake </li></ul>Objectives of this Talk

4.
The mobile enterprise market place and how Mobile OSGi fits into the picture

5.
The Business Case: Big Time! <ul><li>Total US mobile enterprise application service revenues to grow from $9b in 2007 to $13b in 2012. [1] </li></ul><ul><li>“… mobility management services revenues to grow at a CAGR of 81% through 2013 to total of $30b” [2] </li></ul>[1] Source: Insight Research Corporation, http://www.insight-corp.com [2] Source: ABI Research, http://www.abiresearch.com/abiprdisplay.jsp?pressid=1030

10.
Conclusion on the market space <ul><li>The Problem: </li></ul><ul><ul><li>Broad range of advanced technical requirements </li></ul></ul><ul><ul><li>Very complex and rapidly changing eco-system </li></ul></ul><ul><ul><li>High fragmentation in available technologies </li></ul></ul><ul><ul><li>Huge diversity of different device configurations </li></ul></ul><ul><li>Challenges to Enterprises: </li></ul><ul><ul><li>Selection of the right target platform(s) for their apps </li></ul></ul><ul><ul><li>Remote manageability of those platforms </li></ul></ul><ul><ul><li>Sustainability of their investments </li></ul></ul>

11.
Where Mobile OSGi fits in Phone Operating System Application Execution Environment Remote Access Applications By combining some of the platform elements and by making them available cross-platform, Mobile OSGi de-fragments the market! Mobile OSGi

15.
<ul><li>The Dynamic Module System for Java TM </li></ul><ul><li>Specification developed by the OSGi Alliance </li></ul><ul><li>Adopted by a rapidly growing community </li></ul>OSGi is a Worldwide Standard

21.
<ul><li>Mobile phone as part of SOA infrastructure </li></ul><ul><li>Distributed services between osgi container </li></ul><ul><li>Dupport for legacy server and clients </li></ul><ul><li>Discovery support </li></ul><ul><li>Protocol agnostic </li></ul><ul><li>Declarative configuration on top of the service registry </li></ul>Key feature: Remoting

22.
<ul><li>Security model based on Java 2 </li></ul><ul><li>Permissions are managed through Permission-Admin and ConditionalPermissionAdmin </li></ul><ul><li>Static device policy definition mapped into dynamic model </li></ul><ul><li>Device policy can be changed and tailored to the specific needs of your enterprise (provided the operator grants you that privilige) </li></ul>Key feature: Security & Policy Model

23.
<ul><li>OSGi ApplicationAdmin enables different app models to map apps into the service registry </li></ul><ul><li>OSGi acts as “meta container” for applications and abstracts the app model specifics </li></ul><ul><li>This enables: </li></ul><ul><ul><li>New powerful app models can be introduced, even post shipment </li></ul></ul><ul><ul><li>Developers can pick the model they like best </li></ul></ul><ul><ul><li>End users get seamless experience on the phone, one front-end to all apps, regardless their types </li></ul></ul>Key feature: Multi App Model Support

41.
<ul><li>Still it can’t be run on all devices </li></ul><ul><ul><li>CDC/FP=3MB + OSGi=1.2MB + Service=1.3MB = Total=5.5MB </li></ul></ul><ul><ul><li>eRCP/eSWT + simple app adds another 3MB </li></ul></ul><ul><li>It does not present a UI story by itself </li></ul><ul><ul><li>App models depend on UI toolkits </li></ul></ul><ul><ul><li>UI toolkits might not be available across all platforms </li></ul></ul><ul><li>Integration of CLDC based component JSRs into CDC is a challenge </li></ul><ul><li>Mobile OSGi not yet available on all platforms </li></ul><ul><li>Very little market penetration at the moment but that will change soon (refer to Sprint Titan) </li></ul>Does Mobile OSGi solve all your problems? No!