Suggestion/Design consideration & possible issues using JMX - MBean - Timer in WAS6.1

[ms Uday]

Hi All,

I am working on an app, the requirement is to continuously monitor a db table for changes and if it finds any, it has to pull data from table(s) , build an xml message and put in on a Websphere MQ and update some other table(stating message posted).

I am planning to use JMX MBean Timer to continuously monitor the DB table for changes and would like to get your Suggestion/opinion/Design consideration & possible issues on below...
using JMX - MBean - Timer in WAS6.1
What are the things to consider when deploying in WAS cluster..?
is there a way to have a singleton timer..?
any suggestions for failover situations..and suggested design patterns to be followed..

thanks in advance..and appreciate any suggestions/pointers

[ms Uday]

appreciate any suggestions/pointers

[Jess Tong]

Have you considered using Websphere extention - scheduler service? It gives you failover and container managed transaction.