Your SlideShare is downloading. ×
Federated Service-Oriented Architecture (SOA) for Effects ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Federated Service-Oriented Architecture (SOA) for Effects ...

836
views

Published on


0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
836
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
36
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Federated Service Oriented Architecture for Effects-Based Operations Intelligence and Information Systems Matt Brown (720) 858-4014 mebrown@raytheon.com Copyright © 2008 Raytheon Company. All rights reserved. Customer Success Is Our Mission is a trademark of Raytheon Company.
  • 2. Topics Effects-Based Operations (EBO) Service Oriented Architectures (SOA) Federated SOA Characteristics of a Federated SOA that enable EBO – Shared data and services across Communities of Interest – Simplified Integration of legacy capabilities – Leverages existing standards and standards implementations – Maintains interoperability of Vendor tools Conclusions Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 2
  • 3. AFDD-2 Principles of EBO Effects-based operations: – seek to integrate planning, execution, and Operations and assessment. – should focus upon the objectives and the end Organization state. – are about creating effects, not about platforms,weapons, or methods. – approach should consider all possible types of effects. – should seek to achieve objectives most effectively, then to the degree possible, most Air Force Doctrine Document 2 efficiently. 27 June 2006 – cut across all dimensions, disciplines, and levels of war. – focus on behavior, not just physical changes. – recognize that comprehensive knowledge of all actors and the operational environment are important to success, but come at a price. Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 3
  • 4. EBO Requires a Net-Centric Enterprise Traditional siloed systems do not support EBO well – Need capability to easily share large amounts of data across organizational boundaries – Timeliness of data and decisions is critical to EBO – Need access to modeling and sim, and other service like capabilities across the Enterprise – Limited visibility across the Enterprise – Efficient asset usage to gain data for EBO decision making Federated Service Oriented Architecture Provides a Net-Centric Infrastructure to Support EBO Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 4
  • 5. Service Oriented Architectures “Service oriented architecture is an IT strategy that organizes the discrete functions contained in enterprise applications into interoperable, standards-based services that can be combined and reused quickly to meet business needs.” – BEA SOA COTS – Multiple vendors provide each layer Vendor products often blur the layers Vendor standards compliance lacking Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 5
  • 6. SOA Topologies in a Net-centric Environment Global: one shared SR (Service Registry) Directly Connected: two+ completely synchronized SRs 1 2 3 4 1 5 2 3 4 5 1 2 3 4 5 Brokered: two+ SRs selectively Federated: three+ SRs selectively synchronized synchronized (including 1 master) Integration Broker 1 2 3 4 1 5 2 3 4 5 1 2 3 4 5 Integration Broker 1 2 3 4 1 2 3 4 5 5 Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 6
  • 7. Federated SOA Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 7
  • 8. Characteristics of a Federated SOA Infrastructure that enable EBO Shared data and services across Communities of Interest Simplified Integration of legacy capabilities Leverages existing standards and standards implementations Maintains interoperability of Vendor tools Federated Service Oriented Architecture Design Pattern is a Key Architectural Decision Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 8
  • 9. Federated SOA Test Bed Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 9
  • 10. Leveraging Core Services to Integrate Legacy Capabilities Mission Zone (Mobile) Enterprise Zone (Falls Church) ISR Zone (Landover & Falls SENTRY Zone (Fullerton) Church) Subscribe Client UDP UDP Publish Adaptation SENTRY Service MP Track Data Send Send http, REST Respond UDP Adaptation Service http, SOAP Enterprise Air Track TCP, LDAP LDAP Collector Invoke Response Invoke Mediation Transform Service MP Store Track SONIC ESB Respond Send Update JMS Mediation Transform Metadata Service Repository Enterprise C2 Service ISR Service Service Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 10
  • 11. SOA Standards WS-I Basic Profile Standards http://www.ws-i.org/Profiles/BasicProfile-2_0(WGD).html#references The WS-* set of standards is Orchestration Management & overwhelming. Some of the Security standards are not implemented. So, for real interoperability, it’s WS-BPEL XPDL safest to stick to the WS-I Basic Profile: Interface Definition & Discovery SOAP 1.2 MTOM RSS Atom XKMS HTTP 1.1 XML WS-Addressing 1.0 UDDI ebXML WSDL Schema SAML XML 1.0 WSDL 1.1 Mediation XACML XML Schema WS- XSLT XPATH XQUERY Addressing X.509 UDDI 2.0 TLS 1.0 / SSL 3.0 SOAP WS- X.509 v2/v3 Security Data Representation WS-Policy XML JSON LDAP MTOM MIME XML Signature Transport XML HTTP FTP Encryption SSL/TLS JMS Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 11
  • 12. Vendor Agnosticism is Key to Success Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 12
  • 13. Vendor Interoperability Lessons Learned Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 13
  • 14. Conclusions A Net-Centric environment is necessary to enable Effects-Based Operations. A Federated Service Oriented Architecture approach to providing federated interoperability, including federated modeling and simulation, can help achieve Effects-Based Operations. The federated governance design pattern that is used is a key architectural decision in the development process. – It is important to choose a design pattern that allows multiple vendor tools to be used across the enterprise while maintaining interoperability. Leveraging federated SOA and core service capabilities allows existing capabilities to be included in the Effects-Based Operations process. Understanding current standards and how vendors implement these standards is an important element in achieving success. Federated Service Oriented Architecture Enables EBO Copyright © 2008 Raytheon Company. All rights reserved. 4/21/2008 Page 14

×