Copyright OASIS, 2004 David RR Webber XML eBusiness USA ebXML Update Toward a SOA Paradigm Presentation, August 2004 NIST Gaithersburg Maryland

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,

Copyright OASIS, 2004 ebXML in a nutshell Globally developed standard for – Exchanging business messages – Conducting trading relationships – Defining and registering business processes – Communicating data in common terms – Assembling business transactions Using Internet as delivery vehicle

Copyright OASIS, 2004 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 Phase 1 completed May 2001 by 4500 participants representing 2000 organizations in 150 countries from all major continents

Copyright OASIS, 2004 ebXML Adoption 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

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

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

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

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

Copyright OASIS, 2004 Agenda ebXML Today – Why ebXML? (deployment Landscape) – Classic ebXML – Enhanced ebXML – ebXML component drill-down What’s next? - Front-office EPR (Electronic PRocess) work ebXML in the marketplace - vendor products ebXML projects Summary

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

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

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

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

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

Copyright OASIS, 2004 Business Goals 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 Obviously the optimum business solution is to purchase just the right amount of technology to solve the given business requirements.

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

Copyright OASIS, 2004 How the pieces fit together Classic ebXML

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

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

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

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

Copyright OASIS, 2004 ebXML CPA / CPP component Participant Information Messaging preferences and configuration Message exchange details

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

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

Copyright OASIS, 2004 Extending the core architecture Enhanced ebXML

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

Copyright OASIS, 2004 Multiparty Model with BPSS

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

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

Copyright OASIS, 2004 Enhanced ebXML

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

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

Copyright OASIS, 2004 Align BP steps to information systems DealerLocation Activity DealerLocator Map To PurchaseRequest Activity DealerLocator Map To VehicleHistory Activity DealerLocator AvailableVehicle Activity Map To PurchaseApproval Activity Map To [Business Error] e.g., Map DealerLocation Activity to the DealerLocator Web service Business Analysts map B2B Transactions to the services available in Back-end Service Oriented Architecture (SOA)

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" UIDReference="ukt000910" <conditional expression="'//SupplierID' and lookup(value,'SGIRWSDL:supp lierID_check')" Simple Declarative Statements BPSS Step transaction template

Copyright OASIS, 2004 Context is the pervasive driver to effective engineering Drives dynamic process configuring and control Ensures accurate information capture, packaging and delivery 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 : 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

Copyright OASIS, 2004 Aligning the Concepts – Core Components Create Long Term Contract Forecast Component Requirements Send Planning Document Place Order Ship Materials Customer Arrange Payment Supplier Domain: Matl Mgmt Industry: Auto Ship Notice Regulatory: Safety Change Lvl Container Serialized ID ProdId Part Number Ship’d Qty Context UBL - work on supply chain messaging using CCTS

Copyright OASIS, 2004 Generating a Context Instance 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

Copyright OASIS, 2004 Moving to deployment Business agreement Drives document exchanges

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

Copyright OASIS, 2004 ebXML example interchange integration ebXML MSH ebXML Proces s Server ebXML MSH Apps B2B— Tradin g Partne r CPABPSS Internet Services ebXML SOAP Business Process Collaboratio n DMZ Internal Firewall Internet DB Legac y Apps COTS Apps Legac y Apps Application Server(s) Orchestration Services Business App’ Services SOA Layer Business App’ Services

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

Copyright OASIS, 2004 Communication Protocol Envelope (HTTP, SMTP, etc.) SOAP Messages with Attachments MIME Envelope MIME Part SOAP-ENV:Envelope SOAP-ENV:Header eb:MessageHeader eb:TraceHeaderList Other:etc… SOAP-ENV:Body eb:Manifest eb:etc… Other:etc… Payload Message Package Header Container Payload Container(s) ebXML Header Information ebXML Message Service Handler control data ebXML Message Structure

Copyright OASIS, 2004 Interchange sequence detail A complete interchange consists of successfully: – passed authentication/access control – sent the bits to the other end – checked the packaging – checked the header structure – checked the header data – checked the signature on a header (*) – decrypted the payload (*) – verified the signature on a payload (*) – checked the structure of a payload (*) – passed the translated payload to a backend system/application for processing – Backend application successfully processed the payload – Receipt confirmation (*) Note: Items denoted (*) are optional

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

Copyright OASIS, 2004 ebXML Registry - XML document management XML Registry + Repository Life cycle management features Query management engine Security features includes digital signatures, user Ids Classification of any type of object 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

