ebXML Registry Registry egstry Interfaces The registry ovides the Client Registry Cent interfaces interfaces to a ers na aweb based Internet Registry Clent Interfa ng a Regsty browser ha contains the Client Figure 9-1 Registry Architecture Supports Flexible Topologies 9.2.2 Collaboration Protocol Profile( CPP)& Collaboration Protocol Agreement(CPA) To facilitate the process of conducting eBusiness, potential Trading Partners need a mechanism to publish infomation about the Business Processes they support along with specific technology implementation details about their capabilities for exchanging business information This is accomplished through the use of a Collaboration Protocol Profile(CPP). The CPP is a document which allows a Trading Partner to express their supported Business Processes and Business Service Interface requirements in a manner where they can be universally understood by other eb XML compliant Trading Partners A special business agreement called a CPA is derived from the intersection of two or more CPP's. The CPA serves as a formal handshake between two or more Trading Partners wishing to conduct business transactions using ebXML 1. Collaboration Protocol Profile(CPP) 1)CPP Formal Functionality The CPP describes the specific capabilities that a Trading Partner supports as well as the Service Interface requirements that need to be met in order to exchange business documents with that Trading Partner. The CPP contains essential information about the Trading Partner including, but not limited to: contact information, industry classification, supported Business Processes, Interface requirements and Messaging Service requirements. CPP's MAY also contain security and other implementation specific details. Each ebXML compliant Trading Partner SHOULD register their CPP(s) in an ebXML compliant Registry Service, thus providing a discovery mechanism that allows Trading Partners to(1)find one another, (2)discover the Business Process that other Trading Partners support he Cpp definition ShalL provide for unambiguous selection of choices in all instances where there may be multiple selections(e.g. Http or Smtp transport 2)CPP Interfaces A CPP SHALL be capable of referencing one or more Business Processes supported by the Trading partner owning the CPP instance. The CPP Shall reference the roles within a Business Process that the user is capable of assuming. An example of a Role could be the notion of a"Seller” and"Buyer” within a^ Purchasing” Business process The CPP ShALL be capable of being stored and retrieved from an ebXML Reg Mechanism A CPP SHOULD also describe binding details that are used to build an ebXml mess HeaderFigure 9-1 Registry Architecture Supports Flexible Topologies 9.2.2 Collaboration Protocol Profile (CPP) & Collaboration Protocol Agreement (CPA) To facilitate the process of conducting eBusiness, potential Trading Partners need a mechanism to publish information about the Business Processes they support along with specific technology implementation details about their capabilities for exchanging business information. This is accomplished through the use of a Collaboration Protocol Profile (CPP). The CPP is a document which allows a Trading Partner to express their supported Business Processes and Business Service Interface requirements in a manner where they can be universally understood by other ebXML compliant Trading Partners. A special business agreement called a CPA is derived from the intersection of two or more CPP’s. The CPA serves as a formal handshake between two or more Trading Partners wishing to conduct business transactions using ebXML. 1. Collaboration Protocol Profile (CPP) 1) CPP Formal Functionality The CPP describes the specific capabilities that a Trading Partner supports as well as the Service Interface requirements that need to be met in order to exchange business documents with that Trading Partner. The CPP contains essential information about the Trading Partner including, but not limited to: contact information, industry classification, supported Business Processes, Interface requirements and Messaging Service requirements. CPP’s MAY also contain security and other implementation specific details. Each ebXML compliant Trading Partner SHOULD register their CPP(s) in an ebXML compliant Registry Service, thus providing a discovery mechanism that allows Trading Partners to (1) find one another, (2) discover the Business Process that other Trading Partners support. The CPP definition SHALL provide for unambiguous selection of choices in all instances where there may be multiple selections (e.g. HTTP or SMTP transport). 2)CPP Interfaces A CPP SHALL be capable of referencing one or more Business Processes supported by the Trading Partner owning the CPP instance. The CPP SHALL reference the Roles within a Business Process that the user is capable of assuming. An example of a Role could be the notion of a “Seller” and “Buyer” within a “Purchasing” Business Process. The CPP SHALL be capable of being stored and retrieved from an ebXML Registry Mechanism A CPP SHOULD also describe binding details that are used to build an ebXML Message Header