Date post: | 03-Jan-2016 |
Category: |
Documents |
Upload: | chester-gaines |
View: | 222 times |
Download: | 2 times |
ebXML: Status and Evolution, Role in SOA
Jacques Durand (Fujitsu Software)Hamid BenMalek (Fujitsu Software)
ebXML developed by
• United Nations Center for Trade Facilitation and Electronic Business
• Developers of EDIFACT• One of four organizations in the
world that can set de jure standards
• World’s largest independent, non-profit organization dedicated to the standardization of XML applications
• More than 400 members in 26 countries
ISO standard
- ebXML Standards also published as ISO 15000 Standard parts 1-5
- Part of the MOU on e-trading/commerce between ISO/ITU/IEC/UN/ECE
ebXML Functional Areas and Releases• Messaging: ebMS
– SOAP extension, +attachments. ebMS 2.0 -> ebMS 3.0 (end 2005)
• Data Integration: CCTS – Core Components 2.1 (basis for UBL, CAM, OAGIS)
• Business Collaboration: ebBP – Business Process Specification Schema BPSS 1.x -> ebBP
2.0.1 • Registry Repository: ebRS and ebRIM
– Registry 3.0 Services and Protocol– Registry 3.0 Information Model
• Collaboration Agreements: ebCPPA – Collab. Protocole Profile (CPP) and Agreement (CPA)– CPPA 2.0 -> CPPA 2.1
ebXML new version(s): trends
• Adjusting to Evolving Environments– Standards (WServices, UMM, Vertical)– Business (SMBs with diverse connectivity styles)– Architecture (SOA, ESB, eB Gateways)
• Open architecture – ebXML is more a Framework than an Architecture– Components complement each other (bindings), but can
operate independently– Better support for integration alternatives– Effort under way that integrates SOA concepts
ebXML Scenario
Supplier ebXML
Registry
Define or Choose a Transaction Model for Purchase Order (ebBP)
12
34
Register :• P.O. transaction def (ebBP)• Collaboration Profile of Supplier (CPP)
Client
Download:• Profile Supplier (CPP) • transaction def (ebBP) Agreement on
a CPA 5Execute Transaction(ebMS)
ebXML Messaging Services V3• Better Support for Business Use-Cases
– Handle restricted and intermittent connectivity (SMB)– Status inquiries and Monitoring Support– Support Message Exchange Patterns (match Business
Transactions)
• On the wire, just another SOAP extension– Delegate basic protocol functions to WS standards (WS-
Security, WS-Addressing, WS-Rel*)– Message Service Handler (MSH) as an aggregation of
SOAP nodes.– But no dependency on WSDL (Because not every
message is a service invocation)
ebBP (Business Process): Definition, Monitoring and Validation of Collaborations
Client Supplier
Purchase Order Request
Acceptance/ Exception
Business Transaction
1002Purchase Order Reception
1003Create Approval Task for
Supervisor
1004Respond with Approval/Rejection
Response
1005Process Response
1000Assess Inventory Status
1006Notify Department X
1007Update Production Planning Record
1001Generate Replenishment Order
1005Receive Response
[Acceptance] [Rejection]
Collaborationcontract
ebXML Business Process V2.0.1• Focus on public exchanges:
– Performance/ timing parameters, general exceptions– Binding to advanced definition of partner roles (security
reqrt., QoS, etc.) in CPA
• Built-in support for standard Business Transaction definitions:– 6 patterns defined by UN/CEFACT UMM Rev 10.– Allows user-defined patterns to be specified.
• Bridges to WSDL-defined operations and MEPs:– For hybrid collaborations involving WS plus other
protocols.
ebXML CPP/A V2.1• Partner Capabilities and Preferences (CPP)
– Protocol features and QoS– Specific Roles in collaborations, and associated properties– Publish, and Compose (partners’CPPs CPA instance)
• Agreements (CPA)– Configure run-time environments
• Version 2.1– + Errata 2.0 , but backward compatibility (schema)– Extension framework
Alternative messaging (EDIINT, AS2…), business process (ebBP 2) and document exchanges (WSDL)
• Management of Enterprise content and meta-data:– Lifecycle, validation, conformance to user-defined
standards, versioning, queries, auditing– Advanced support for XML (search and querying) – Content-based events / notifications
• Registry Profiles: define restrictions and extensions of Usage for Particular Domains– Web Services Profile– WSRP (Remote Portlets) Profile– Others: HL7, IHE XDR, Open GIS…
ebXML Registry Services 3.0
A Functional View of SOA
• Messaging and Connectivity– Protocols, security, QoS, exchange patterns
• Data Integration – XML Vocabularies, conversion, validation, documents
• Orchestration – BPM, transactions, coordination
• Registry / Repository– Meta-data, artifacts, definitions, policies, governance
Where does ebXML fit in
• As an eBusiness Enabler for SOA:– Partners Agreements (CPP/A)– Monitoring of Customized Collaborations– Robust Messaging, for loose coupling
• As an SOA Management and Governance Service:– Registry / Repository
A Functional View of SOA
• Messaging and Connectivity– Protocols, security, QoS, exchange patterns
• Data Integration – XML Vocabularies, conversion, validation, documents
• Orchestration – BPM, transactions, collaborations
• Registry / Repository– Meta-data, artifacts, definitions, policies, governance
B2B Connectivity Patterns for SOA (1)
Appcode
Web Server
SOAP
Service Invocation Everywhere
WebServicesstack
WebService
WebService
invoke ERPWebService
SCMWebService
WebService
ERP
Integration Broker
B2Bgateway
adapter
WebService
BPM
ebMS
Other
B2B Connectivity Patterns for SOA (2)
•Queuing•Data Map
SOAP
“Accidental architecture” and Heterogeneous Integration
WebService
SCM
J2EE application
ERP
SCM
BPEL
WebService
B2Bgateway
ebMS
Other
SOAP
JMSJCA
.NET applicationSOAP,C#/CLR
B2B Connectivity Patterns for SOA (3)Enterprise Service Bus - mediated
ESB WebService
CRM
WebService
A Functional View of SOA
• Messaging and Connectivity– Protocols, security, QoS, exchange patterns
• Data Integration – XML Vocabularies, conversion, validation, documents
• Orchestration – BPM, transactions, collaborations
• Registry / Repository– Meta-data, artifacts, definitions, policies, governance
ebXML ebBP and SOA
• Monitoring of Collaboration Contracts (B2B)– Regardless of their implementation (Web service
invocations, or just message exchanges.)
• Partner-specific Collaboration Contracts– Properties of collaborations (timing, performance, QoS)
not tied to transaction definitions, but may vary depending on partners involved (CPA). Collaboration pattern -> ebBP Collaboration properties -> CPA
ebBP instance
A Functional View of SOA
• Messaging and Connectivity– Protocols, security, QoS, exchange patterns
• Data Integration – XML Vocabularies, conversion, validation, documents
• Orchestration – BPM, transactions, collaborations
• Registry / Repository– Meta-data, artifacts, definitions, policies, governance
• SOA Governance– Lifecycle management and access control of Enterprise Web
services metadata and artifacts Approval, visibility, use, deprecation, and deletion based on maturity
level, user roles, organizational policies. (WSDLs, schemas, process def such as BPEL, ebBP, WSRP, XSLT) Accessible via SOAP binding (WSDL-defined)
• Registry Profile for Web Services– Deploy/publish and federated management of Web services
metadata and artifacts
ebXML Registry Service and SOA
ebXML Registry Services: SOA Governance
Control •Service visibility, •Access,•Classification, •Lifecyle stage,...
6
1
23
5
4
• Cross-partner integration relies on:– Common Content standards– Common Messaging Protocols– Common Transactions
• Or on managing the heterogeneity of the above !– Loose coupling of systems– Partners’ Profiles and Agreements– Data Integration and Adapters
ebXML, SOA and Supply Chains (1)
Island of consistency
Both a B2B and anIntegration Challenge
• Cross-partner integration relies on:– Common Content standards– Common Protocols– Common Transactions
• Or on managing the heterogeneity of the above !– Loose coupling of systems– Partners’ Profiles and Agreements– Data Integration and Adapters
ebXML, SOA and Supply Chains (2)
SOA: Integration focused•ESB•Standardize on Services•Loose coupling
ebXML:• Supports SOA Governance• Focus on the B2B Collaboration