IKE2 .


120 views
Uploaded on:
Description
Correspondence Mechanism (Network, Shared Memory, and so forth.) TENA ... Resilience capacity to recoup from application, PC, and system disappointments ...
Transcripts
Slide 1

IKE2 — Implementing the Stateful Distributed Object Paradigm J. Russell Noseworthy j.russell.noseworthy@objectsciences.com

Slide 2

FI 2010, TENA, & IKE 2 How Do They Interrelate? Establishment Initiative (FI) 2010 is a DOT&E/CTEIP program whose mission is to give items to: Enable interoperability among reaches, offices, and reenactments in a brisk, cost-proficient way, and Foster reuse for extent resource usage and for future instrumentation improvements Central Product of FI 2010: Test and Training Enabling Architecture (TENA) to be used at test and preparing extents to advance interoperability amongst focuses and to encourage reusability of benefits among focuses ( http://fi2010.jcs.mil/) IKE 2 is the Middleware Component of TENA Today With IKE 2

Slide 3

What is a SDO? Stateful Distributed Object (SDO) Object Interface Location-straightforward interface to techniques Just like a CORBA interface Publication State Data that is dispersed from workers to intermediaries Dissemination done by means of distribute/subscribe Publication state can be perused as though it were nearby information Publication state is discernible

Slide 4

TENA Application A TENA Application A TENA Application B TENA Application B TENA Application C TENA Application C User Application Code Servant Proxy Servant Proxy Servant Proxy Servant IKE 2 IKE 2 IKE 2 IKE 2 IKE 2 IKE 2 Middleware Communication Mechanism (Network, Shared Memory, and so forth.) Communication Mechanism (Network, Shared Memory, and so on.) What is IKE 2? Middleware that Implements SDOs IKE 2 is middleware interfacing circulated "intelligent reach assets" IKE 2 Combines: Peer-to-associate Paradigm Publish/Subscribe Paradigm Distributed Object Paradigm Observable Distributed Shared Memory Paradigm IKE 2 applications may have: Diverse idleness & throughput needs Hard continuous needs Quality-of-Service needs Security needs Large land partitions

Slide 5

SDOs are Described in TDL What is TDL and Why Use It? TDL influences existing business norms however much as could reasonably be expected OMG IDL gives a strong establishment whereupon to manufacture Stand on the shoulders of mammoths OMG has been creating IDL for a long time Plan to use XML and UML/XMI Take preferred standpoint of expansive (and developing) number of COTS devices TDL presents builds not straightforwardly upheld in IDL Class versus interface has just strategies, no distribution state Extends versus executes Single legacy for classes; numerous legacy for interfaces Publication state Attributes that are dispersed to subscribing IKE 2 applications Client applications advised with production state is changed TDL used to auto-created C++ and IDL

Slide 6

Example TDL & IDL Auto-created from TDL Example.TDL Example/Platform.IDL #include <Participant/Participant.idl> #include <Sensor/Sensor.idl> Module Example { module PlatformIDL { valuetype PublicationState : ParticipantIDL::PublicationState { open twofold fuel; open SensorIDL::PublicationState longRangeSensor; }; interface Servant : Participant::Servant { void move(in twofold x); }; }; }; bundle Example { interface Controllable { string instate(); }; class Participant : actualizes Controllable { string name; long ID; }; class Sensor : expands Participant { string state; string point(in twofold azimuth) }; class Platform : augments Participant { twofold fuel; Sensor longRangeSensor; void move(in twofold x); }; };

Slide 7

IKE 2 Implementation C++ Implementation in Testing Today IKE\'s 2 nd beta discharge has been made IKE 2 might be accessible for your (administration) use Contact me Not certain about business use as of now SDOs support inheritence from different SDOs Subscribers to a base class will get (cut) information from inferred classes SDOs bolster regulation of different SDOs Subscribers to SDOs contained in different SDOs got the contained information IKE 2 is actualized utilizing ACE+TAO IKE 2 utilizes DIME to give information scattering DIME uses TAO\'s Real-Time Event Channel

Slide 8

IKE 2 Uses DIME What is DIME? DIME = Distributed Interest-based Message Exchange Originally created for the RTI-NG (DoD recreation middleware) program Wanted a framework to encourage exploring different avenues regarding different message directing method DIME is an extensible structure for Publish/Subscribe message passing frameworks Publish/Subscribe applications require a way to portray who gets what messages Most existing frameworks have just primitive intends to play out this depiction, e.g., a whole number This weights the application developer with the difficult issue of mapping whole numbers to more elevated amount semantically rich portrayals E.g., Tanks in Bosnia = 7, Tanks in Serbia = 8, and so forth. DIME permits the application software engineer to depict who gets what messages at abnormal state The difficult issues, for example, mapping portrayals to whole numbers is isolated from the application program

Slide 9

Future Work What Future Needs are Envisioned? Where Can We Get More Help from TAO? Constant Support — Many imagined applications have equipment tuned in CORBA Real-Time capacities will be straightforwardly re-utilized Fault Tolerance — capacity to recoup from application, PC, and system disappointments Many imagined applications are mission basic Security — Always essential to the DoD people group Scalability — Some applications might be included several hubs Heterogeneous Communication — support concurrent utilization of various correspondence components (e.g., IP, shared memory) and related steering and chain of command issues

Slide 10

Acknowledgments is appreciative to , the prime contractual worker for the work exhibited here is additionally thankful to the FI 2010 project office for making it conceivable to go to this gathering This work is the result of the cooperation of a group of people: Steve Bachinsky, Jon Franklin, Marvin Greenberg, Rob Head, Don Hinton, Serge Kolgan, Mike Mazurek, Sean Paus, Ed Powell, Ed Skees, Rodney Smith

Recommended
View more...