| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timer configurable service |
« View previous topic :: View next topic » |
| Author |
Message
|
| Esa |
 Posted: Fri Dec 02, 2011 4:29 am Post subject: Timer configurable service |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Hello,
Timer configurable service seems to be a (very humble) step towards job control within message broker. Currently it can be used for controlling the queues used for communication between TimeOutControl and TimeoutNotification nodes, for example if they run on separate brokers. You can also override the timeout value sent by the TimeoutControl node.
I would like to have the configurable service to be able to override all the fields in the timeout request message. to refresh your memory, here is the example timeout request message from InfoCenter:
| Quote: |
<TimeoutRequest>
<Action>SET</Action>
<Identifier>TenTimes</Identifier>
<StartDate>TODAY</StartDate>
<StartTime>NOW</StartTime>
<Interval>10</Interval>
<Count>10</Count>
<IgnoreMissed>TRUE</IgnoreMissed>
<AllowOverwrite>TRUE</AllowOverwrite>
</TimeoutRequest> |
In fact, I would like to be able to configure if the TimeoutNotification node should fetch the request message from the communication queue or from a configurable service. Because the TimeoutNotification node cannot listen to a configurable service the way it is listening to the communication queue now, that would require a separate listener and a notification mechanism that would kick when the excution group starts or when a configurable service has changed. But isn't that exactly what we have been promised for configurable services in V8?
I know this is a controversial subject, but what do you think? Could that be a good enough alternative for cron?
I'm expecting some educated comments from the usual suspects... |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Dec 02, 2011 4:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It wouldn't require a notification method when the EG starts. The configurable services are read at EG startup time, so it's merely a matter of taking action at that point rather than any significant extra code change.
The difficultly is that configurable services are slightly mis-named (in the same way that connectionURLFormat is slightly mis-named).
They're not really "Services". They're really just configuration entries. So they really should be considered "configuraTION services" rather than "ConfigurABLE SERVICES".
So what you really want is a Timeout service that is capable of making events occur when it fires, at least one of those events being a message to a Broker node. |
|
| Back to top |
|
|
| Esa |
| Posted: Fri Dec 02, 2011 5:15 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqjeff wrote: |
"
So what you really want is a Timeout service that is capable of making events occur when it fires, at least one of those events being a message to a Broker node. |
Jeff, I see what you mean. That service would not be just a container of configurations as current "configurable services" but a real service that is active in making things happen.
It seems I must rethink my scenario. Unless somebody else does it for me. |
|
| 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
|
|
|
|
