1. Copyright OASIS, 2004 David RR Webber david@drrw.net Dan Pattyn DanPattyn@austin.rr.com Presentation, November 2004 XML2004 Washington DC The New ebXML for SOA

2. Copyright OASIS, 2004 ebXML in the News "As ebXML becomes standardized, it will become the de facto way everyone does business." --Tony Scott, CTO, General Motors Interview in Information Week – March, 2004 http://www.informationweek.com/shared/printableArticle.jhtml?articleID=1 8201098

3. Copyright OASIS, 2004 ebXML in a nutshell n Globally developed standard (ISO15000) for: l Exchanging business messages l Conducting trading relationships l Defining and registering business processes l Communicating data in common terms l Assembling business transactions n Using Internet as delivery vehicle

4. Copyright OASIS, 2004 ebXML Adoption - 2004 Comparison of ebXML adoption by region, number / size / scope of projects as of December 22, 2003 China – 11,000 ebMS servers USA – DOD EMALL EU – Formal Adoption

5. Copyright OASIS, 2004 Backed by Industry Groups The Open Healthcare Group

6. Copyright OASIS, 2004 Interactive models Conventional models A New Approach to Software Engineering Analysis Specification Design Coding Test Maintenance Developers Adaptation, integration Installation Use Needs Requirements Procurement Business Users

7. Copyright OASIS, 2004 n Traditional Approach l ETL l EAI l UML l Data warehouse l B2B + electronic commerce n New Holistic Approach l Service Oriented Architecture l Business-centric models l Context driven environment l Semantic vocabularies and ontologies Leverage XML Paradigm Shift

8. Copyright OASIS, 2004 Value Co-Creation via Customer Centric Collaboration Extreme Mobility Infrastructure Occasionally Connected Application Wearable Computing Business Process Evolution Cross-Enterprise Service Centric Digitization Transaction Centric Digitization of Simple Task & Processes Process Re-Engineering Process Improvement

9. Copyright OASIS, 2004 Emerging Supporting Standards

10. Copyright OASIS, 2004 Agenda n ebXML Today l Why ebXML? (deployment landscape) l Classic ebXML l Enhanced ebXML for SOA l ebXML component drill-down n Summary l Review

11. Copyright OASIS, 2004 Deployment Landscape Today’s medium to large enterprises face a bewildering array of interchange format and mechanism choices Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness

12. Copyright OASIS, 2004 The CIO nightmare n What standards do I choose? n How do I build significant ROI for my organization? n Can I leverage my existing systems? n What resources are available to deploy my solution? n What are my partners doing? n How much of this is real? n How do I avoid being in a vendor revolving doors strategy? n How is open source important to my organization? n What if I just build it my way and ignore everyone else?

13. Copyright OASIS, 2004 Identifying the Needs n What are you trying to build anyway? n Better EDI system? n Reach SME partners more effectively? n e-Marketplace solution? n Next generation XML system and network? n Open e-Government systems? n Customer facing service solution? n Integration of major corporations applications? n Common industry collaboration and vocabularies?

14. Copyright OASIS, 2004 n People accept that a digital world is coming and are adjusting their work habits accordingly: l virtual presentations and meetings l all digital documents and transactions l digital photographs, voices, sounds, RFID, and signatures (online banking, iTunes, UPS, Radio Shack, Home Depot). n Digital artifacts shared factor – naturally multi- lingual. n Vast gulf between First World and Third World. The Challenge of Change

15. Copyright OASIS, 2004 Business Challenges n In determining operational needs there are four levels and areas to include: l The first level is the overall operational approach to solving large enterprise level interactions, l then enterprise to small business interactions, l small business to small business interactions l and service solution to customer. 1 2 3 4

16. Copyright OASIS, 2004 Business Goals n Since everyone’s business needs vary depending on their own circumstances, the focus here is on providing the means to understand the technology capabilities and then giving guidelines on how those relate to solving typical business needs n Obviously the optimum business solution is to purchase just the right amount of technology to solve the given business requirements.

