on 08-15-2016 4:36 AM
Hi experts,
I need to setup a scenario File -> REST -> Multiple Files.
Initially I though I could use simple async/sync bridge:
File (async) --> XI --> REST (sync request)
REST (sync response) --> XI --> 0..N Files (async)
However I'm not sure how I could design it with 2 operation mappings, as the 2nd Op Mapping would have to be designed for multi mapping.
Anyone would please share how I could design this scenario if it's possible with async/sync or would it be done only by using BPM?
Tks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rafael!
First ICo:
Async interface for sender (File) with message type.
Sync receiver interface with request/response/fault message types (Rest).
Message mapping (if needed) to transform sender message to Rest request.
Operation mapping with request mapping only assigned to it (as response mapping will be processed by second ICo).
Second ICo:
Async interface for Rest response (Sender) with response message type.
Async receiver interface for your multiple files.
Message and operation mappings for Rest response transformation to multimessage structure (0..unbounded).
In receiver communication channel use adapter modules to build async-sync bridge. Take a look at screenshot above for example.
Refer to this blog to learn more:
Regards, Evgeniy.
Hi Rafael,
You can use a UDF to do the REST call. However, take note that if anything fails in the pipeline, the message will be persisted and will be executed 3 times (you don't want that to happen).
BPM would be the clean solution though.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.