Modify a routing ID

After you create a Community or Partner, you can:

• Add additional routing IDs
• Delete routing IDs

Add a community routing ID

1. In the user interface, select Trading configuration > Manage trading configuration to display the Communities page.
2. From the list of communities, click the name of a community to display the Summary page for that community.
3. In the navigation graphic at the top of the screen, click the Routing IDs icon to open the Routing IDs page.
4. In the Add a routing ID section, complete the fields:
   • Routing ID – Enter a routing ID. A routing ID can be in any format or length (up to 255 characters), including standard EDI or custom formats that include special characters or spaces.
   • Party ID type – For ebXML, AS4 or WebServices traders only, enter an ebXML party ID type only if the routing ID you enter is not a URI. For cXML traders only, enter the matching cXML credential domain type. For more information, see Routing ID for ebXML.
5. Click Add.

Add a partner routing ID

1. In the user interface, from the Partners menu select Manage partners.
2. From the list of partners, click the name of a partner to display the Summary page for that partner.
3. In the graphic map at the top of the screen, click the Routing IDs icon to open the Routing IDs page.
4. In the Add a routing ID section, complete the fields:
   • Routing ID – Enter a routing ID. A routing ID can be in any format or length (up to 255 characters), including standard EDI or custom formats that include special characters or spaces.
   • Party ID type – For ebXML, AS4 or WebServices traders only, enter an ebXML party ID type only if the routing ID you enter is not a URI. For cXML traders only, enter the matching cXML credential domain type. For more information, see Routing ID for ebXML.
5. Click Add.

Delete a routing ID

1. On the Routing IDs page of a partner or community, in the list of routing IDs, click Delete for any routing ID that you want to remove.
2. Click OK to confirm and complete the delete action.

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.
• 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.

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.

Related topics

• Routing IDs
• Add a routing ID