bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Implementing cXML

cXML Administration

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.

Administration of cXML transactions is performed using the WebLogic Integration B2B Console. The following sections describe the administrative work required to support cXML transactions:

- Connecting to Other cXML Trading Partners

- Collaboration Agreements

- Security

Connecting to Other cXML Trading Partners

Conversations between cXML trading partners use both peer-to-peer and hub-and-spoke configurations. While these configurations are discussed in Introducing B2B Integration as they apply to most situations, cXML varies slightly in its use of these configurations. The following illustration demonstrates how a routine cXML transaction uses both topologies simultaneously.

Figure 2-1 cXML Deployment Configurations

In this illustration, the Ariba Commerce Services Network (ACSN) is the hub. Most transactions are performed through this hub, with individual trading partners serving as the related spokes. However, when you browse a partner's catalog, a PunchOut trading session is created that connects directly to the remote system. In this case, the hub-and-spoke topology is bypassed in favor of a peer-to-peer configuration. Once the PunchOut session is finished, and the Buyer wants to send an Order or a Subscription, then the system topology reverts to a hub-and-spoke model, and the ACSN again acts as the hub.

It is important to note that when cXML is used with WebLogic Integration, the ACSN is the only authorized hub. WebLogic Integration does not provide support for any other hub-and-spoke deployments, and no other system is capable of acting as a hub for cXML-based transactions.

Collaboration Agreements

Collaboration agreements used with cXML are similar in scope and effect to collaboration agreements configured for other trading protocols. For more information about configuring collaboration agreements, see Administering B2B Integration and Online Help for the WebLogic Integration B2B Console.

The one significant difference in configuring collaboration agreements lies in how credentials are configured. Because cXML uses the Ariba Commerce Services Network as the authenticating hub, all credentials are configured in relation to the ACSN, not in relation to another trading partner.

In practice, this means that your shared secret is always registered with the ACSN, rather than one that is defined solely and specifically between you and a trading partner.

Security

WebLogic Integration provides support for the security model embodied in cXML 1.1, which uses the concept of shared secrets to verify message authenticity. Shared secrets are passwords or other text strings used to verify the identity of a given partner. Like a password, a given trading partner entity is linked to a specific shared secret, providing one-to-one identity mapping. There is no provision to prevent multiple trading partners from using identical shared secrets, however.

cXML 1.2 introduces a specific implementation of digital signatures based on the Base64-encoded X.509 V3 certificate model. Currently, WebLogic Integration does not support this implementation of digital signatures.

Configuring Shared Secrets

Use the WebLogic Integration B2B Console to configure shared secrets. For more information about this procedure, see Online Help for the WebLogic Integration B2B Console.