| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timer nodes & Soap nodes in IIB |
« View previous topic :: View next topic » |
| Author |
Message
|
| vickas |
 Posted: Mon Jul 21, 2014 11:34 pm Post subject: Timer nodes & Soap nodes in IIB |
 |
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
HIe All ,
My requirement is to hit a service daily at a particular time , i.e at 12:00 noon . Here , i may recieve more than one request within the scheduled time.
so i have set 'AllowOverwrite' property to FALSE , to store the requests in a Queue (storage Q) .
Here is my flow Design
mqInput --> compute -->trycatch (try) -->timeoutcontrol
trycatch(catch) -->Queue
timeoutnotification-->MQget-->compute--> Soaprequestnode-->Mqoutput
trycatch(catch) -->Queue - purpose is to store the msgs if i recieve more than 1 request within the scheduled time. (acts as storage Q)
MqGet --> used to get all the msgs stored in it . a looping logic is written in the compute just a ahead of it in the flow.
this flow worked fine for many times but when i redeployed the flow again , the msgs were in the Storage Q itself , i mean to say , Timeout notification node is not being Trigged.
i redeployed the flow again deleting the existing generated bar and also restarted the EG as well , but i still dont find any change.
why has this happened ?? what might be the prob ??
what are the ones to be checked ? any problem with the Soap + Timer nodes combination ?? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jul 22, 2014 4:57 am Post subject: Re: Timer nodes & Soap nodes in IIB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vickas wrote: |
| any problem with the Soap + Timer nodes combination ?? |
IMHO (and I expect a storm of protest) Timer nodes are not ideal for this kind of scenario. Remember that the "timer" is effectively a countdown timer which can (as you've discovered) be reset or affected by a number of situations. If you're trying to wait for n seconds before doing something else (like checking for a response) they're great. If you're trying to wait the n seconds until 12 noon tomorrow, they're less so.
I prefer to build the flow you're describing as
MQInput -> Compute -> SOAPRequestnode -> MQOutput
and drop the "timeout notification" message with cron or similar (which is great at doing 12 noon without fail).
My 2 cents, other solutions are undoubtably possible and may be better, the best solution for your situation varies according to your exact requirements, etc, etc.
_________________
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
|
|
|
|
