Beyond Web Services A network-centric approach to system design

Transcription

1 1 Beyond Web Services A network-centric approach to system design David Crute Principal Architect Integrated Systems Division General Dynamics C4 Systems

2 2 Network Services Evolution Software Integration Object Integration Web Integration Open-Ended Network Integration C / S C / S Objects Portable GUIs Web Services Network Appliances Network Services

3 The Future possibly the single-most transforming thing in our forces will not be a weapons system, but a set of interconnections and a substantially enhanced capability because of that awareness. -- Defense Secretary Rumsfeld

4 Current Trend Vs Current Capabilities 4 Data Centric VS Network Centric Data Centric is the current environment Data Centric supports Situational Awareness Traditional Client Server Enables Web Services Network Services can be deployed Today Extends Legacy Systems Effectiveness Provides Resources & Applications in addition to Data across the entire Network Enables time-critical applications Frameworks can let any system work in a System of Systems Environment Empowers Web Services

5 The Vision for Change Joint Vision 2020 Naval Power 21 AF Vision 2020 Army Vision 2020 Marine Expeditionary Maneuver Warfare 5

6 6 Common Requirements Secure C4ISR Information Networks Global Access to Critical Data Information Interoperability Shared Awareness Collaborative Environment Support for Joint/Coalition Operations etc. Requirements Point to the need for a new architecture!

7 The New Imperatives How to Improve Design of large, complex Net-centric capabilities? How to Lower Risks inherent in designing and deploying large, complex Net-centric capabilities? Shape evolution of Enterprise IT Vice 7

8 8 Net-centric Characteristics Heterogeneous Variety is essential and inevitable basis for healthy evolutionary growth and survival within dynamic threat environment Parallel Multiple implementation and concurrent use of components and processes increases speed and provides fail-over capability Market-driven Emphasizes Market principles vice top down direction to optimize Survival of the fit (v. selection of the fittest from a single perspective) Developers experiment early and often to find the right niche Agile and adaptable Capable of rapid reconfiguration to meet new and unanticipated requirements or circumvent disruption Expedient task-oriented collaborations vice static bureaucracy

9 Vision of Networked Services Sensor Systems Command & Control System Network Engagement Systems Targeting Interface Provided by Fire Support Element Viewing Application Provided by UAV Sensor 9

10 10 OSD Vision for the Future A Top Level Architecture Perspective Global Perspective A Network Centric Distributed Multi-INT support System Element Perspective A Deployable, Modular, Scaleable Combat System Component Perspective Parts of the Elements Basic architectural modules

11 11 Next Generation Architecture Network-Centric starts at the system design Everything connected to the network Plug-n-Play System Infrastructure Extend the concept to System-of- Systems Plug-n-Play Distributed Systems Shared Information Environment Enable Global Reach Support Discovery of services in a global environment

12 Local Area Network PL PL 12 Scaleable, Network-Centric Approach Lookup Service Map Services Data Services Interface Services Database Normalized Data Map Server Component Level (Jini,JXTA,Bluetooth, IEEE 1394) Global Level (Web Services/J2EE, Portals, App Servers, Network ID) Element Level (Java/Jini/JXTA/XML/HTML)

13 13 Foundation for Web Services Publish, Find, Use Services: UDDI Formal Service Descriptions: WSDL Service Interactions: SOAP Universal Data Format: XML Ubiquitous Communications: Internet Simple, Open, Broad Industry Support

14 14 But are web services enough? Web Services fit well here Enterprise Architecture (10 Second Resolution) Some web services technologies can be applied here Not a good fit here System Architecture (Second Resolution) Platform Architecture (ms Resolution)

15 15 Limitations with web services Web Services are great for enterprise applications, but are of limited use in highperformance systems SOAP protocol is not sufficient for timecritical interfaces UDDI lacks notification mechanisms when services fail XML processing adds significant overhead to network and processing

16 16 Network Services for System and Component Architectures

17 17 Net-Centric System Design Network Centric design needs to move beyond sharing data in the enterprise and be applied to how we architect our systems from the ground up

