slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Gateways Background PowerPoint Presentation
Download Presentation
Gateways Background

Loading in 2 Seconds...

play fullscreen
1 / 21

Gateways Background - PowerPoint PPT Presentation

  • Uploaded on

Automated Tools for Gateway Selection and Configuration 12S-SIW-051 2012 Spring SIW March 26-29, 2011. Gateways Background. Multi-architecture LVC environments are commonplace in support of DoD distributed test and training events

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

Gateways Background

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Automated Tools for Gateway Selection and Configuration12S-SIW-0512012 Spring SIWMarch 26-29, 2011

    2. Gateways Background • Multi-architecture LVC environments are commonplace in support of DoD distributed test and training events • There are numerous difficult technical issues that must be addressed when integrating simulations across different simulation architectures • Middleware incompatibilities • Dissimilar development processes • Dissimilar metamodels for runtime data exchange • Solutions to these issues can be extremely resource intensive to implement and inadequate testing can adversely affect the quality of the simulation results • There is a need to improve the quality and reduce the time and costs associated with the development of multi-architecture LVC environments • Original motivation for the Live-Virtual-Constructive Architecture Roadmap (LVCAR) effort

    3. Gateway Challenges • Despite the many documented success stories associated with the use of gateways to facilitate LVC interoperability, there are also some significant issues that impact technical, schedule, and cost risk • No central “marketplace” of gateways • Few mechanisms for user to determine what reuse opportunities are available • No mechanisms for direct comparisons of gateways • Gateways built for specific needs • Not built for reuse/not built for extensibility • Extensive duplication of existing gateway capabilities • Process of developing mappings (i.e., translations) among simulation data elements is very time consuming and error-prone • Little reuse of mapping data or automated tool support available • Process of gateway configuration is highly manual and varies from gateway to gateway • Potential barrier to migrating to better gateway products

    4. Live-Virtual-Constructive Architecture Roadmap (LVCAR) Implementation The DoD Way Ahead for LVC Interoperability LVCAR Study Implementation of LVCAR Study Recommendations LVCAR – Implementation Project (LVCAR-I) Gateways/Bridges Common Capabilities Common Object Models SOA Pilot We Are Here

    5. LVCAR-I Gateways Effort – Initial Products • Gateways Characterization Report • Identified capabilities offered by a wide range of different existing gateways • Mapped user requirements to these capabilities to identify gaps • Gateway Configuration Model (GCM) • Identifies an explicit set of gateway requirements, and discusses how the emerging gateway products and processes will address those requirements • Gateway Capability Description (GCD) • Delineates the various capabilities that individual gateways can offer to user programs, along with specific levels of implementation for each unique capability • Gateway Performance Benchmarks (GPB) • Identifies specific gateway performance measures, along with use cases that describe how and where these measures should be applied • Gateway Tutorial • Discusses basic technical concepts and provides user guidance on acquiring gateways

    6. LVCAR-I Gateways Effort –Current Products • Developed a common Gateway Description Language (GDL) • A machine-readable format/syntax, for describing both user gateway requirements and the capabilities that individual gateways can offer • Supports user discovery of needed gateway capabilities • Developed a common SDEM Mapping Language (SML) • Formalized format and syntax for mappings between different SDEMs • Reduces number of required mappings, and supports reuse of mapping data • Developed an initial repository for GDL-based gateway descriptions • Incorporates applicable search and requirements-to-capabilities matching algorithms • Developed initial tools for GDL and SML file creation/editing • Developed a Common Components Tool (CCT) • Captures gateway initialization data in a common underlying database format • Developed gateway implementation-specific plug-ins • Converts CCT data into the form needed to configure the gateway for a particular application

    7. Gateway Selection Process Repository and Distribution Point Stewards Gateway Developers & Vendors Searchable files describing gateway products using Gateway Description Language (GDL) based on Gateway Capability Description 1. Create files describing gateway products and capabilities using Gateway Description Language (GDL) GDL Editor Exercise Managers and Gateway Users GDL Editor 2. Create search criteria based on high priority capabilities, storing it in GDL format 5. Discuss with Community of Interest: Gateway Developers & Vendors, and other Gateway Users 4. Best Matches from Search Gateway 1: Gateway 2: Gateway 3: etc. GDL EditorSearch 3. Search the GDL file repository and create a Best Matches list 6. Select gateway to deploy based on meeting exercise capabilities, configurability, licensing, and user feedback Reevaluate ✓ Selected Gateway

    8. GDL Editor – Gateway Description & Matching • Gateway Description • Designed to efficiently create GDL files via a GUI-based procedural “wizard” • The tool will step the user through a process to collect requirements via Gateway Capabilities Definition and Gateway Performance Benchmark information • Generates a GDL file for repository archival • Gateway Matching • This capability was designed to aid the gateway user in selecting the most appropriate gateway solution • Creates or imports a user-defined gateway requirements via GDL file • Imports developer-provided gateway capabilities GDL files from repository • Generates a set of best gateway matches for user consideration and archival

    9. GDL Editor User Interface –Capability Definition

    10. GDL Editor User Interface –Capability Definition

    11. GDL Editor User Interface – Requirements Matching

    12. GDL Editor User Interface – Requirements Matching 12

    13. Gateway Mapping and Configuration Process Gateway Gateway Configuration written in Gateway-Specific Format Mapping Rules Filtering Rules Filtering Rules • Greatly enhances retention of simulation mappings and gateway configurations Simulation Component Simulation Component Simulation Component Simulation Component Simulation Component Simulation Component Simulation Architecture Simulation Architecture SDEM SDEM • SDEM, mapping, and configuration reuse permits reduced gateway configuration cycle effort & time SearchableSML Remote Repository Library CCT with Gateway-Specific Plug-in Searchable SML Local Library Simulation Data Exchange Model (SDEM)-to-SDEM mapping written in SML 2. Create/modify Gateway Configuration using Common Components Tool (CCT) All Files Stored SML Editor 1. Define/Reuse Mapping using SDEM Mapping Language (SML) Editor

    14. Simulation Data Exchange Model (SDEM) Mapping Language (SML) Editor • Designed to efficiently create SML files via a GUI-based procedural “wizard” • The tool will step the user through a process to create a mapping file between two SDEMs • Imports the needed SDEMs • Exports the SML compliant with SML schema • The tool will generate an SML file compliant with the SML schema • If desired, upload the file to a repository for archival and reuse

    15. SML Editor – Defining the Mapping Between SDEMs

    16. Common Components Tool (CCT) • Designed to aid the gateway developer to extend gateways to new Architecture/SDEMs • Imports SDEMs in their native format (OMT, TDL, ANDEM, …) • Imports SDEM mapping file in SML format • Imports gateway configuration data in GCL format • Generates a database with mapping information • Provides a plug-in architecture to support specific gateway implementations • Allows the gateway developer to: • Access mapping data without having to import multiple file formats • Create a gateway-specific CCT plug-in to generate required inputs for their gateway • Can be code, file, or a combination of both • Quickly extend their gateway to support new user mapping requirements

    17. Common Components Tool –Architecture CCT SML Loader Gateway Specific Writer Plug-in Gateway Developer API GCL Loader CCT Database ANDEM Loader ASF Loader API ASF Loader Plug-in CCT Core Architecture Specific Format ( i.e. OMT, TDL) Loaders CCT Loaders Gateway Specific Writers

    18. Employing Stored SML in the CCT to Generate a Gateway Common Components Tool Configura-tion Files CCT User Interface Gateway-Specific CCT Plug-in SML Database SML Database SML Data SML Data Software Source Executable Distributed Simulation: Federation/Exercise Generated/Configured Gateway Federation/Exercise Distributed Sim API Distributed Sim API

    19. CCT Demonstrated: Gateway Builder Employed for creating MATREX to TENA-Platform Exercise Common Components Tool CCT User Interface Microsoft Visual Studio Project Gateway Builder Source Files Gateway Builder CCT Plug-in SML Database SML Database SML Data SML Data MS Visual Studio Compilation Example Distributed Simulation: MATREX Federation Generated and Configured Gateway TENA-Platform Exercise Viewer MATREX Federate TENA/CORBA API

    20. LVCAR Gateways Effort – Next Steps • Improve the usability of the GDL and SML Editors • Interface enhancements, better documentation • Develop a common implementation-independent Gateway Configuration Language (GCL), in a machine-readable format/syntax, for describing gateway configuration data • Includes both specification and editing tool • Implement needed extensions to the CCT and gateway plug-ins • Other architectures/SDEMs, and potentially entirely new gateway plug-ins • Develop new tools/methodologies for gateway benchmarking • Develop more advanced, hands-on “Gateways 201” tutorial • Community outreach • Special Gateways Event at Fall 2012 SIW, and potentially others

    21. Questions and Feedback