17. Copyright OASIS, 2004 How do you put this all together? ActionEvent Information Rule What Why HowWhen Where / Who ActionEvent Information Rule What Why HowWhen ActionEvent Information Rule What Why HowWhen

18. Copyright OASIS, 2004 How the pieces fit together Classic ebXML

19. Copyright OASIS, 2004 Classic ebXML vision n Two trading partners collaborate together to create working relationship n Interchange defined as requestor / responder n Business transactions exchanged control the state of the process n Sharing of definitions and business understanding between partners within a community n Allows smaller companies to participate, not just large corporations

20. Copyright OASIS, 2004 ebXML components n Technical Architecture (TA1.04) n Message Services (ebMS – MHS) n Collaboration Protocol Agreements (CPA / CPP) n Business Process ( BPSS ) n Registry Services / (RegRep / RIM) n Core Components (CCTS / UBL)

21. Copyright OASIS, 2004 Initial Pieces – Defining the Interaction Bulk Buying Business Process Specifications (BPSS) Collaboration Agreement (CPA) Specifies Bulk Buying Business Process Check Product Availability Dealer Location Product Requirements Submit Purchase Order Schema definitions (XSD) + content processing templates Contains Business Transactions XML Messages Grammars Supplier > Dealer

22. Copyright OASIS, 2004 Classic Two-Role Business Process n Requestor / Responder interaction model

23. Copyright OASIS, 2004 ebXML CPA visual editing Participant Information Messaging preferences Message exchange details (DUNS Party ID Company Contact Web site Process Role Status Description) Process Linkage

24. Copyright OASIS, 2004 ebXML CPA / BPSS functions ebXML BP identifies Business processes including multi-party, multi- step exchanges Roles an organization must play Business transactions Messages being exchanged Context variables Business rules of edge conditions Transaction handling services Error handling ebXML CPA provides: Service name and parameters Endpoint for invocation Role of an organization in the context of a service Organization demographic information Failure scenarios Business process scenario and business transaction activity step Link to partner responsibilities Transaction Messages being exchanged Transport level QOS parameters Certificate and Encryption configuration Business status of agreement

25. Copyright OASIS, 2004 ebXML Solution Architecture Capture Process Details with Participant Roles / Context and Message Exchanging Definitions Reference – Domain Ontology and Semantic Information Reference - Domain Transactions + Business Process Models References Business Agreement Templates 11 Messaging System Drives Messaging System Partner A Partner B Exchanges 22 Enveloping + Routing Transactions + Validation Handles Queue Integration Agent Controlled by 33 Processes – state management, linking and switching Integration – application system interactions Manages44 BPSS + Workflow – Models of Interaction Service / Actions CAM XML templates – Business Exchange Formats and Rules CPA – Exchange Agreements Produces

26. Copyright OASIS, 2004 Classic ebXML example Each partner has ebMS exchange system BPSS implicit from exchange flow

27. Copyright OASIS, 2004 Classic ebXML example + Registry Registry provides common reference point BPSS implicit from exchange flow

28. Copyright OASIS, 2004 Extending the core architecture Enhanced ebXML

29. Copyright OASIS, 2004 SOA - Business Needs n Ability to manage a large community of participants in an e-Service and e-Business system n Manage central resources to allow partners to quickly join the community and integrate their own applications into the e-Service network n Partners can select the business process they want to use, pick the version(s) of transactions they can support, create their CPA configuration(s), test compliance, certify their ebMS systems and begin interacting

30. Copyright OASIS, 2004 Enhancing ebXML - Multiparty n Need to handle complex flows beyond two-party configurations n Today’s internet world is rarely simple n Partners perform multiple roles and interact with and provide range of services n Knowing context is vital

31. Copyright OASIS, 2004 BPSS key to eBusiness SOA n SOA l provides technology foundation and open interchange model and specifications n BPSS l formalizes this with business process control l captures the business exchange details l provides business agreement model for participants l provides facilitation for components in the SOA l XML template script sharable across an industry domain l context driven enables localization of standard models

