Home > Articles

Like this article? We recommend

Like this article? We recommend

ebXML Concepts

This section provides an overview of the general concepts for using ebXML in a B2B environment. The five modules described in this section make up an ebXML framework. They are very modular and can be used independently. The modules included provide the following capabilities:

  • Reliable messaging. ebMS and MSH

  • Rules for exchanging messages. CPP and CPA

  • Business process workflow and collaboration. BPSS

  • Discovery. Registry and repository

  • Data items to capture business concepts. Core components

The following figure describes the design time (green) and runtime (red) interaction between trading partners in a B2B interaction using ebXML. The interactions begin with the development of a BPSS and CPP XML description of a business process. These documents get published to the ebXML registry and repository. A trading partner looks up the documents from the registry, and a trading partner agreement is negotiated and saved as a CPA. CPA and BPSS are then shared with each trading partner and loaded into the runtime infrastructure. The runtime execution is then kicked off by a cron job or a trigger from a back-end application and ebXML messages flow from one trading partner to the other through the Message Service Handler (MSH). The flow of messages traverses the business process based on the state machine-like workflow described in the BPSS and constraints and service level descriptions of the CPA.

Figure 2FIGURE 2 Using ebXML to Connect Business Applications at Trading Partners

The goal of ebXML is to provide an open XML-based infrastructure to enable enterprises to conduct business over the Internet. It offers a standardized set of APIs and technologies that promote ad-hoc business collaboration. ebXML builds on the experience of EDI, and takes advantage of XML and the Internet. ebXML consists of the following architectural modules.

Messaging Service

ebXML provides an ebMS for environments that require a robust, low-cost solution to enable electronic business. It is a standard method for exchanging business messages among ebXML trading partners.

The ebMS is a closely coordinated definition for an ebXML MSH. It defines the message enveloping and header document schema used to transfer ebXML messages over a communications protocol such as HTTP or SMTP, and the behavior of software sending and receiving ebXML messages. The ebMS is defined as a set of layered extensions to the base SOAP and SOAP Messages with Attachments specifications.

Figure 3FIGURE 3 Top-Level View of ebXML Messaging Service

SOAP with Attachments provides the ability to transport non-XML data, as required. An ebXML message contains structures for a message header (necessary for routing and delivery) and a payload section.

The ebXML message service provides security and reliability features that are not available in SOAP, but are necessary to support international electronic business. The ebXML message service is structured to enable messaging reliability, persistence, security, and extensibility.

The message service handler (MSH) provides the following functionality:

  • Message header processing

  • Message header parsing

  • Security services

  • Reliable messaging services

  • Message packaging

  • Error handling

Partner Profile and Agreement

The business process specification serves as primary input for forming collaboration protocol profiles and agreements. This section describes the documents that are used to create the rules for exchanging messages.

Collaboration Protocol Profile

A collaboration protocol profile (CPP) describes the message-exchange capabilities between business partners that engage in business transactions. It describes business capabilities such as what business processes are available. Also, it describes the technical capabilities, including messaging exchange capabilities; as well as transport, messaging, and security constraints. The CPP is stored in the ebXML Registry.

The CPP, which enables the automation of business collaboration, is a machine-readable description that can be published and discovered. With the CPP, business collaboration is specified in a declarative, rather than a procedural, manner.

Collaboration Protocol Agreement

The message-exchange agreement between two business partners is described by a collaboration protocol agreement (CPA). The CPA is a technical, binding description: It specifies the exact requirements and mechanisms for the transactions through which two companies exchange messages electronically. The CPA references the CPP business process schema definition. The CPA can define delivery channels, abstract configurations of how messages are exchanged, and characteristics of message exchange on a message-by-message basis. By comparison, WSDL is just a common, shared endpoint.

The trading partners' computing systems use the CPA to set up a runtime environment. This enables the exchange of business messages through the MSH, which ensures message security and reliability. Along with process specification, the CPA defines a conversation between the two parties.

Business Process

Business process models enable organizations to create software components that collaborate on behalf of business partners. Business processes are the verbs of electronic business and can be represented using modeling tools. The specification for business process definition enables an enterprise to express its business processes so that they are understandable by other enterprises. This enables the integration of business processes within an enterprise or between enterprises.

