1 / 7

Web-Enabled RTI An XMSF Exemplar Katherine L. Morse, Ph.D., SAIC Ryan Brunton, SAIC

Web-Enabled RTI An XMSF Exemplar Katherine L. Morse, Ph.D., SAIC Ryan Brunton, SAIC David Drake, SAIC. Goals / Accomplishments. Build a prototype HLA federation using XMSF compliant Web Services for communication between federates in an existing federation

keefe
Download Presentation

Web-Enabled RTI An XMSF Exemplar Katherine L. Morse, Ph.D., SAIC Ryan Brunton, SAIC

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. Web-Enabled RTIAn XMSF Exemplar Katherine L. Morse, Ph.D., SAIC Ryan Brunton, SAIC David Drake, SAIC

  2. Goals / Accomplishments • Build a prototype HLA federation using XMSF compliant Web Services for communication between federates in an existing federation • HPAC and ITEM in the WMDOA federation • Take initial steps to making an existing federate callable as a Web Service • SOAP formatted RTI calls employing BEEP communication layer • HLA specification compliant (DMSO RTI) • Bi-directional calls allow Federate Ambassador call backs • Encapsulation of non-reentrant RTI libraries • Permits multiple instances of Web Service

  3. ITEM and HPAC Integrated Display

  4. Communication Architecture for Demonstration Windows Platform Sun Platform HPAC RTI RTI & Federate Ambassador Stubs Remote RTI &FederateAmbassadors ITEM Simulation Engine RTI API RTI API SOAP Services SOAP Services SOAP/BEEPCommunicationsover “Internet” BEEP Communications BEEP Communications

  5. Example SOAP Data Exchange • Request to getAttributeHandle <?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Header/> <soap-env:Body> <getAttributeHandle> <whichClass>15</whichClass> <theName>testClass</theName> </getAttributeHandle> </soap-env:Body> </soap-env:Envelope> • Response <?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Header/> <soap-env:Body> <result_getAttributeHandle value="42"/> </soap-env:Body> </soap-env:Envelope>

  6. Why is This Important? • Implements bi-directional communication initiation over the Web • Superior to http with its uni-directional initiation • http unsuitable for supporting simulation communication patterns • Enables existing HLA compliant federates to be integrated easily over the Internet • Including through most firewalls with minimal reconfiguration! • Demonstrates Web Service wrapping of existing architectures • Approach can also be applied to DIS, ALSP, etc.

  7. Next Steps • Document current approach as an XMSF Profile • Set of protocols used • Set of data and metadata standards used • Detailed description for applying protocols and data standards to implement the architecture • First draft in 2003 Euro SIW paper • Extend current implementation • Expand the set of HLA services supported • Develop Web Service wrappers for launching federates remotely • Enables composability of federates stored in repositories • Identify partnership opportunity for operational deployment of this XMSF Profile Done Done

More Related