aspose file tools*
The moose likes Websphere and the fly likes Suggestion/Design consideration & possible issues using JMX - MBean - Timer in WAS6.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Suggestion/Design consideration & possible issues using JMX - MBean - Timer in WAS6.1" Watch "Suggestion/Design consideration & possible issues using JMX - MBean - Timer in WAS6.1" New topic
Author

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

ms Uday
Greenhorn

Joined: Jul 06, 2010
Posts: 4
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
Greenhorn

Joined: Jul 06, 2010
Posts: 4
appreciate any suggestions/pointers
Jess Tong
Greenhorn

Joined: Nov 01, 2010
Posts: 8
Have you considered using Websphere extention - scheduler service? It gives you failover and container managed transaction.
 
 
subject: Suggestion/Design consideration & possible issues using JMX - MBean - Timer in WAS6.1