I have a question. Well currently, I have a Microsoft application. It is quite a large application composed of subsystems of ASP applications. For each ASP application subsystem, there is a scheduled .exe file running in the IIS in order to get data from the db and generate the updated html files for each subsystem. Each display page for each subsystem updates itself by using these updated html pages as hidden frames and transfer their content to the visible frames to reflect the changes. This is to not make the page refresh that obvious.
Now I am planning to convert this application into a Java application. But the first thing I'd like to do first is try to better it's performance. You see, each .exe file is run every 30 secs to get the updated info from the db and reflect the changes on the new html files. Problem is, the data in the db does not update very often so it would be quite inefficient to have the .exe file query the db over and over. Since the data provided should be in real time, we assigned it to query the db every 30 secs.
For it's conversion into java, my manager suggested me to use Websphere MQ for this. The plan is to have a separate system query the db early in the morning, store the data in memory. It could communicate with another existing system via sockets to be able to receive changes in the db. It would then sort each changes for each system then send messages to each subsystem if the particular change is for that system. It would use MQ for communicating with each subsystem. Each subsystem then would accept and filter messages for it so that it would be able to update their data only when there are changes...rather than query the db every 30 secs.
My problem is I do not know if this is really the best way to do it or if Websphere MQ is really needed in this type of situation. I have never used it yet, I only read a couple of overviews and introductions to it. If there are other alternatives in this setup, kindly tell me or if this is the best way to do it...can anyone give a headstart on how to implement it? and like how to they set this up exactly in websphere.....and I'll do the rest.
Sorry if im kinda asking for spoonfeeding here. Im a VB guy and I've just been working with Java for a few months now and they wanted me to learn a lot of new java and websphere technologies and the information I am absorbing is just overwhelming. I would appreciate any form of help.
The Websphere MQ approach, at least how I see it, would be one of using messages to let the data store tell YOU when its updated (using MDB's or some plain old server-side objects). A good idea, but I think a better approach would be Entity beans for your business tier. Since I'm not sure what exactly the probelm is at hand, from what I've read, this could be one possible solution as the persistence is managed by the container. WebSphere makes entity design fairly painless with the data perspective and wizards they use. (Can't say the debugging is painless though ... WebSphere wasn't the easiest to work with when things go wrong.. and they will!)
Hope that at least gives you a little insight or sparks some ideas.
^^ I haven't tried using Entity beans yet although I have read a lot about it. So you're saying that if I use Entity beans instead of storing data from db into memory...I won't be needing the use of messaging anymore?