Work with specific protocols and standards > ebXML > Set up a community for ebXML trading

Set up a community for ebXML trading

Configuring a community for ebXML trading is like setting up any community, with some notable differences. Primarily, the community must be associated with a community- and partner-specific CPA for trading to occur. The CPA determines options for message packaging, requests for acknowledgments and compression, not the collaboration settings in the user interface. In addition, the community routing ID must have a specific format.

See Communities and Add a community for details not specific to ebXML about setting up a community.

Routing ID for ebXML

When setting up a community for ebXML, the routing ID must be set up in one of two ways:

The routing ID (party ID) must be a Universal Resource Identifier (RFC 1630). For example, urn:myroutingid. When the routing ID is a URI, an ebXML party ID type is not necessary.
or
When the routing ID (party ID) is not a URI, enter an ebXML party ID type in addition to a unique routing ID. The ebXML party ID type can be any string (a URI, a DUNS number or something else) and the routing ID can be any unique string. For example: urn:mystring 123456789. The type value must match the PartyId /@type attribute value for the PartyInfo entry in the CPA for the community.

The user interface lets you set up routing IDs either way.

Moreover, if you trade with the same partner using both ebXML and any other message protocol, the community needs separate routing IDs for each protocol. The ebXML routing ID must not be the default. The default must be the routing ID used for the other message protocol.

The community and CPAs

The user interface lets you import complete CPAs as well as CPA templates and associate them with a community. Other than importing or deleting, however, tasks for managing CPAs are handled outside of this application. The exception is when you import a CPA template and have partners use the partner registration wizard. See ebXML partner self-registration.

When you import a complete CPA to Activator, several things occur. The CPA is associated with the importing community and the system creates a partner for the partner specified in the CPA. The system extracts from the CPA the public key certificate data and the URL or e-mail address for sending messages and adds them to the partner profile.

Your community is not affected when a CPA is imported. During the importing process, however, Activator checks whether the community keystore contains the corresponding private keys for all the signing and encrypting public keys in the PartyInfo section of the CPA.

Before a community can import a complete CPA, the community must be set up on Activator. The community name, routing ID, and certificate data must be the same in the community and the CPA.

Once the community and partner are configured and a CPA is associated with the community, message exchanges can begin.