| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Scheduling a call to a Web Service |
« View previous topic :: View next topic » |
| Author |
Message
|
| nelson |
 Posted: Fri Nov 07, 2014 12:23 pm Post subject: Scheduling a call to a Web Service |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi All,
Is there any way to schedule the calling of a service (exposed as a WS, MQ, etc... or in other protocol)? or what idea do you have to do this within IIB. For example, to start the flow (call the WS) once a month.
Thanks in advance. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Nov 07, 2014 12:26 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You mean based on some kind of Timeout Notification? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 07, 2014 12:27 pm Post subject: Re: Scheduling a call to a Web Service |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nelson wrote: |
| Is there any way to schedule the calling of a service (exposed as a WS, MQ, etc... or in other protocol)? or what idea do you have to do this within IIB. For example, to start the flow (call the WS) once a month. |
Yes. Write a flow that calls the service, and start the flow on the schedule you need.
Seriously.
Any scheduling tool (even the Windows built in one) can start & stop a flow through a command. If you want something a bit more sophisticated, put an MQInput node on the front of a flow and use amqsput to drop a trigger message on the required schedule. This allows you to pass parameter data if you need to, and manually rerun the flow if you need to.
Other scheduling solutions are undoubtably possible.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 07, 2014 12:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| You mean based on some kind of Timeout Notification? |
Do not attempt to run a timeout notification for a month and expect it to go off on schedule. Or on v7 or lower, at all. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nelson |
| Posted: Fri Nov 07, 2014 1:07 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| Vitor wrote: |
| mqjeff wrote: |
| You mean based on some kind of Timeout Notification? |
Do not attempt to run a timeout notification for a month and expect it to go off on schedule. Or on v7 or lower, at all. |
What do you mean by "expect it to go off on schedule" ? .What I have read is that these nodes work with a queue that stores a message and triggers the call to the TimeoutNotification node when scheduled... is there a problem with that behavior?
Thanks in advance for your comments. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 07, 2014 1:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nelson wrote: |
| What do you mean by "expect it to go off on schedule" ? .What I have read is that these nodes work with a queue that stores a message and triggers the call to the TimeoutNotification node when scheduled... is there a problem with that behavior? |
It's not "when scheduled", it's "when the timeout counter expires". Over the course of a month, one can expect that the broker (or parts of it) may be restarted (to change a setdbparms) or even brought down to allow for an OS level backup. Both of these will cause the "countdown" to stop while the broker is down. If it's a restart, no big. If it's a 3 hour outage every Sunday at 3am, in a month the "schedule" will be 12 hours out.
And as to it not starting, personal experience has shown that the notification service and/or the countdown against the queue can be adversely affected by such restarts, or indeed by running for more than about an hour. Clearly such problems could be addressed by a PMR but this site (because I write the rules) use broker's timer capability (and note it's in the Timer drawer on the Toolkit not the Scheduling drawer) to wait 10 seconds before retrying a web service or a database call.
For the kind of "every month at 6am on the 23rd" schedule, we use cron. Which goes off on schedule even if you've powered the box down cold in the meantime.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nelson |
| Posted: Fri Nov 07, 2014 1:30 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| Vitor wrote: |
| nelson wrote: |
| What do you mean by "expect it to go off on schedule" ? .What I have read is that these nodes work with a queue that stores a message and triggers the call to the TimeoutNotification node when scheduled... is there a problem with that behavior? |
It's not "when scheduled", it's "when the timeout counter expires". Over the course of a month, one can expect that the broker (or parts of it) may be restarted (to change a setdbparms) or even brought down to allow for an OS level backup. Both of these will cause the "countdown" to stop while the broker is down. If it's a restart, no big. If it's a 3 hour outage every Sunday at 3am, in a month the "schedule" will be 12 hours out.
And as to it not starting, personal experience has shown that the notification service and/or the countdown against the queue can be adversely affected by such restarts, or indeed by running for more than about an hour. Clearly such problems could be addressed by a PMR but this site (because I write the rules) use broker's timer capability (and note it's in the Timer drawer on the Toolkit not the Scheduling drawer) to wait 10 seconds before retrying a web service or a database call.
For the kind of "every month at 6am on the 23rd" schedule, we use cron. Which goes off on schedule even if you've powered the box down cold in the meantime. |
Understood. cron seems a good choice.
Vitor. Thanks a lot for your time. |
|
| 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
|
|
|
|
