1 / 26

Tech Spec Overview: Introduction

Tech Spec Overview: Introduction. OSGi R3 and Remote Management Ertico/OSGi meeting Jan 22, Brussel Introduction. What is the OSGi Service Platform?. A Java framework for developing remotely deployed service applications, that require: Reliability Large scale distribution

bisa
Télécharger la présentation

Tech Spec Overview: Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tech Spec Overview: Introduction OSGi R3 and Remote Management Ertico/OSGi meeting Jan 22, Brussel Introduction

  2. What is the OSGi Service Platform? • A Java framework for developing remotely deployed service applications, that require: • Reliability • Large scale distribution • Wide range of devices • Collaborative • Created through collaboration of industry leaders • Spec 2.0 publicly available at www.osgi.org • Spec 3.0 soon to be released

  3. When is the OSGi Service Platform feasible? • The end user is interested in using services any time, not managing a system • The system must be extendable and upgradeable • The system is (intermittently) connected to a network • Remote Management is provided by an Operator

  4. Example OSGi deployments • Telematics • Residential gateway • Wireless Base Station • Kiosk • Web pad • Settop box • Vending Machine

  5. Essentials • Reliable • Large-scale deployments fail without extremely high reliability • Portable • Attract third-party developers to create essential innovative services • Embedded systems come in many different flavors • Dynamic • Allow configuration to adapt to user & operator needs over time • Secure • Protect service providers from each other • Guarantee a prescribed quality of service • Scalable • Members have very different configurations for their deployment of OSGi frameworks

  6. Bundle Bundle Bundle Bundle (Application) = service interface exported and imported by bundles OSGi Java VM Operating System Driver Driver Driver Hardware OSGi Environment

  7. Core Functions • Life Cycle Management • Install, Start, Stop, Update, Uninstall • Registry of services with notifications • Package and version management • Open remote management architecture • Strict separation of specifications and implementations • multiple implementations

  8. Framework Entities OSGi Framework Bundle A {} Bundle B {} Bundle C {} = service, java interface

  9. Bundles • A bundle is the deliverable application • Like a Windows EXE file • A bundle registers zero or more services • A service is specified in a Java interface and may be implemented by multiple bundles • Searches can be used to find services registered by other bundles • Query language • The Framework itself is represented as the system bundle

  10. Collaborative model • More than an Applet, MIDlet, Xlet runner • Bundles can collaborate through: • service objects • package sharing • A dynamic registry allows a bundle to find and track service objects • Framework fully manages this collaboration • Dependencies, security

  11. No management bundles Service registry No collaboration packages No package management (versions!) packages No native code Collaborative model How does OSGi relate to MIDP, Java TV, Browsers Java Application Manager Midlet, Xlet, or Applet Midlet, Xlet, or Applet JAVA Operating System Hardware

  12. Service Registry • The Framework Service Registry is available to all bundles to collaborate with other bundles • Requires permission • Under operator control • Services are associated with properties • Query language to find appropriate service • Bundles can update the properties

  13. R1 R2 R3 Preliminary Position XML Parser Service Measurement Preferences Service User Admin Device Manager Http Service Log Service Configuration Admin Service Tracker Wire Admin Connector Service Jini Service UPnP Service Package Admin Permission Admin URL Handler Start Level Release 3 Services (Preliminary) OSGi Specifications Content Framework Execution Environment

  14. Security • OSGi (optionally) uses Java 1.2 Security based on Permission classes • This automatically verifies the call-chain • Applications providing secure functions can limit the call-chain check • Permissions can be managed by the Management Agent through the PermissionAdmin service • Java Security is flexible but very complex and CPU intensive

  15. Management • Framework provides mechanisms, but is policy free • I.e. a bundle can be installed but from where is left open • Management policy provided by a bundle specific to the operator: • Called a Management Agent • Management policies made/selected by the operator

  16. R3 Reference Architecture

  17. Application Models • Gateway Model • Archetypical OSGi model where an Operator manages a box used by an end-user • Industrial Model • The Operator uses OSGi to manage an industrial system like for example GSM Base Stations • Self Managed Model • Similar to PC model where the end user is his own Operator • Services in the network model • Implemented by Telia

  18. Remote Management Reference Architecture • Goal: • Interoperability between management systems and OSGi Service Platforms. Management Systems Protocols OSGi Service Platforms ACUNIA SNMP ProSyst IBM Tivoli CIM IBM HP OpenView Propriet. Gatespace ... ... ...

  19. R3 Remote Management Reference Architecture

  20. Remote Management Reference Architecture • Standardization of protocols not necessary because new protocols can be downloaded • An SNMP bundle from vendor X will connect all SNMP management systems to any OSGi Service Platform • Management primitives are available as OSGi APIs • life cycle management • monitoring • configuration management • security

  21. Remote Management • Model delivers interoperability • Does not address management applications interoperability (I.e. JSR 124) Management Systems Protocols OSGi Service Platforms Gatespace ProSyst/IBM/VDO Gatespace/Acunia... SNMP Solstice ProSyst/IBM/ /VDO Gatespace/Acunia/... CIM Ericsson eservices Propriet. ACUNIA/IBM/ VDO Gatespace/ProSyst/... ... ... ...

  22. Remote Management • Management APIs based on bundle, not end end user service provisioning • An end user service can consist of multiple bundles • Dependencies between bundles should be managed by the server • I.e. bundle X requires bundle Y and Z • Bundle's manifest supports many different schemes

  23. Initial Provisioning • How does the first Management Agent get into the Service Platform? • This process is called Initial Provisioning • Recommended specification R3

  24. Send url with SPI Send ZIP file with bundles and configuration info Optionally Repeat Install Management Agent bundles Communicate With a specific protocol Initial Provisioning • The Service Platform contacts the remote manager with a URL • ZIP file contains bundles that are installed and started Remote Manager Service Platform bundles

  25. Initial Provisioning • Initial Provisioning is an abstract specification with concrete mappings for the following URL schemes: • HTTP:, standard HTTP urls • HTTPS:, secure HTTP • RSH:, uses a shared secret when HTTPS is too heavy • FILE:, initial Management Agent can come from file system • Manufacturers can easily provide support for • Smart cards • Removable disks

  26. Questions??

More Related