1 / 26

Using OASIS standards for SOA development for eGovernment applications

Using OASIS standards for SOA development for eGovernment applications. SOA CoP Technology Briefing MITRE, McLean, VA May 2006 David RR Webber webberd@od.nih.gov. Unique eGovernment Challenges. Business Perspective – meeting goals / needs Community of Practice – fostering open adoption

ronni
Download Presentation

Using OASIS standards for SOA development for eGovernment applications

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. Using OASIS standards for SOA development for eGovernment applications SOA CoP Technology Briefing MITRE, McLean, VA May 2006 David RR Webber webberd@od.nih.gov

  2. Unique eGovernment Challenges • Business Perspective – meeting goals / needs • Community of Practice – fostering open adoption • Management – formal oversight and methods • Accessibility – open platform, open system • Security – certify participants, non-intrusively • Agility – flexibility of interfaces, content, rules • Performance – scalability, cost, re-use, maintenance

  3. eBusiness and eGovernment Overview of Architecture and Components Needs

  4. SOA Functional Components External Systems Network Security Content Transport Payload Handling Registry Business Systems Manage Workflow

  5. Staged Virus Check Certificates Identity Fire Wall MoUs Profiles Synch Partners Asynch Industry Semantics Errors Receive Validation Scripts Send Role + Context Scripts Business Rules Dispatch Business Rules Errors Content Events Actions Versions SOA Operational Details External Systems Network Security Content Transport Payload Handling Registry Business Systems Manage Workflow

  6. How can OASIS help? • It’s all a bit overwhelming!!! • Where to start? How to differentiate? • How can I go from business requirements to technology realization? • Divide the problem into layers! • Tackle each layer, and ensure interaction between layers is consistent with open interfaces with known roles and context • What can OASIS provide?

  7. Formalizing the Business Needs • Business-Centric Methodology • Business Process Specification • ebBP / BPSS V2.0.3 • External Processes • Internal Processes • BPEL • Internal machine level workflows / ERP integration • Technology Architecture – FERA / ebSOA • MoUs / CPAs • Transaction interchanges and content • Security – SSL, DSig, SAML

  8. Attaining SOA Through Component Layers Business Agreement Languages (RINs) Collaboration Profile Agreement (CPA) Choreography & Coordination Lang. (BPSS) Context Driven Information Exchanges (CAM) Semantic Registry

  9. Developers Developers Conventional models Analysis Analysis Specification Specification Design Design Test Test Maintenance Maintenance Coding Coding Installation Installation Use Use BusinessUsers BusinessUsers Procurement Procurement Requirements Requirements Needs Needs Interactive models Changing the ”Just write code” paradigm Adaptation, integration

  10. Operational Challenges • Need to formulize and manage partner agreements both inside and outside enterprise • Speed-up ability to integrate with partners by providing intuitive business-centric tools • Provide common point of reference for partners to ensure consistent operational practices • Facilitate re-use across enterprise by providing templates of proven solutions • Provide open standards-based approach that can be accessed by implementation systems

  11. 1. Memorandum of Understanding - MoU OASIS components Business Managers • Meeting of the Minds • Business Goals • Define Scope • Rough Timeline • Creation / Best Practice Wizard 3. On-line Registry Systems Administrators • Manage operational use • Provide automation access 2. Collaboration Protocol Agreements Operations Managers • Precise Choreography • Automated • Messaging Parameters • ebMS transport • WSDL web services

  12. Storing the Enterprise Artifacts Collaboration Partner Agreements- CPA Collaboration Partner Profiles - CPP 5 Contract BP Specification 4 Workflow Process XForms Specifications Schema 3 Content Assembly Mechanism - CAM Messages Artifact relationships 2 Motivation Time People Presentation Rules Events Roles Directory Services Data/Codes Services/Functions Network 1 MSH/SOAP Nouns Verbs Transport Routing, Packaging Core Components WSDL Source: BCM Lubash Pyramid

  13. Information Exchange Integration requirements • Outward facing messaging systems • Formal agreement profiles for business participants • Business process workflow definitions • Information exchange rules • Registry to hold agreements, definitions, scripts… • Internal integration routing and dispatch methods • User interfacing for entry and control

  14. SOA Exchange Design Goals • Automated registration of participants • Ability to self-certify exchange transactions • Version control and ability to approve partners • Centralized registry for participant management • Declared and shared business rule scripting • Integration through messaging services • Backend application integration services • Uses open public specifications and open source

  15. Commercial Examples Today Amazon.com & eBay.com

  16. Leveraging Open Standards • Combining best-of-breed solution with both ebXML and Web services working together • Expose synchronous and asynchronous interfacing to control content access • Open source solution components to allow unrestricted integration by partners • Foundation of ebXML formal interchange model • Leveraging loose coupling of web services • Industry best-practices and lessons learned (who has solved similar needs?)

  17. XML Technology Detail Some Components, Specifications and Implementation

  18. Linkage Between Messaging and CPA • Messaging envelope contains: • Sender name • Service / Action names • Sender CPA id value • Receiver CPA id value • Optional certificate • CPA validation contains: • CPA id lookup to registry • Verifies sender • Verifies valid Service / Action pairs for this partner • Coupling from Service / Action to transaction validation • Coupling from Service / Action to backend delivery • Verify certificate

  19. Role of the Registry for SOA Information Dissemination to all Participants / Stackholders • Trading partner management • Registration of trading partners with Agency • Authorization to do e-business with Agency • Authentication integrated with Backend Applications (single sign-on) • Simplified management of CPAs / SSL certificates • Self service management of providers capabilities & certifications • Metadata management • All XML schemas for transactions • All trading partner capabilities (including all of agency services) • Definition of data elements in each transaction • Instructions, documentation, and other • Version management of objects in registry

  20. Opportunity Summary Lessons learned; Technology Metrics

  21. Lessons Learned • Providing self-service facilities is key to rapid adoption • Infrastructure exists today off-the-shelf to create pre-built templates for industry domains • Using open specifications allows integration into wide range of environments • Open source solutions allows partners to readily obtain technology • Use of partner id concept to manage partners and versioning interchanges

  22. Technology Metrics • Create infrastructure that can support large communities via registry-managed control mechanisms • Provide simple integration for external partners by providing open source solutions as base-line • Supports commercial tools that implement ebXML and web services • Built-in methods that allow centralized control over rules, versions, and delivery routing • Reasonable security without being overly inhibiting to adoption • Complete integrated audit trail logging • Using existing specifications and toolsets • Proven technology with wide adoption and reference deployments

  23. Opportunities • Provide infrastructure for application across a broad cross section of related agency and departmental areas: • HHS - Cancer Research Centers • CDC – Emergency Alerting systems • Navy – Medical Services coordination • FEMA – Emergency supply chain delivery • DHS – Intra-agency information sharing • EPA – External regulatory reporting • NSF – National Science Foundation Grants

  24. Q & A Discussion • Nortel Government Solutions • For more information • Visit our Website: • http://www.nortelgov.com

  25. Project Resources • NIH eRA Project site – http://era.nih.gov • NIH Grants site - http://era.nih.gov/ElectronicReceipt/ • Commons online site – https://commons.era.nih.gov/commons/ • Grants.gov online site – http://www.grants.gov/GetStarted

  26. Technology Resources • www.oasis-open.org • www.ebxml.org • www.freebXML.orgwww.ebxmlforum.org

More Related