32. Copyright OASIS, 2004 Multiparty Model with BPSS V2

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

34. Copyright OASIS, 2004 ebXML components work today n Technical Architecture (ebSOA) n Message Services / Web Services (ebMS – MHS) n Collaboration Protocol Agreements (CPA / WSDL) n Business Process ( BPSS ) n Federated Registry Services / Semantic Content (RegRep / RIM / SCM – OWL) n Core Components (CCTS / UBL) n Content Assembly Mechanism (CAM) n Context Management / State Management (new)

35. Copyright OASIS, 2004 Enhanced ebXML – BPSS and context driven

36. Copyright OASIS, 2004 Modelling the Business Process n from the model – generates actual BPSS as XML instructions

37. Copyright OASIS, 2004 Deterministic linking of BPM to layers n Each step consists of deterministic action and outcomes Select associated responding document Group Possible Responses Configure outcomes and flow control Transport layer return settings

38. Copyright OASIS, 2004 Content Assembly Template Configure the Business Exchange Rules XML instance structure(s) Business context rules + Content Reference rules + Data Validation rules + External Mapping rules Logical business transaction can have more than one structure layout can add inline rules directly into structure makeOptional() excludeTree() item type="noun" name="Agency/@AgencyID" UIDReference="ukt000910" <conditional expression="'//SupplierID' and lookup(value,'SGIRWSDL:supp lierID_check')" Simple Declarative Statements BPSS Step transaction template

39. Copyright OASIS, 2004 n Context is the pervasive driver to effective engineering n Drives dynamic process configuring and control n Ensures accurate information capture, packaging and delivery n Key to correct relationships between partners in a collaboration Lack of context control mechanisms is the most prominent reason why legacy e-Business systems are difficult and complex to extend and support Date: circa 1568 1 : the parts of a discourse that surround a word or passage and can throw light on its meaning 2 : the interrelated conditions in which something exists or occurs Understanding about Context

40. Copyright OASIS, 2004 Generating a Context Instance n Add parameter value rules and document value rules Check a document and change a BPSS parameter Create a rule and set a value Configure Context Instance header

41. Copyright OASIS, 2004 Moving to deployment Business agreement Drives document exchanges Participant Profiles Domain Semantics Information Purposing Information Exchange

42. Copyright OASIS, 2004 Example – Collaboration SOA Industry Partners XML Structure Rules XML Structure Rules Transport ebMS server Transport ebMS server Oracle database Oracle database Central ebXML Registry Central ebXML Registry CPA check CPA check CAM data validator CAM data validator Partner Management Web forms Partner Management Web forms (Persistent Storage) CPA instances CPA instances CPA instances CPA instances System Administrators Manage Partner Interactions Applicant Company Applicant Institution Proxy Submission Service Provider Messages 22 11 33 44 55 e-Service authority system Messages

43. Copyright OASIS, 2004 Some extended details on each piece ebXML component drilldown

44. Copyright OASIS, 2004 Messaging Layers Coupling Tighte r Looser Security Limited Extensive ebXML Web Services for XML Message Web Services for RPC Reusable Components SOAP/HTTP (JAX-M for ebXML) ebXML WS SOAP/HTTP (JAX-RPC) ORB (RMI/IIOP) WS SOAP/HTTP (JAX-M for WS-Routing) Typical access via: Granularity Small A2A Integrated Apps Homogeneou s Application WS Big A2A Integrated App Families B2B Market, Global Multi-enterprise ebXML Application Arena Message Services

45. Copyright OASIS, 2004 WSDL and ebXML CPA / BPSS WSDL provides: Service name Service parameters Endpoint for invocation ebXML CPA provides: Service name and parameters Endpoint for invocation Role of an organization in the context of a service Failure scenarios WSDL identifies: Business processes ebXML BP identifies Business processes Roles an organization must play Messages being exchanged Error handling article comparing messaging technologiestechnologies at ebXMLForum

