Copyright OASIS, 2005 / 2006 Standards and Open Source Standards and Open Source Tools for Implementing Tools for Implementing Loosely Coupled SOA Loosely Coupled SOA XML, metadata techniques and micro-services tools SOA CoP MITRE, MacLean, VA October 2006 David RR Webber, Chair OASIS CAM TC [email protected]http://drrw.net
29
Embed
Copyright OASIS, 2005 / 2006 Standards and Open Source Tools for Implementing Loosely Coupled SOA XML, metadata techniques and micro-services tools SOA.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Copyright OASIS, 2005 / 2006
Standards and Open Source Standards and Open Source Tools for Implementing Loosely Tools for Implementing Loosely Coupled SOACoupled SOAXML, metadata techniques and micro-services tools
formal definition of loose coupling actually is, why it is beneficial and if indeed solution providers are actually delivering on the original vision?
Worse many implementations and approaches appear to be delivering tight-coupling with XML as constricting as the original issues of EDI and CORBA based systems!
Government is looking for information agility and metadata based information integration in the context of SOA today, so how can this be achieved?
Copyright OASIS, 2005 / 2006
Interactivemodels
Conventionalmodels
Changing the "Just write code" paradigm
AnalysisSpecification
Design
Coding
Test
Maintenance
Developers
Adaptation, integrationInstallation
Use
Needs
Requirements
ProcurementBusinessUsers
Installation
Use
Needs
Requirements
ProcurementBusinessUsers
AnalysisSpecification
Design
Coding
Test
Maintenance
Developers
Copyright OASIS, 2005 / 2006
Standards based work today OMG – UML / XMI model-based JSR - DROOLS JSR – API for Rule Engines ISO Common Logic OCL OASIS CAM, Registry, BCM CEFACT WGs – UCM, CCTS, UMP
Copyright OASIS, 2005 / 2006
What about “Architecture”?
Many Architecture models out there FERA - Federated Enterprise Registry Arch’ Simple service registry model Architecture “blue-print” templates Business-Centric Methodology (BCM) OMG – model driven architecture W3C – web content / document architecture Alignment of mechanisms around XML-
scripting techniques
Copyright OASIS, 2005 / 2006
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 (micro-services) Provide open standards-based approach that can
be accessed by implementation systems Ability to support remote ad hoc connections
Copyright OASIS, 2005 / 2006
External
Systems
Registry
SOA Operational Details
Network
Content
Transport
Security
ManageBusiness
Systems
Workflow
Payload
Handling
ContentVersions
MoUs
Business
Rules
Certificates
Identity
Role +
Context
Profiles
Industry
Semantics
Partners
Events Actions
Errors
Scripts
Scripts
Staged
Synch
Asynch
Fire
Wall
Virus
Check
Receive
Send
Dispatch
Errors
Validation
Business
Rules
Copyright OASIS, 2005 / 2006
Unravelling the Gorgonian Knot? 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
• Manage operational use• Provide automation access
Copyright OASIS, 2005 / 2006
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
Structure validation Context driven versioning and includes XPath DOM
Rule-based services: 30+ built-in functions Integration with rule engines (e.g. DROOLS) Call-out to Java methods
Data persistence / transformation services: SQL xslt
Copyright OASIS, 2005 / 2006
Use Case AnalysisUse Case Analysis
What a typical CAM deployment looks like
Copyright OASIS, 2005 / 2006
Business Functionality
Creating reliable domain solution templates for Communities of Interest (CoI)
Providing rapid deployment and simple change support Handling local context drivers and flexibility Linking business process, partner collaborations and
transaction exchanges into legally verifiable and deterministic solutions
Opening up business integration rules so that partners can confirm their usage
Validating and processing content with open public specification and rules base
Copyright OASIS, 2005 / 2006
Versioning Challenges
If the schema version changes – how to ensure it does not break our in place validations?
How to rapidly adapt to rule changes in a production environment?
How to develop user context driven deep version control and re-use of sub-components?
Enhance and automate Test release cycle by improving transparency for bug fix process and expose change deltas to speed testing process?
Copyright OASIS, 2005 / 2006
Grants Application Example
XML content
XSD schemafrom Grants.gov
2
DynamicStructure rules
Structure sub-form componentswith includes allows re-use
Context XML and context driven assembly BIE, ACC, CCs and CAM structure components Referencing Registry dictionaries - business nouns W3C RIF / OMG PRR / OWL / DROOLS semantic rules Eclipse support via CAM open source editor XSD auto-mapping support
Copyright OASIS, 2005 / 2006
www.jcam.org.uk
camprocessor.sourceforge.net
www.drools.org
www.oasis-open.org/committees/cam
Resources:
Copyright OASIS, 2005 / 2006
A special mention for our contributors to the CAM and jCAM work:
UK – Martin Roberts with BTplcUSA – Sidhartha Nagolu with AC-Tech / NIH