ebXML Technologies | XML, Web Services, and the Data Revolution


Team-Fly

	XML, Web Services, and the Data Revolution By Frank P. Coyle
	Table of Contents

	Chapter 5. Web Services

ebXML is inclusive of small and large businesses.

Electronic Business XML is based on a set of building blocks that makes use of existing standards wherever possible. The ebXML specifications have been developed through a worldwide volunteer effort in a process that is open and transparent. Anyone, anywhere with a computer and Internet connection may participate in the ebXML initiatives.

The technical architecture consists of several pieces:

Messaging: ebXML uses SOAP to send messages.
Business processes: ebXML distinguishes itself from other XML frameworks through its emphasis on business processes. Modeling languages and charting tools such as the Unified Modeling Language (UML) are used to standardize and capture the flow of business data among trading partners .
Trading partner profiles and agreements: ebXML defines an XML-based Collaboration Protocol Profile (CPP) to list supported industries, business processes, messages, and data-exchange technologies.
Registries and repositories: Registries contain the industry processes, messages, and vocabularies that define the transactions that occur between trading partners.
Core components : Core components operate at the data level to provide interoperability among industries and identify the data items that businesses use most often across industries, assigning them neutral names and unique identifiers.

ZwiftBooks and ebXML

ZwiftBooks uses ebXML to define a process for doing business.

As we can see in Figure 5.6, ZwiftBooks first reviews the contents of an ebXML registry to determine the requirements for an ebXML implementation appropriate for the publishing industry. Having determined the appropriateness of relevant ebXML transaction definitions, ZwiftBooks decides to buy rather than internally generate the software needed to support the anticipated ebXML transactions.

Figure 5.6. The steps in an ebXML-driven business process.

graphics/05fig06.jpg

The next step is for ZwiftBooks to create and register a CPP with the ebXML registry. If ZwiftBooks has found a suitable Business Process in the registry, it will use it; otherwise it will define a process peculiar to its way of doing business and register it in the registry. The net effect will be sufficient information in the CPP for potential partners to determine the business roles in which ZwiftBooks is interested and the type of protocols it expects from its potential partners.

When ZwiftBooks has registered its CPP, other companies can query the ebXML repository to determine compatibility. If the potential partner determines that partnering is feasible , negotiation can proceed based on conformance to the CPPs. While it may be ideal to have all this occur automatically online, the reality of partnering will likely involve person-to-person interaction before final deals are signed. Once agreement has been reached, the two companies can begin doing business and engaging in transactions.

ebXML Terminology

Registry: A central server that stores a variety of data necessary to make ebXML work. Among the information a registry makes available in XML form are Business Process and Information Meta Models, the Core Library, Collaboration Protocol Profiles, and the Business Library. Basically, when a business wants to start an ebXML relationship with another business, it queries a registry in order to locate a suitable partner and to find information about requirements for dealing with that partner.

Business Processes: Activities that a business can engage in and for which it would generally want one or more partners. A Business Process is formally described by the Business Process Specification Schema (a World Wide Web Consortium [W3C] XML Schema and also a document type definition), but may also be modeled in UML.

Collaboration Protocol Profile (CPP): A profile filed with a registry by a business wishing to engage in ebXML transactions. The CPP will specify some Business Processes of the business, as well as some Business Service Interfaces it supports.

Business Service Interface: The ways that a business is able to carry out the transactions necessary in its Business Processes. The Business Service Interface also includes the kinds of Business Messages the business supports and the protocols over which these messages might travel.

Business Messages: The actual information communicated as part of a business transaction. A message contains multiple layers. At the outside layer, an actual communication protocol must be used, such as HTTP or SMTP. SOAP is an ebXML recommendation as an envelope for a message payload. Other layers may deal with encryption or authentication.

Core Library: A set of standard parts that may be used in larger ebXML elements. For example, Core Processes may be referenced by Business Processes. The Core Library is contributed by the ebXML initiative itself, while larger elements may be contributed by specific industries or businesses.

Collaboration Protocol Agreement (CPA): In essence, a contract between two or more businesses that can be derived automatically from the CPPs of the respective companies. If a CPP says "I can do X," a CPA says "We will do X together."

SOAP: The W3C protocol for exchange of information in a distributed environment endorsed by the ebXML initiative. Of interest for ebXML is SOAP's function as an envelope that defines a framework for describing what is in a message and how to process it.


Team-Fly

Top