46. Copyright OASIS, 2004 Registry Roles “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”. Business Analyst Web Interface Information Profiles Distribution Administration Program Level Semantics Information Engine Industry Business Standards Registry Protocol Standards ebXML, ISO11179, OASIS, OAGi, RosettaNet, UBL, UDEF XML Software Developers Interchange

47. Copyright OASIS, 2004 ebXML Registry - XML document management n XML Registry + Repository n Life cycle management features n Query management engine n Security features includes digital signatures, user Ids n Classification of any type of object n Federation of Content Registry Interface Life Cycle Manager Query Manager Security Manager Persistence Manager Authentication Authorization Soap Repository Database with RIM Registry Objects Organization Extrinsic Objects BPSS, CPA, CC http://registry.oasis-open.org

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

49. Copyright OASIS, 2004 Capturing Noun Semantics

50. Copyright OASIS, 2004 Review SummarySummary

51. Copyright OASIS, 2004 Summary n Enhanced ebXML allows business users to logically decompose the problem and express it coherently and reliably n Templates capture the business scenarios and rules n Templates derived to ebXML artifacts – CPA, BPSS, CAM, WSDL, plus context parameters as needed n Deployment environment driven by software templates n Industry groups create catalogues of re-usable solutions and networks of collaborating systems

52. Copyright OASIS, 2004 Vendors Products n Full list available from http://ebxml.org/implementations http://ebxml.org/implementations n 12 vendors certified for interoperable ebMS solutions n Implementations from: Oracle, Adobe, Sun, Fujitsu, Sybase, BCEmergis, BEA, Cyclone Commerce, Sterling Commerce, bTrade, webMethods, TIE Commerce, Smartdraw.com and more n Open source solutions – http://freebXML.com for messaging and registryhttp://freebXML.com

53. Copyright OASIS, 2004 Selected ebXML Projects n Automotive Industry moving to adopt ebXML - Feb 2004 Automotive Industry moving to adopt ebXML - Feb 2004 n ebXML underpins new Korean Bank and Insurance services - Feb 2004 ebXML underpins new Korean Bank and Insurance services - Feb 2004 n US Gov DOD EMall Embraces ebXML Messaging - Jan 2004 US Gov DOD EMall Embraces ebXML Messaging - Jan 2004 n US Center for Disease Control (CDC) ebXML implementation - October, 2003 US Center for Disease Control (CDC) ebXML implementation - October, 2003 n e-Invoice system for major Metro operator - September, 2003 e-Invoice system for major Metro operator - September, 2003 n ebXML Asia interoperability testing - August, 2003 ebXML Asia interoperability testing - August, 2003 n Bangkok, Thailand Project - SMEs & Nectec - August, 2003 Bangkok, Thailand Project - SMEs & Nectec - August, 2003 n ebXML and Energy Utilities Market- July, 2003 ebXML and Energy Utilities Market- July, 2003

54. Copyright OASIS, 2004 Finding ebXML Resources n Download the specs from www.ebxml.orgwww.ebxml.org n Open source resources www.freebxml.comwww.freebxml.com n News and Events www.ebxmlForum.comwww.ebxmlForum.com n Join OASIS n Subscribe to ebXML-DEV mail list (link @ ebXML.org) n Review public archives of OASIS ebXML TC work n Encourage your industry group to adopt ebXML specifications for their standards n Specify ebXML-compliance from providers

55. Copyright OASIS, 2004 Books on ebXML n Kotok and Webber, ebXML: the New Global Standard, New Riders, Aug 2001, http://www.ebxmlbook.com/ n Nickull, et al., Professional ebXML Foundations, Wrox Press, Nov. 2001 n Chiu, ebXML Simplified, John Wiley & Sons, June 2002 n Gibb and Damodaran, ebXML Concepts and Application, John Wiley & Sons, Nov. 2002

56. Copyright OASIS, 2004 www.ebxml.org www.oasis-open.org