Download presentation
Presentation is loading. Please wait.
Published byBeverley Thompson Modified over 8 years ago
1
Data Sharing Service Kiran Devaram Samatha Gangapuram Harish Maringanti Prashant Shanti Kumar Pradeep Tallogu
2
Overview CORBA specification CCM Specification Middleware description Demo of Existing System Project scenario Project scope List of assumptions
3
CORBA specification Common Object Request Broker Architecture An architecture and specification for creating, distributing, and managing distributed program objects in a network
4
Object Semantics Objects Requests Object creation and Destruction Types Interfaces Value types Abstract Interfaces Operations Attributes
5
ORB request path
6
Client Request Path ORB Core Dynamic Invocation IDL Stubs ORB Interface Static IDL skeleton Client Object Implementation Dynamic skeleton Object Adapter
7
ORB Structure
8
Corba Component Model (CCM) CORBA Component Model (CCM) is a specification for creating server-side scalable, language- neutral, transactional, multi-user and secure enterprise-level applications.
9
Typical CCM Specification consists CCM Containers CORBA components that run in these containers Portable Object Adapter (POA) Object Request Broker (ORB) other CORBA object services like CORBA Transactions, CORBA Security, CORBA Persistence, CORBA Events, etc...
10
CCM scenario
11
CORBA Component Component is a new CORBA meta-type. Extension of Object (with constraints) Has an interface, and an object reference Also, a stylized use of CORBA interfaces/objects Provides component features (also named Ports) Could inherit from a single Component type Could support multiple interfaces Each component instance is created and managed by a unique component home
12
Component Features Attributes – configurable properties Facets – offered operation interfaces Receptacles – required operation interfaces Event sources – produced events Event sinks – consumer events
13
CORBA Component Component Interface Facet Event sink Attributes Receptacles Event Sources
14
Middleware – Data Service Developed by Rockwell Collins ATC Used to simulate data sharing between components in an aircraft Highlights Data sharing Rate handling Data Staleness handling Bounds checking Error logging Scope for functional increments
15
Data Service [contd..] Basic methods Advertise Subscribe getValue setValue getDataChannel sendGroup
16
Advertise call path Producer Avionics Data Service Data Channel a b c getDataChannel (name) Advertise (…) SetValue
17
Producer & Consumer connections Producer Consumer a b c a b c Data Channel Data Service
18
Project Scenario Number of Components : 3 Technologies OpenCCM – 0.4 OpenORB – 1.2.1 Java Services Data Service Naming Service
19
Existing Architecture Configuration File Producer Consumer and Producer Consumer Data Service Timer Set Data Get Data & Set Data Get Data event
20
Existing system demo
21
getData & setData Up call Set Data Architecture Configuration File (Timer Service) Producer Consumer and Producer Consumer Data Service Up call Wrapper
22
Project Scope Providing up-call capability to Data Service Improving data service’s rate handling mechanism Enhance performance by including thread pool for making component calls
23
Up-Call Management Include new wrapper within the Data Service Resolve component reference through Name Service Receive trigger calls from timer Package component call to include role Retrieve thread from thread pool Make up-call to respective components
24
Data Service Rate Handling Pull - model Store producer proxy reference within consumer proxy Break set data call at producer proxy Look up producer proxy reference at getData call Retrieve most recent data from Producer proxy
25
Thread Pool Implementation Provide thread pool for component calls Resource utilization through pre- spawning fixed number of threads Data Service uses worker thread to make up-call Same thread does a set or get on the Data Item Thread sync maintained between multiple threads
26
Assumptions Only one producer for each data item Maintaining naming convention for each component Scenario architecture is known
27
References Object Management Group – formal specification catalogue Avionics Data Service documentation OpenCCM documentation OpenORB manual
28
Comments and Questions
29
Go Cats Go K-State Beat Nebraska
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.