eb XML Architecture Anne Thomas Manes Sun Microsystems
eb. XML Architecture Anne Thomas Manes Sun Microsystems atm@sun. com O’Reilly Conference on Java, March 29, 2001
Disclaimer The eb. XML specifications are not complete. The details articulated in this presentation are subject to change. The final specifications will be compete in May 2001.
Agenda • • • What is eb. XML? Architecture Overview Architecture Details SOAP and UDDI Roadmap How to get involved
What is eb. XML • eb. XML = Electronic Business XML • Global Standard for electronic business • eb. XML enables anyone, anywhere to do business with anyone else over the Internet • Specifically designed to support SME • Complementary to existing B 2 B initiatives (UDDI, Rosetta. Net, Trade. Xchange, etc. ) An end-to-end B 2 B XML Framework
Sponsored by … UN/CEFACT (United Nations Center For Trade Facilitation And Electronic Business) (Organization for the Advancement of Structured Information Standards) Hundreds of participants from all over the world Businesses, governments, academia, institutions
eb. XML Vision • A global electronic market place where enterprises of any size, anywhere can: – Find each other electronically – And conduct business • Using XML messages • According to standard business process sequences • With clear business semantics • According to standard or mutually agreed trading partner protocol agreements • Using off the shelf purchased business applications
B 2 B Collaboration • B 2 B collaboration requires more than just an XML protocol and a service registry • You have to deal with – – – Business semantics Negotiating terms and conditions Interoperability Security and Privacy Reliability • eb. XML provides concrete specifications to enable dynamic B 2 B collaborations
B 2 B Collaboration Process Definition Process Evolution Process Management Partner Discovery Electronic Business Collaboration Process Execution Electronic Plug-in Partner Sign-Up
eb. XML Specifications Business Process, Core Components Process Reengineering Registry/ Repository Process Definition Partner Discovery Process Evolution Process Management Business Process Management Electronic Business Collaboration Process Execution Message Service, Business Service Interface Collaboration Protocol Profile Partner Sign-Up Electronic Plug-in Collaboration Protocol Agreement Business Service Interface
eb. XML Architecture Runtime Design Time Business Process Register & Discover Collaboration Protocol Profile Business Service Interface Business Documents Registries/ Repositories CP Agreement Transport Core/Industry Components XML based: XMI, Specification Schema, Document Schemas Collaboration Protocol Profile Business Service Interface Package Business Services/App’s
Usage Example 1 Request eb. XML specifications 2 eb. XML specifications detail Register scenarios and implementation details Register company business profile 4 eb. XML BO Library eb. XML BP Model 12 DO BUSINESS! Confirm profile and scenarios accepted 3 Specifications Build local system implementation y. X Accept CPA 9 8 Submit CPA 5 y uer ut abo 6 Q y pan Com an mp Co X 10 om st C eb. XML BO Library eb. XML BP Model ’s X any p Com ’s y. X rio na Sce rio ena Sc pan e u Req file ro ’s P Profiles 7 11 Scenarios INDUSTRY INPUT
Company Profile • Collaboration Protocol Profile – Defined using eb. XML Specification Schema – Concrete specification of your ebusiness offerings • Business scenarios you support • Service interfaces you implement • Document formats exchanged • Technical requirements/options (protocols, security, reliability) • Composed of – Business process models – Information models – Context rules
Business Scenarios • Often defined by Industry Groups – Standard business scenarios remove the need for prior agreements among trading partners • Business Process Model – Interactions between parties – Sequencing of interactions – Documents exchanged in each interaction • Information Model – Document definition – Context rules
Core Components • Reusable low-level data structures – e. g. , party, address, phone, date, currency – Context-sensitive • Single, consistent lexicon • Used to define business process and information models • Facilitates interoperability between disparate systems
Context Affects Process • • • Industry Sector Product Business process Geo-political region Official constraints – – Legislative Standards Good practice Contractual
Business Process . . . Create Long Term Contract Business Process Collaboration Forecast Component Requirements Transaction Send Planning Document Customer Collaboration Place Order Ship Materials Arrange Payment Supplier
eb. XML Specification Schema Business Process Composition Partner Types Business Collaboration Choreography Transition Guard Request Document Roles Business Transaction Response Document Business Transaction Execution Patterns
BP and Info Modeling Architecture Patterns Content Patterns Business Process Modeling Information Modeling Methodology Content Methodology BP-Metamodel BP-model Info-Metamodel Model-XML Rules Conversion to XML Model-XML Rules XML BP-DTD XML BP-doc XML Info-DTD Registry
Conversion of UML Models to XML • Business process definitions • XML Schema and DTD generation • Populate classification scheme XML Schema XMI (MOF. DTD) Transformation Rules XML Process Definition Populate Classification Scheme
Traditional Classification Scheme Taxonomies Industry Health. Care Automotive Retail Geography USA Ford: object Japan Europe Toyota: object Chevy: object BMW: object Nissan: object
Registering Your Business • Register your business in an eb. XML Registry – Index to all information in the repository – Rich query facility • Store specifications in an eb. XML Repository – – – CPP Schemas Process models Core components Classification and categorization schemes Arbitrary objects and code
eb. XML Reg/Rep • eb. XML Registry and Repository – Registry = index of things – Repository = holder of things • Distributed model • Nodes maintained by – – – Industry groups Market places Exchanges Communities Individual companies
Negotiating an Agreement • Find registry and search for partners • Examine CPP • Ascertain compatibility of business process and technical specifications • Stipulate your “rules of engagement” • Produce Collaboration Protocol Agreement – Conditions under which two partners will conduct business transactions together
CP Agreement Formation • • Negotiate two Cooperative Protocol Profiles Party 1 queries and discovers Party 2 Party 1 proposes rules of engagement Sends CPA to Party 2 for review and acceptance Cooperative Protocol Profile 1 Cooperative Protocol Profile 2 Rules of Engagement Cooperative Partner Agreement
Collaborative Protocol Agreement • Agreement for business interaction between two parties – Technical specifications: • Message Service requirements • Application requirements – References: • CPPs • Legal terms and conditions
Business Service Interface • Implements the CPA, supporting dynamic integration • Not yet specified – Hand-crafted for the moment • Enables one Party to converse with the other Party using the eb. XML Message Service
eb. XML Message Service • Reliable, secure XML messaging service – Enforces the rules of engagement in CPA • Transport independent • Extends SOAP Messages with Attachments (Sw. A) – Reliability framework – Security framework – Manifest, trace, and delivery options
Delivery Options • Communications models – – Synchronous or asynchronous Request/response Fire and forget Multipart message delivery • Reliability options: – Best effort – Once and only once
Security • • Identification Authentication Authorization Privacy Integrity Non-repudiation Logging
eb. XML Message Structure Communication Protocol Envelope (HTTP, SMTP, etc. ) SOAP Messages with Attachments MIME Envelope MIME Part SOAP-ENV: Envelope SOAP-ENV: Header eb: Message. Header Message Package Header Container eb. XML Header Information eb: Trace. Header. List Other: etc… SOAP-ENV: Body eb: Manifest eb. XML Message Service Handler control data eb: etc… Other: etc… MIME Part Payload Container(s)
Summary of Components • Registry and Repository • Core Components • eb. XML Specification Schema – Business Process Model – Information Model • CPP/CPA • Message Service
SOAP and UDDI • Obviously useful, but they don’t constitute an end-to-end B 2 B framework • No support for business models or negotiating business agreements • No Quality of Service facilities • Complementary not competitive to eb. XML – SOAP provides messaging foundation – UDDI helps you find eb. XML services – eb. XML Repository stores service specifications
eb. XML Timetable Sept 1999 eb. XML Commissioned -- Canberra Nov 1999 First Meeting – San Jose May 2000 Requirements document -- Brussels Nov 2000 Message Service beta - Tokyo Feb 2001 Technical Architecture - Vancouver Mar 2001 All specs in review May 2001 All specs released - Vienna
eb. XML Summary • Worldwide project to standardize the exchange of electronic business data • XML-based infrastructure to enable consistent, secure, and interoperable message exchange • Supported by hundreds of industry consortia, standards bodies, companies, and individuals from around the world
eb. XML Changes the Future • Out-of-the-box technical interoperability • Unambiguous commercial interoperability – Explicitly specified and “executable” business processes • Service-based business process architecture • Enable the evolution of many new business models and patterns
Resources • eb. XML Participation & Mailing Lists – Open to everyone – http: //www. ebxml. org/participate. htm • eb. XML Specifications – http: //www. ebxml. org/specdrafts/approved_specs. htm
- Slides: 36