18 18 An Example: Typical interface implementation Provider Consumer GUI GUI App SW Driver Driver App SW Must have agreement on Protocol, message sets, data elements & physical interface Typical interface issues 1. Consumer must create a custom driver that implements the protocol and processes the agreed-upon datasets 2. Consumer must define the private software interface to provide information to application software 3. Must implement software to establish and manage the connection (requires foreknowledge of parameters) 4. Requires significant interface testing 5. Typically must implement a new driver to handle any additional providers or consumers Private SW Interface

19 19 Service implementation Provider Consumer GUI GUI App SW Driver Private Protocol Driver App SW Service-based approach 1. Software driver (proxy) is provided by the service provider 2. Underlying message set/protocol is hidden from the consumer system 3. Connection parameters are also hidden from the consumer proxy knows how to connect to provider 4. Consumer can get service from anyone implementing the service interface Must have agreement on Service discovery mechanism & software interface Agreed upon Service interface

20 20 Application Services Provider Consumer GUI GUI App SW Driver Private Protocol Driver App SW Service-based approach 1. Entire Software application is provided by the service provider 2. Underlying message set/protocol is hidden from the consumer system 3. Connection parameters are also hidden from the consumer Application knows how to connect to provider 4. Consumer can get service from anyone implementing the service interface

21 21 Ad-hoc Component Integration Lookup Service Map Services Data Services Interface Services PL PL Local Area Network Database Map Server Normalized Data

22 22 Goal: Plug-n-Play Systems Design Interface software packaged with the Hardware Hardware can be added with no software modifications

23 Distributed System Services COTS/GOTS Visualization Package Visualization Service Framework CGS MTI UAV Mobile Graphical Components AFATDS AFATDS Services Servicesprovide providenot notonly only the access to data, but the access to data, butthe the smarts for how to deal smarts for how to deal with withthe thedata data Targeting Interface Provided by AFATDS UAV Viewing App Provided by CGS 23

24 24 Interoperability Strategy C4ISR Applications Mission Planning Advanced User Interaction C2 Execution Automation / Decision Aides ISR Targeting Fusion Services ISR Services Service Abstraction Service Frameworks Discovery Framework Web/App Server Install Service Container Services Context Services Security Mgt Framework Framework Connector Framework Architecture Portability Protocol Plug-Ins Web Service Protocol Plug-Ins Real-time Protocol Plug-Ins Operating System & Platform JVM Operating System Platform Networks Networks ( internal and external ) A common common service service abstraction abstraction allows allows services services to to be be deployed deployed in in Enterprise, Enterprise, System System or or Platform Platform architectures architectures

25 Interoperability Strategy C2 ISR C4ISR Applications Mission Planning Advanced User Interaction Execution Automation / Decision Aides Targeting Fusion Services ISR Services Application Interoperability Freedom C4I Visualization Framework System Framework Alert Framework Collaboration Framework Agent Framework Simulation Framework Data Dissmeination (JBI) Database Framework Openwings Layer Discovery Framework Web Server (Tomcat) Install Service Container Services Context Services Security Mgt Framework Framework Connector Framework Architecture Portability Interoperability Packs Joint (NCES) Interop Pack Army (SOS COE) Interop Pack Airforce (C2ERA) Interop Pack Navy (NavyOA) Interop Pack Marine (MAGTFOC) Interop Pack Operating System & Platform JVM Operating System Platform (ISRIS Server) Networks Networks ( internal and external ) 25

26 26 Service Abstraction - Openwings What is Openwings? An open architecture forum established in 1999 by Sun Microsystems and General Dynamics Primary Goal Provide a standard infrastructure that is developed by industry for time-critical, distributed, networked systems Openwings Community 9 Expert teams, 100+ organizations, 350+ members Reference version freely available to all via the Openwings web site (

27 Openwings Architecture Model Openwings provides abstractions from platforms, discovery mechanisms and middleware technologies The Openwings framework also provides interfaces for security, management and installation services Jini UDDI JXTA Data Services Openwings Facilities Discovery Plug-ins Container Services Domain Model J2EE J2SE J2ME Network Component Component Component Component Services Connector Services RMI IIOP JMS SOAP Component Component Component Install Services Context Services Management Services Security Services 27

28 28 Summary Web Services provide a model for enterprise integration, but aren t sufficient for time-critical applications Network-Centric System Design needs to extend to how we architect systems from the ground up. There is a need for a single architecture framework that bridges both enterprise and component architectures Openwings provides a good foundation to build from

29 29 OPENWINGS

30 Questions? 30