| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Need Help |
« View previous topic :: View next topic » |
| Author |
Message
|
| TCV |
 Posted: Mon Sep 22, 2003 9:21 am Post subject: Need Help |
 |
|
Apprentice
Joined: 21 Aug 2003
Posts: 48
|
Hi ,
I have an application where users enter, delete, modify data using GUI and all the changes are stored in a Database. The application is running on an Oracle 9i Application server running on W2K. The changes to the DB have to be communicated to another Mainframe application running somewhere. We want to use MQSeries to communicate between the applications.
My idea of setting up the system is whenever there is a change to the DB on the sending side a trigger should trigger an application, which will gather the updated info from the DB and create a file and handover the file to MQ. From there the file gets transferred to the other end. The sending end I am not clear how this has to be done. Can some one please suggest me a process
Thanks
TC Venkatesan |
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue Sep 23, 2003 9:45 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Well, depending on the database you are using you can use a database trigger. I'm not a DBA, but you can configure your database such that whenever a row gets inserted/updated in a particular table, the database will run some application that you have written. The application can then find the particular row and create an MQ message.
Similarly, you could have a long-running application that simply polls the database for changes. For instance, you might have a column in the table that indicates whether the row has been processed yet. When the row gets inserted, the column is null. Your application queries the database every few seconds with a query like:
"select * from table where processed = null"
If it gets any rows back, it creates MQ messages for them, and then marks those rows as being processed.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Sep 23, 2003 11:42 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Couldn't you put your MQ message in the same unit of work as your database update? You could use a two phase commit and get both jobs done at the same time. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 24, 2003 6:41 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
There is also a product called Oracle Interconnect (by Oracle) which has an MQSeries adapter, that does all the stuff you are trying to do.
-------
Venny |
|
| Back to top |
|
|
| TCV |
| Posted: Wed Sep 24, 2003 7:04 am Post subject: Hi |
|
|
Apprentice
Joined: 21 Aug 2003
Posts: 48
|
Hi Vennela,
Could you tell me more about this Oracle Interconnect adapter for MQSeries and how it works.
Thanks
TCV |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 24, 2003 8:05 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
How it works?
It's simple. Whenever there is a DB update/insert/delete, the adapter puts a Message which has information on what table has been updated, whether it is a delete or an update, the record inserted or updated, etc. You can customize what you want in the message, XML or D3L (something I haven't used but it exists) etc.
The vice versa also works. When an XML message is put to a queue, the DB is updated.
We have been using it to send Data from an Oracle table on a Unix box to an AS/400 QMGR and vice versa. |
|
| 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
|
|
|
|
