Router

Allows business documents to be routed based on participant preferences. Participants can be configured with different services to enable business documents to be delivered to them. In the scenario modeling, data published to trading partners is marked through a Router.

Router extracts the organization code from the data published during run time and extracts relevant organization preferences for document delivery and executes the service specified for the Participant.

Configuration properties

The following are the properties of this node:

Table 1. Router configuration properties
Property Description
Document Name Select the document being routed to the Participant. For example, Purchase Order.
Route XML Data To Following Roles
Trading Partner Role Select the participant’s role. For example, BUYER or SELLER
XML Attribute Enter the XML path where the participant’s organization code is located. For example, xml://Order/@OrganizationCode.

Participant preferences are appended to the document before executing the specified service.

Connection properties

The following are the Router node’s connection properties:

Table 2. Router connection properties
Connection Node Connection Rules
Can be the first node after the start node Only for services invoked synchronously
Can be placed before
  • Any transport node except FTP or File I/O
  • Any other component node
Can be placed after
  • Start node
  • Any transport node except FTP or File I/O
  • Any other component node
Passes data unchanged Yes