An ebXML Vision Electronic Business Collaborations ebXML BP-Analysis Team An ebXML Vision Electronic Business Collaborations Karsten Riemer, Sun Microsystems

Vision of ebXML Collaborations Process Definition Partner Discovery Process Evolution Electronic Business Collaboration Partner Sign-Up Process Management Process Execution Electronic Plug-in

Architecture of ebXML Collaborations RegRep BP CC BPEng CPP Process Definition Partner Discovery Management Execution Electronic Plug-in Sign-Up Evolution BPM Electronic Business Collaboration CPA BSI TRP/BSI

Business Service Interface ebXML Architecture BP Specification Business Process Core Data Blocks Business Messages CPA Context For Built With Implement one Partner Role Implement other Partner Roles Register Designtime CPP Transport Package Business Service Interface Internal Business App Runtime This model describes not only how all this will work, but also provides a good idea of how ebXML is organized. For example, The Business Process project team is developing the methodology for building models of business processes, and the Core Components group will publish a methodology for defining core blocks of business data. And both groups develop examples, from common business processes, to prove the validity of their methodologies. These two teams work closely together, and their work products will enable standards and industry groups to develop business messages. These will be stored in a global ‘repository’, which will probably be many repositories all linked together. Like the Internet! The Trading Partner Profile team is describing how trading partners will share information about themselves. Transport will handle the actual exchange of all this information, and the messages between trading partners. And those are just a few of the work efforts going on at ebXML. You’ll see this slide again, with some variation, when we talk about Proof of Concept.

Business Collaboration Anatomy of a Collaboration (adapted from UMM Metamodel) Process Classification Business Process Hierarchy Business Collaboration Agreement Economic Event Partner Types Business Transaction Request Document Response Document Roles Choreography Transition Guard

Business Process Editor: Define the “outside” of the collaboration Actors Precondition Result Collaboration Ends When Starts When

Business Process Editor: Choreograph Transactions into Collaborations Roles Start End Transaction Guard Failed Roles Roles Start End Transaction Guard Start End Transaction Failed Guard Failed

Business Process Editor: Define each transaction Responding Role Requesting Role Business Transaction End RequestDocSet Start Requesting Activity Responding Activity ResponseDocSet Guard Fail