Copyright OASIS, 2004 Storing the Enterprise Artifacts Motivation Time People Specifications Schema Workflow Contract Directory Services Collaboration Partner Profiles - CPP Collaboration Partner Profiles - CPP 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

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

Copyright OASIS, 2004 Capturing Noun Semantics Draft layout for storing noun details in registry See: OASIS Registry Semantic Content Management sub-committee work (SCM SC) Can use Designer Tools to automatically generate from XSD model

Copyright OASIS, 2004 Automating Trading Partner Setup Example ebXML Server ERP POXML PO ERP XML Purchase Order ebXML Registry ebXML Service Layer Custom LOB Custom Invoice ERP System Accounting System ebXML Server ERP to Accounting PO Trading Partner Map Custom XML Invoice Schema & Map Exchange Profiles to quickly configure relationship

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

Copyright OASIS, 2004 Toward a complete end-to-end solution including services What’s next? Front-Office EPR work

Copyright OASIS, 2004 EPR Uses Workcards as a GUI Metaphor Participant and Context Based Architecture Participant can be: 1. Traditional User 2. Machine or Device acting as a Proxy for a User Environmental Context dynamically modifies Declarative Display Metaphor

Copyright OASIS, 2004 EPR Folder’s Core Components Object Models Organizing and Managing Tasks Service Portals SERVICE PART EPR Folder Container: Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Document card Handles all the Documents in the folder. WS linking Steering Card functions Workflow card Support to adm. working process in the business logic. (Often RuleControlled ProcessFlow) Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Dokumentkort Styrer tilgang til blankett- og dokumentmaler samt arkiverte Dokumenter. Job card (Service card) Def. of physical Instructions in a working process. Includes inspection and reports. Steering Cards: Arbeidsmappe ( Opprettes når ny bruker eller ny process ) Arbeidsmappe ( Opprettes når ny bruker eller ny process ) Working Folder Contain everything a user needs in work. All Working Folders are divided into phases Related to progress. Role Service + UserID phase Steering card Single Sign-On (PKI) portal: (Security Domains)

Copyright OASIS, 2004 Networked devices Workcards adapt to user environment

Copyright OASIS, 2004 Template Driven Application Infrastructure EPR – Electronic Processes Instead of using UML to craft solution model – the application infrastructure is provided already with task-centric focus - erpAPL Business rules, scripts, workcards and templates in XML are used to configure the solution environment to the target domain - eprXML erpAPL is modular – so a lightweight solution is possible – that can be extended to a full-featured deployment as needs grow Deployment in-front of legacy applications with transaction exchanges as interface

Copyright OASIS, 2004 Solution Architecture Templates - Capture Business Process Context details Reference – Domain Ontology and Semantic Information References Generate – XML artifacts that drive the implementation components Creates Technology – Implementation components Runs Processes – state management, linking and switching Integration – legacy system interactions Tracks Portal – user interface dynamically configured Enables

Copyright OASIS, 2004 eHealthcare eprApl eGovernment eprApl CAM processor Legacy systems General epr templates Public systems XML documents (content) Communication infrastructures eprXML engine eHealth epr templates eGov epr templates BCM switch/link Blue: ePROBE Yellow: others Web services + ebXML Integrating EPR applications together XML SOA - Process and Exchange rules

Copyright OASIS, 2004 Next Steps Work needed: – Formal Publication of OASIS Specification on EPR – Continue development of EPR application (eprAPL) – Library of EPR templates by industry – Integration with OASIS Registry semantics – Integration with BPSS and ebMS – Publishing of initial open source implementation

Copyright OASIS, 2004 Vendors Products ebXML in the marketplace

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

Copyright OASIS, 2004 Selection of Commercial and Government adoptions ebXML Projects

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

Copyright OASIS, 2004 Resources Summary

Copyright OASIS, 2004 Get involved in ebXML Download the specs from Open source resources News and Events Join OASIS Subscribe to ebXML-DEV mail list ebXML.org) Review public archives of OASIS ebXML TC work Encourage your industry group to adopt ebXML specifications for their standards Specify ebXML-compliance from providers

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

Copyright OASIS, 2004 Acknowledgements This presentation would not be possible without the unstinting efforts of the OASIS BCM team members, the OASIS BPSS team and support from the EPRforum members and the ebXML community. These slides are a culmination of materials from over a dozen presentations and sources representing many hundreds of hours of work. The momentum now building is exciting and we look forward to realizing the vision here to enable better societies through the exploitation of electronic network technologies.

Copyright OASIS,