A routing ID is a unique identifier that Activator uses as the "to" and "from" address for e‑commerce messages exchanged over the Internet.
There is a relationship between routing IDs (used for partner identification at the transport level) and messaging IDs (used for partner identification at the message level). Typically, routing IDs are automatically generated based on the messaging IDs created for the partner. Users can add routing IDs manually as well.
When you add a community or partner, the user interface prompts you to enter one routing ID. After the initial community or partner setup, you can add as many additional routing IDs as you want. To add or delete a routing ID, click Routing IDs on the navigation graphic at the top of the community or partner summary page and follow the prompts.
Although a community or partner can have many routing IDs, the user interface designates one per community or partner as the default. Default routing IDs are used by default for message protocol headers when packaging messages. For example, when packaging an AS2 message, the default routing IDs are used for as2‑to and as2‑from attributes in headers, regardless of the routing IDs parsed from the payload. In the user interface you can change the default routing IDs for a community or partner. To override default routing IDs, you work with user-defined collaboration settings.
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.
If you use the ebXML message protocol, see Routing ID for ebXML for special requirements.