|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
IIB9: Notify Consumers by API |
« View previous topic :: View next topic » |
Author |
Message
|
akil |
Posted: Thu Jul 30, 2015 1:29 am Post subject: IIB9: Notify Consumers by API |
|
|
 Partisan
Joined: 27 May 2014 Posts: 338 Location: Mumbai
|
Hi
Ive a scenario where at the completion of a flow, i need to notify customers.. the notification is to be done by calling API's published by these customers.
The customers expect XML payloads over HTTP(s) , but each has it's own format .
As new customers come, and they need to be notified (in their respective formats), it is important that the existing 'software units' don't change (at all) or with minimal changes.
It would be great if the deployment could be restricted to just the units for the new customer, and not the full package .
I've been thinking of 2 approaches
1. use an XSL to transform from a canonical format to the customer format, as new customers come, a new XSL needs to be added to the project, and deployed
2. use a mapping node , with a map for each customer. This requires the mapping file to be included in the project , and deployed
Both of the above approaches require the full app to be deployed,
Is there any other (easier) alternative? _________________ Regards |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jul 30, 2015 4:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can always redirect the "send a notification" logic to a separate flow.
If you need to make sure that the notification is completed before the original flow completes, you can use a synchronous call to the second flow.
Then you can package the customer notification logic into it's own bar file, and it's own application/service if you want. |
|
Back to top |
|
 |
akil |
Posted: Thu Jul 30, 2015 7:15 am Post subject: |
|
|
 Partisan
Joined: 27 May 2014 Posts: 338 Location: Mumbai
|
The response (success/failure) of the notification web-service call needs to be relayed back to the application , for tracking .. the calling app doesn't really care how long it takes, it just needs to know whether it was sent / not sent ..
When you say, call the flow, you mean MQ or some intermediate transport .. right? _________________ Regards |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jul 30, 2015 7:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
akil wrote: |
When you say, call the flow, you mean MQ or some intermediate transport .. right? |
Yes.
If you don't need to send the response to the calling application before you close the flow that's been called - i.e. you can send the success/failure message asynchronously, just drop it on a queue. |
|
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
|
|
|
|