This section specifies data for routing, i.e. receiving of messages from different source systems and transmitting them to different target systems. You can choose among routing strategies that correspond to various routing algorithms. xBus supports three strategies:

• Distribute - This routing function sends data to one or more systems and awaits no response data.
• Invoke - This is like a function call, data is sent to a system and the processing continues with the response. With multiple invokes a chain of senders can be implemented. This means the response data of one sender is used as the request data of the following sender.
• Invoke and Distribute - This is the combination of the above described. First the data goes through one or more invocations, then the response data of the last sender is distributed to one or more systems.

Data Flows explains these possibilities in more detail.

The sections and keys and values of the entries are used to configure the router:

	Router_source.function_Invoke1..n = destination Router_source.function_Distribute1..n = destination

where:

source - the name of the neighbor-system from which the data has been received

function - the name of a function, thathas been read out of the message

1..n - a serial number to determine the sequence of invokes or distributes

destination - the name of the system where the message shall be routed to

Note

• First all of the invokes will be processed, afterwards the distributes.
• At least one entry must be defined for each receiving system.

system-specific    optional

chapter	section	key	example
Router	logical name.function	Invoke1..n	Router_StockCheckAutolineRequest.StockCheck_Invoke1=StockCheckWholesale

Use this parameter, if a call to the neighbor-system shall be done with Invoke.

If you want to transmit the messages to multiple destinations, you should increase n on 1 for each next destination. For example:

	######################## # xxxSystem ######################## ... Router_System1.Default_Invoke1=System2 Router_System1.Default_Invoke2=System3 .....

Note that this parameter is not allowed for every sender, because some senders will not give back a response. The Technical Layer page describes, which senders give back a response.

system-specific    optional

chapter	section	key	example
Router	logical name.function	Distribute1..n	Router_PartsOrderAutoline.Default_Distribute1=PartsOrderWholesale

Use this parameter, if the data shall be distributed to a neighbor-system.

If you want to transmit the messages to multiple destinations, you should increase n on 1 for each next destination. For example:

	######################## # xxxSystem ######################## ... Router_System1.Default_Distribute1=System2 Router_System1.Default_Distribute2=System3 .....