3. CPP/CPA with ebXML Registry Part A Regi CPAY Pary B Figure 9-3 Overview of working architecture of CPP/C PAwith ebXML registry (1) Any Party may register its CPPs to an ebXML Registry (2) Party B discovers trading partner ching in the Registry and downloads CPP(A)to Party B server. (3) Party B creates CPA(A, B)and sends CPA(A, B)to Party a (4) Parties A and B negotiate and store identical copies of the completed CPA as a document in both servers. This process is done manually or automatically (5) Parties A and B configure their run-time systems with the information in the CPa (6 Parties a and b do business under the new CPA 9.2.3 ebXML Message Structure and Packaging Figure 9-4 below illustrates the logical structure of an ebXML Message Transport Envelope(smtp, Http, etc. ) bXML Message Envelope(MIME multipart/related) ebXML Header Envelope ebXML ebXML Header Document Header Manifest leader bXML Payload Envelope Payload Container Figure 9-4 ebXML Message Structure An ebXML Message consists of an optional transport Protocol specific outer Communication Protocol Envelope and a Protocol independent ebXML Message Envelope. The ebXML
3. CPP/CPA with ebXML Registry Figure 9-3 Overview of working architecture of CPP/CPAwith ebXML registry （1） Any Party may register its CPPs to an ebXML Registry. （2） Party B discovers trading partner A(Seller) by searching in the Registry and downloads CPP(A) to Party B server. （3） Party B creates CPA(A,B) and sends CPA(A,B) to Party A. （4） Parties A and B negotiate and store identical copies of the completed CPA as a document in both servers.This process is done manually or automatically. （5） Parties A and B configure their run-time systems with the information in the CPA. （6） Parties A and B do business under the new CPA. 9.2.3 ebXML Message Structure and Packaging Figure 9-4 below illustrates the logical structure of an ebXML Message. Transport Envelope (SMTP, HTTP, etc.) ebXML Message Envelope (MIME multipart/related) ebXML Header Envelope ebXML Header Document ebXML Payload Envelope ebXML Payload Document(s) Payload Container Manifest Header ebXML Header Container Figure 9-4 ebXML Message Structure An ebXML Message consists of an optional transport Protocol specific outer Communication Protocol Envelope and a Protocol independent ebXML Message Envelope. The ebXML
Message Envelope is packaged using the MImE multipart/related content type. MIME is used as a packaging solution because of the diverse nature of information exchanged between Partners in eBusiness environments. For example, a complex Business Transaction between two or more Trading Partners might require a payload that contains an array of business documents(XMl or other document formats), binary images, or other related Business Information 9.3 The operation of Business Processes 9.3.1 Business Processes and Business documents At a very basic level, a business process is the means by which one or more activities are accomplished in the conduct of business. Within the business process there could be one or more collaborations, each consisting of one or more transactions. Figure 9.5 below is a simple representation of a business process and an illustration of the types of business processes which might be needed between Customer and Supplier to complete an order for materials Business process Business Business Process Process Create Long Term Contract Collaboration Transaction Forecast Compon Transaction Send Planning Documen Collaboration Arrange Payment Figure 9-5 Business Collaborations, and Transactions Conceptual Vi 9.3.2 ebXML functional phases 1. Implementation Phase The implementation phase deals specifically with the procedures for creating an application of the ebXML infrastructure. A Trading Partner wishing to engage in an ebXML compliant transaction SHOULD first acquire copies of the ebXML Specifications. The Trading Partner tudies these specifications and subsequently downloads the Core Library and the business Library. The Trading Partner MAY also request other Trading Partners' Business Process information(stored in their business profile) for analysis and review. Alternatively, the Trading Partner MAY implement ebXML by utilizing 3rd party applications. The Trading Partner can also ubmit its own Business Process information to an ebXML compliant Registry Service Figure 9-6 below, illustrates a basic interaction between an ebXML Registry Service and a Trading Partner
Message Envelope is packaged using the MIME multipart/related content type. MIME is used as a packaging solution because of the diverse nature of information exchanged between Partners in eBusiness environments. For example, a complex Business Transaction between two or more Trading Partners might require a payload that contains an array of business documents (XML or other document formats), binary images, or other related Business Information. 9.3 The operation of Business Processes 9.3.1 Business Processes and Business Documents At a very basic level, a business process is the means by which one or more activities are accomplished in the conduct of business. Within the business process there could be one or more collaborations, each consisting of one or more transactions. Figure 9.5 below is a simple representation of a business process and an illustration of the types of business processes which might be needed between Customer and Supplier to complete an order for materials. Business Process Business Process Collaboration Transaction ... ... Transaction Collaboration Business Process Create Long Term Contract Forecast Component Requirements Send Planning Document Place Order Ship Materials Customer Arrange Payment Supplier Figure 9-5 Business Process, Collaborations, and Transactions Conceptual View 9.3.2 ebXML Functional Phases 1. Implementation Phase The implementation phase deals specifically with the procedures for creating an application of the ebXML infrastructure. A Trading Partner wishing to engage in an ebXML compliant transaction SHOULD first acquire copies of the ebXML Specifications. The Trading Partner studies these specifications and subsequently downloads the Core Library and the Business Library. The Trading Partner MAY also request other Trading Partners’ Business Process information (stored in their business profile) for analysis and review. Alternatively, the Trading Partner MAY implement ebXML by utilizing 3rd party applications. The Trading Partner can also submit its own Business Process information to an ebXML compliant Registry Service. Figure 9-6 below, illustrates a basic interaction between an ebXML Registry Service and a Trading Partner