The document discusses the application of Service-Oriented Architecture (SOA) for net-centric operations, emphasizing the benefits of open-source technology in developing scalable, strategic systems. It highlights the need for decentralized management, interoperability, and local expertise, particularly for defense applications, while advocating for the establishment of national SOA platforms and shared open-source resources. Ultimately, it positions free and open-source software as essential for building effective SOA solutions, enabling both innovation and strategic advantages.

1. Service Oriented Architecture for Net Centric Operations based on Open Source Technology Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO, WSO2 Founder, Director & Chief Scientist, Lanka Software Foundation Member, Apache Software Foundation Emeritus Board Member, Open Source Initiative Visiting Lecturer, Univ. of Moratuwa, Sri Lanka IONS Technical Seminar. May 21, 2009. Colombo, Sri Lanka.

2. About me IBM Research from 1997 to 2005 Co-authored most of the key Web services specifications WSDL, WS-Eventing, BPEL4WS, ... Contributor to Apache Web services Contributor to Apache SOAP, Apache Axis, Apache Axis2, Apache WSIF, Apache Neethi, Apache Axiom, ... Member of Apache Software Foundation

3. Founder & Chief Scientist, Lanka Software Foundation

4. (Emeritus) Board Member of Open Source Initiative

5. Founder, Chairman & CEO of WSO2 Open source SOA platform company

6. Agenda SOA & its implications

7. Open source and its implications

8. Open standards

9. Interoperability framework for net centric operations

10. US DoD SOA activities

11. Open source SOA for defence applications

12. Summary

13. What is SOA? An approach for building large scale systems where functionality is bundled as interoperable “services” Details of how the service is implemented are not important

14. Consumer operates against a service contract that defines the business interface and qualities of service Services interact with each other by sending messages in an interoperable standard

15. Service metadata is often registered for easy discovery and governance

16. SOA?

17. Typical business SOA picture

18. SOA in Sri Lanka government: LankaGate Other Applications Services Providers Open Standards SOA Architecture Enabling Web 2.0 Concepts Mobile Payment Gateway Other portlets Lanka Interoperability Exchange Citizens Businesses Visitors Government Multiple Access Channels (eg. Web, Mobile, Email, etc.) Identity Mgt. CMS portlet GIC portlet e-Gov Service 1 portlet e-Gov Service m portlet Services Directory Service 1 (eg. e-RL) Service n

19. Advantages of SOA Localized management of information and data (Think of object orientation taken to the next level) Decentralized deployment Owner of information runs the service that exposes the data 100% securable Complete security platform available Total focus on interoperability While maintaining proper authentication & authorization Open-ended, decentralized customization and localization Scalable for a single country or a coalition

20. Open source Open source fundamentally about source code being available Under license terms that allow you to improve & redistribute Collaborative development paradigm Enabled by the Internet Does not necessarily mean free of charge Support often costs money “Free software” vs. “open source software” Free & open source software (FOSS)

21. Advantages of FOSS Freedom to innovate

22. Try before you buy

23. Lower cost of entry

24. Better security

25. FOSS software? Anything !

26. Everything from server/desktop/embedded system operating systems to all middleware to desktop apps to enterprise apps

27. Very often FOSS builds on other FOSS Standing on the shoulders of giants

28. Culture of easy license-compatible dependency taking EVERY software vendor now has FOSS in some form, inside or shipping No longer a niche concept

29. FOSS & SOA “You can't buy SOA, you have to build it”

30. Closed-source SOA products are complex, non-agile and expensive

31. Deployment of SOA always requires a lot of customization

32. Especially in military context, does not provide the framework for the military organization to take control of the software Build local skill and knowledge and reduce external dependency Opportunity to “fork”

33. Open standards Standards are critical for interoperability

34. Open standard means has wide adoption and support

35. Critical for long term data protection

36. Critical for interoperability between friendly nations

37. Interoperability framework vs. architecture framework for net centric operations Traditional thinking on building large scale systems is to have an architecture framework

38. Does not provide sufficient room for innovation within local contexts “Local” can range from national level to different military branches to different parts of a single organization Key criteria is interoperability Documented data standards

39. Use of interoperable message protocols and standards

40. Use of interoperable security protocols and standards Opportunity to share code across units, branches, nations

41. SOA in an SOA (in an SOA ...) MoD MoD Common Services Navy

42. Security in SOA SOA technology platform provides complete security story Message level security

43. Scalable authentication

44. Fine grained authorization

45. Audit / Non-repudiation Even enemies can share the same technology platform and use policy driven security to ensure proper access and protection

46. End-to-end security is now possible

47. US DoD SOA activities DoD Net Centric Enterprise Services (NCES) Common services for the DoD

48. SOA platform SOA Symposium in Washington, DC in March 500+ attendees from all branches of military – CIOs, senior IT officers

49. Focused on education of SOA concepts Very large complex problem for US DoD 3.5m people in organization

50. Incredible amount of legacy to deal with

51. Complex procurement processes that are inherently designed around enterprise systems (Which have repeatedly proven to not deliver on time or on budget!)

52. Forge.mil US DoD effort to start an “open source” community around their requirements (initiated in 2009)

53. Sharing code, data standards, protocols, documents: Enable cross-program sharing of software, system components, and services

54. Promote early and continuous collaboration among all stakeholder (e.g., developers, material providers, testers, operators, and users) throughout the development life-cycle

55. Rapidly deliver effective and efficient development and test capabilities for DoD technology development efforts

56. Help protect the operational environment from potentially harmful systems and services

57. Encourage modularity so that large programs to be developed, fielded, and operated as a set of independent components that can evolve and mature at their own rates

58. Eliminate duplicative testing and improve dependability by adopting common test and evaluation criteria supported by standard testing tools and methods SoftwareForge now operational Meant for US military use primarily

59. FOSS for defence Software is underpinning everything – from weapons systems to vessels to operational aspects

60. Depending on external software technology providers only is a huge national security risk Exposes one to external threats FOSS allows one to not only consume, but also PRODUCE software assets Which can become currency in global relationship management On a grander national scale, help develop local IT expertise and industry E.g.: US DoD has been catalyst for much innovation

61. Opportunity to leapfrog!

62. Recommendations Each country DoD needs to set up their own SOA platform Using FOSS products to give maximum flexibility Each country needs to set up its own equivalent of Forge.mil

63. Set up shared registry of data standards E.g.: Definitions of various types of vessels and their characteristics

64. (Not mandatory to use, but enable serendipitous reuse when possible) Set up shared data centers using (FOSS) cloud computing technology for use within branches of the military as well as across

65. Make military software technology a strategic weapon for the country & allies

66. Summary Service Oriented Architectures (SOA) is now the accepted approach for building very large scale systems that actually work

67. SOA enables scalable, strategic sharing of information in net centric operations

68. Free & Open Source Software (FOSS) provides a superb platform for building SOA solutions

69. FOSS provides intrinsic strategic advantages to the country

70. It can be done – local expertise is already there in every country Look for it, enable it, sponsor it, nurture it