| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB Flow design approach |
« View previous topic :: View next topic » |
| Author |
Message
|
| niks29986 |
 Posted: Thu Feb 12, 2015 3:46 am Post subject: WMB Flow design approach |
 |
|
Novice
Joined: 04 Sep 2014
Posts: 14
|
Hello Guys,
This is very useful platform to get the direction on almost every query on Integration space. Thanks for that!
My project is in design phase. It is a Mobile API using Message broker as middleware. The requirement is not very much in-line to the role of Message broker. The end to end design is almost done and Project is not willing to take a major step back.
Requirement:
1. App will make a call to WMB.
2. WMB sends the data to third party A over MQ.
3. WMB receives response from A and validates and sends to third party B (MQ).
4. WMB receives data from B, does some validation, data trimming and sends the response to Mobile APP.
There are almost 30 interfaces with similar calls.
All the above logic needs to be divided in separate flows with no thread wait.
I understand WMB is not a tool where you suppose to do this orchestration but I want to know your inputs on handling the situation.
Kind Regards,
Nikhil |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Feb 12, 2015 6:13 am Post subject: Re: WMB Flow design approach |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| niks29986 wrote: |
Requirement:
1. App will make a call to WMB.
2. WMB sends the data to third party A over MQ.
3. WMB receives response from A and validates and sends to third party B (MQ).
4. WMB receives data from B, does some validation, data trimming and sends the response to Mobile APP. |
1. App makes a call to WMB
2. WMB stores enough session information to identify the specifc request in a database (or cache if you mean IIB not WMB)
3. WMB formats query and sends to A over MQ
4. WMB receives response, correlates with store & updates status in store if relevant, validates, sends to B over MQ
5. WMB receives response from B, does the validation, trims the data (and the Xmas tree), retrieves the session information from the store & replies to the mobile app.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
