1 / 11

Usage of Enterprise OSGi inside Siemens:

Usage of Enterprise OSGi inside Siemens: Siemens Communications, Enterprise Systems HiPath product family SCA and OSGi integration e.g. Service Delivery Platform e.g. Usage of Enterprise OSGi parallel to JEE Pervasive Computing e.g. Daidalos EU project

adamdaniel
Download Presentation

Usage of Enterprise OSGi inside Siemens:

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. Usage of Enterprise OSGi inside Siemens: • Siemens Communications, Enterprise Systems • HiPath product family • SCA and OSGi integration • e.g. Service Delivery Platform • e.g. Usage of Enterprise OSGi parallel to JEE • Pervasive Computing • e.g. Daidalos EU project

  2. HiPath Application Product LineA SOA based product line architecture prescribes development of product specific elements as well as for common SW assets. These elements are hosted by a lightweight (server side) service execution environment. The OSGi Service Platform is used at the very core. HiPath ProCenter HiPath OpenScape Media Portal Suite HiPathOpenStage HiPath 8000 Assistant

  3. Interest in Enterprise OSGi • driving factors • increased availability, scalability, reliability • integration into heterogeneous enterprise environments

  4. Interest in Enterprise OSGi • extension of the OSGi service model • support of multiple containers in a single logical container • quality of service • performance framework • enhanced enterprise security • authentication, authorization (inter and intra container) • large scale deployment support • multi node, update/patch support

  5. SCA and OSGi • Our Interest • OSGi Binding • OSGi implementation type • OSGi-based SCA container • What’s missing? • SCA based component model (e.g. remote services versus components) • Improved Lifecycle and Enterprise suitable Dependency Management • Inter-Container Communication • Service Discovery • Availability

  6. Daidalos Interest in Enterprise OSGi • Inter-Container Communication API • Concepts and APIs for dependability mechanisms • Generic Service Discovery Concept

  7. Backup

  8. extension of OSGi service model • distribution over multiple containers • distinction of service vs component • support for runtime AOP, e.g. interceptors, proxies • enterprise style Declarative Services • public vs private properties • better integration with CAS • late injection of optional dependencies • declared object dependencies • availability of service instances because of changes to properties or -> modification of existing DS specification

  9. multiple containers • inter container communication • integration into existing and new ESBs • support for different communication patterns, e.g. request-reply, request-multiple-reply, publish-subscribe, push-poll • distributed (scaled) service registry • distributed or global configuration, e.g. central master configuration • support for migration of configuration

  10. integration scenarios • ESBs • corporate LDAP • user & identity systems • management applications • end user UIs

  11. OSGi service enhancements • MetaType service • additional attributes like readonly etc. • ConfigurationAdmin service • better support for persistent data

More Related