Business process models specify business processes that enable partners to collaborate. While practices vary from one organization to another, most activities can be decomposed into business processes that are generic to a specific type of business. This analysis, which utilizes business modeling, identifies business processes and business information metamodels that can likely be standardized. The ebXML approach looks for standard reusable components from which to construct interoperable processes.

The ebXML business process specification schema (BPSS) supports the specification and collaboration of business transactions into business collaborations. Each business transaction can be implemented using one of many available standard patterns. These patterns determine how business documents and signals between trading partners are exchanged to achieve the required electronic transaction.

The ebXML BPSS supports the specification of business transactions and the collaboration of business transactions into business collaborations using the unified modeling methodology (UMM). The ebXML BPSS is available in two stand-alone representations, a UML version and an XML version.

To help specify the patterns, UMM provides a set of standard patterns, and BPSS provides a set of modeling elements in support of those patterns.

Registry and Repository

The ebXML Registry provides a general purpose content management system that enables publishing and discovery of arbitrary content, as shared information between interested parties, for the purpose of allowing business process integration. Content submitted for sharing can include XML schema and documents, process descriptions, core components, context descriptions, UML models, information about parties, and even software components. Standardized metadata is stored in the registry to catalog the published content. This published content is stored in a corresponding repository, and is used to facilitate ebXML-based B2B partnerships and transactions.

The ebXML Registry can be used to store many types of content. In many ways, it plays a similar role in Web services as relational databases play in enterprise applications. Depending on the use case, the ebXML Registry can be used at design time, at runtime, or at both design and runtime. It is common in B2B integration to use an ebXML Registry to store a business process. In this prototype, the main goal of the repository is to enable the developer to download the schema for a business process at design time. The ebXML Registry provides a superset of functionality provided by UDDI. UDDI is suitable for use cases involving simple publish/discovery of organizations and services. The ebXML Registry is more appropriate when there is a need for more complex metadata, extensibility, ad hoc querying, and support for arbitrary content.

Core Components

Core components represent a set of common data items that capture real-world business concepts. They use industry-neutral notation, which enables interoperability among industry domains. ebXML core components are similar to a catalog of XML schemas for business information entities. Core components can be assembled like building blocks, creating the intended message for a business process.

When a new trading partner message is created or an existing one is changed, it is done by creating new core components in the prototype. For our prototype, new core components were implemented using custom document type definition (DTD). A business process might contain multiple core components. However, an essential aspect of our Sun ONE Application Server B2B collaboration prototype is that the underlying infrastructure—BPSS, MSH, and so on—remains the same.

XML Grammars and Standards Initiatives

While they solve a large part of the problem, standard XML messages are not robust enough to provide traditional EDI functionality on the Web. A reliable XML messaging framework is also needed to implement the equivalent of EDI networks on the Internet. ebXML defines core components, business processes, XML Registry, messaging services, trading partner agreements, and security.

To facilitate convergence of data standards for electronic businesses, the universal business language (UBL) initiative with OASIS defines specific XML schemas for common business documents such as purchase orders, invoices, and shipping notices. Though still in its early stages, the UBL effort is rapidly gaining support from EDI organizations and consortia, representing industries as far ranging as electronics, IT, retail, insurance, and accounting.

The ebXML initiative is complementary to UBL, and neutral with regard to particular XML syntaxes. ebXML delivered three basic components of a first-generation infrastructure for XML-based electronic commerce: a specification for XML messaging, a specification for trading partner agreements, and a specification for registries and repositories. These specifications are designed in a way that allows businesses to use them separately or together. UBL is intended to provide standard documents that can be exchanged over standard messaging, after the partners have been looked up in a registry.

WS-I Basic Profile Standard

This section provides an overview of the general concepts for using WS-I Basic Profile. A profile is a named group of Web services specifications at specific version levels, along with conventions about how they work together. WS-I is developing a core collection of profiles that support interoperability for general-purpose Web services functionality.

Through the first phase of Web services adoption, four specifications have risen to prominence as providing the basic functionality required to start developing Web services. These specifications are XML Schema 1.0, SOAP 1.1, WSDL 1.1, and UDDI 2.0. The first profile proposed is WS-I Basic Web services.

This set of specifications is used to provide the basic XML schema, packaging, and enterprise service definitions. It provides a base building block that is leveraged and extended by the ebXML standards as described earlier.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020