/
(3.10) Int4 IFTT Dispatcher in Boomi

(3.10) Int4 IFTT Dispatcher in Boomi

The Dispatcher is used during test case execution to inject the inbound message into the corresponding interface. Please note that when the Start Shape can be invoked directly from the Int4 IFTT using an HTTP end-point, the Dispatcher is not required.
Also, do not forget to do the configuration for the Dispatcher on the Int4 IFTT side.

Please note that only in case of direct process call from Int4 IFTT you can omit the Dispatcher and make a direct call to the HTTP Client URL.

Dispatcher Process

The Dispatcher should have a Dell Boomi connector as Start Shape and a properly configured Web Service Server Operation Listener.
That way, any type of message would be able to enter into the dispatcher process.

The custom HTTP header field “x-wss-process“ keeps the process/interface name that should be executed. You can access this field by just reading the Dynamic Document Property “inheader_x-wss-process“. So, for every interface that has to be tested, there needs to be a corresponding routing in the Dispatcher.
For example, in the following Route Shape, there are handled three interfaces that may be invoked through Dispatcher:

Dell Boomi - Route Shape

After the Route Shape, you need to add a Connector with the additional configuration to send the message to the required process.

Lastly, you need to close the branches with Stop Shapes.

Related content

(3.10) Global Parameters configuration for Dell Boomi
(3.10) Global Parameters configuration for Dell Boomi
More like this
Creating the configuration object for the Dell Boomi interface
Creating the configuration object for the Dell Boomi interface
More like this
(3.10) Creating the configuration object for the Dell Boomi interface
(3.10) Creating the configuration object for the Dell Boomi interface
More like this
(3.10) Boomi Specific Template Solution
(3.10) Boomi Specific Template Solution
More like this

© 2017 - 2022 Int4 AG All rights reserved