Introduction

Note: The cXML business protocol is deprecated as of this release of WebLogic Integration. For information about the features that are replacing it, see the BEA WebLogic Integration Release Notes.

This section introduces the cXML standard for electronic business transactions. cXML is an extensible e-commerce-oriented XML standard developed by Ariba and widely used for e-commerce purchasing transactions.

This section describes the following aspects of the cXML standard and its use with WebLogic Integration:

• WebLogic Integration Architecture and cXML

• cXML API

• Business Documents

• Digital Signatures and Shared Secrets

• Message Validation

• Limitations

 

---

WebLogic Integration Architecture and cXML

cXML support provided by WebLogic Integration consists of the following components:

• cXML protocol layer

• cXML API support

cXML integration is provided through the use of business process management (BPM) business operations and the cXML API. For more information, see Using the cXML API, and Using Workflows with cXML.

The following diagram illustrates the cXML architecture used by WebLogic Integration, and shows how WebLogic Integration interacts with other systems using cXML.

Figure 1-1 WebLogic Integration cXML Architecture

 

WebLogic Integration support for cXML is designed to allow seamless integration of cXML with the standard B2B integration infrastructure. For more information about the remainder of the B2B integration architecture, see Introducing B2B Integration.

Because of the design environment for cXML, support for hubs other than the Ariba Commerce Services Network is not provided.

cXML Protocol Layer

The cXML protocol layer provides the ability to send and receive messages via the Internet, according to the cXML specifications for transport, message packaging, and security. WebLogic Integration creates individual cXML sessions, each of which creates and manages a URL where the WebLogic Integration server can receive cXML messages. You can configure cXML sessions, as needed, by using either the WebLogic Integration B2B Console or a configuration file. To use a WebLogic Integration configuration file, create a configuration file based on the WLC.dtd file to configure cXML sessions as needed. If you choose this approach, use the Bulk Loader to load the configuration file into the repository.

 

---

cXML API

WebLogic Integration includes comprehensive API support for the creation of cXML user applications. For more information about the cXML API, see Using the cXML API, and the BEA WebLogic Integration Javadoc.

 

---

Business Documents

Business document processing is performed in WebLogic Integration using a combination of public and private processes. Public processes are processes used to integrate and manage transactions between trading partners. Private processes are processes used internally by a trading partner; for example to communicate between a company's public processes and its internal ERP and CRM systems. Private processes are thus not directly exposed for trading partner consumption or use. For further explanation, see "Managing Business Processes" in Overview in Introducing B2B Integration.

cXML business documents are part of the public processes in which trading partners participate while performing e-business transactions. For example, a PunchOut is part of the process that a Customer trading partner performs with a Product Supplier trading partner to get information from a live repository on the price and availability of goods that the Customer wants to buy and the Product Supplier wants to sell. Trading partners planning to use PunchOuts must do the following:

• Implement the public process associated with the PunchOut

• Connect their internal systems, as well as their private processes and workflows, to the public process

WebLogic Integration implements all business documents available within cXML:

• Catalogs

• PunchOuts

• Purchase Orders

• Subscriptions

For further information on cXML business documents, go to the cXML.org Web site at the following URL:

http://www.cxml.org  

 

---

Digital Signatures and Shared Secrets

The standard method of securing transactions in cXML is the shared secret. In cXML terms, a shared secret is typically a username/password combination, exchanged through secure transport before business communication begins.

WebLogic Integration includes full support for cXML shared secrets. For more information about implementing and configuring shared secrets, see the Online Help for the WebLogic Integration B2B Console. In addition, you may optionally use https transport for your messages.

In cXML v1.2, optional digital signatures based on the Base64-encoded X.509 V3 certificate model were introduced. These digital signatures are not the same as the RSA CertJ digital signatures implemented in WebLogic Integration. Currently WebLogic Integration does not support cXML digital signatures. For more information, visit the cXML.org Web site at the following URL:

http://www.cxml.org 

 

---

Message Validation

The cXML standard requires all cXML documents to be valid and to refer to published cXML Document Type Definitions (DTDs). Validation is not required by the cXML standard, but it is provided by WebLogic Integration as a service.

 

---

Limitations

Several cXML-related features are not supported in this release of WebLogic Integration:

• Digital Certificates: As discussed earlier, cXML 1.2 digital certificates are not supported.

• cXML 1.2 attachments are not supported at this time.

• Non-ACSN hub support: No support is provided for any hub other than the Ariba Commerce Services Network. All hub-based transactions must be routed through the ACSN. Peer-to-peer support is provided.

• No Sample implementation is provided at this time.