1 / 8

SOA in a Military Environment Technical Architecture Implications

Interoperability Clearing House. SOA in a Military Environment Technical Architecture Implications. Robert Babiskin, COO John Weiler, Executive Director Info@ICHnet.org 703 768 0400 www.ICHnet.org.

sulwyn
Download Presentation

SOA in a Military Environment Technical Architecture Implications

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. Interoperability Clearing House SOA in a Military Environment Technical Architecture Implications Robert Babiskin, COO John Weiler, Executive Director Info@ICHnet.org 703 768 0400 www.ICHnet.org This document is confidential and is intended solely for the use and information of the client to whom it is addressed.

  2. Legacy A DIB Legacy A Legacy A A A A Service Y Service Z Service W A A A A A A SOAs will be built on ESB-based Infrastructure • Assumes heterogeneous services, applications • Policy and Governance managed by • Service Level Agreements (SLAs) • Focus on specifications, interoperability, • integration • Works well with a hybrid process and • capability enterprise (e.g., Afloat, NMCI, • USMC, DoD/J/S, Coalition, etc) • Redundancy, disconnected operations • Failover, Contingency of Operations • Performance • Other functional/operational requirements • (e.g., local “working” copies) • Varying mechanisms, trust models • Replication, Synchronization, Messaging, • Orchestration • One/Two way trusts A Service X A A TAPE Security Svc TAB Legacy E S B Msg Svc Portal Flow Mgr

  3. SOAs will require a Replication Architecture C4I Intel

  4. ESB function-1 ESB function-n Service Infrastructure ESB Real-time SOA Fabric will be on a Shared Service Infrastructure with Multiple C4I ESBs Message Svcs Data Svcs Security Svcs User Interactive Svcs Data Svcs Security Svcs Custom Svcs Service Management CANES SOA ESB(s)

  5. ESB function-1 ESB function-n Service Infrastructure Authorization Service ESB Real-time SOA Fabric will require “Common” Authorization Services e.g. JEB Token Service Authentication Create Token Authentication Service Credentials SAML Token Authentication Authorization SOAP+ SAML PDP SOAP+ SAML PEP Web Service 1 PDP PEP Web Service 2 Authorization CANES SOA ESB(s) PEP Web Service 3

  6. ESB function-1 ESB function-n Service Infrastructure Authorization Service Service Management ESB Real-time SOA Fabric will support a Heterogeneous Client Environment OperationalC2 Defensive C2 Support C2 Tactical Data Links Browser Application Client Mobile CANES SOA ESB(s)

  7. ESB function-1 ESB function-n Service Infrastructure Authorization Service Service Management ESB Real-time SOA Fabric will need a “Standard”Service Management Metadata/UDDI Credential Service Registry Composition/ WSDL Monitoring/ WSDL SVC Mgt SOAP/HTTP Application Core Service Process Logic Data/Content Orchestration, Msg’g Routing, Discover Registry, Security SOA Stack Legacy CDNE Intel Tracks Image Sensor Policy GIS ROE BFT CANES SOA ESB(s)

  8. ICH’s Architecture Assurance Method will define SOA Solution Architecture Components • Common SOA capability alignment and prioritization that will be shared • Identification of interoperability capabilities • Assessment of Service Components that will be shared • Determine interoperability of relevant SOA industry stacks and determine the tradeoff in capability versus. Adapters versus. Business case differences AAM

More Related