The ebXML Technology

The simplest way to view the ebXML Technology is to show a high-level use case scenario for two Trading Partners, first configuring and then engaging in a simple business transaction and interchange. The model describes an example of the process and steps that may be required to configure and deploy ebXML Applications and related architecture components.  From this model the Architecture of ebXML can be derived.

Here Company A has become aware of an ebXML Registry that is accessible on the Internet (Step 1). Company A, after reviewing the contents of the ebXML Registry, decides to build and deploy its own ebXML compliant application (Step 2). Custom software development is not a necessary prerequisite for ebXML participation. ebXML compliant applications and components may also be commercially available as shrink-wrapped solutions.

Company A then submits its own Business Profile information (including implementation details and reference links) to the ebXML Registry (Step 3). The business profile submitted to the ebXML Registry describes the company’s ebXML capabilities and constraints, as well as its supported business scenarios. These business scenarios are XML versions of the Business Processes and associated information bundles (e.g. a sales tax calculation) in which the company is able to engage.  After receiving verification that the format and usage of a business scenario is correct, an acknowledgment is sent to Company A (Step 3).

Company B discovers the business scenarios supported by Company A in the ebXML Registry (Step 4). Company B sends a request to Company A stating that they would like to engage in a business scenario using ebXML (Step 5). Company B acquires an ebXML compliant shrink-wrapped application.

Before engaging in the scenario Company B submits a proposed business arrangement directly to Company A’s ebXML compliant software Interface. The proposed business arrangement outlines the mutually agreed upon business scenarios and specific agreements. The business arrangement also contains information pertaining to the messaging requirements for transactions to take place, contingency plans, and security-related requirements (Step 5).  Company A then accepts the business agreement. Company A and B are now ready to engage in eBusiness using ebXML.

This conceptual overview introduces the following concepts and underlying architecture:

1. A standard mechanism for describing a Business Process and its associated information model.

2. A mechanism for registering and storing Business Process and Information Meta Models so they can be shared and reused.

3. Discovery of information about each participant including:
         -  The Business Processes they support.
         -  The Business Service Interfaces they offer in support of the Business Process.
         -  The Business Messages that are exchanged between their respective Business Service
            Interfaces.
          - The technical configuration of the supported transport, security and encoding protocols.

4. A mechanism for registering the afore mentioned information so that it may be discovered and retrieved.

5. A mechanism for describing the execution of a mutually agreed upon business arrangement which can be derived from information provided by each participant from item 3 above. (Collaboration Protocol Agreement – CPA).

6. A standardized business Messaging Service framework that enables interoperable, secure and reliable exchange of Messages between Trading Partners.

7. A mechanism for configuration of the respective Messaging Services to engage in the agreed upon Business Process in accordance with the constraints defined in the business arrangement.
    

The relationships of these concepts and the architecture itself are described in the ebXML Technical Architecture Specification v1.04. http://www.ebxml.org/specs/ebTA.pdf.

Having described the concepts and architecture it is shown that there are multiple technological pieces that are needed to complete the ebXML Technical Architecture. These pieces can be placed into two differing Infrastructure categories. These are:

·     The Semantic Framework Infrastructure

·     The Technical Infrastructure

Within these Infrastructures categories fits each individual piece of the Architecture.

An ebXML specification is linked to each piece of this architecture. How these fit together is shown in the ebXML Infrastructure and its relevant specifications figure.

Developed by CEN/ISSS W/S eBES - ©1999-2003 All Rights reserved. Terms of use       

This page last modified on 2003-10-21