MQSeries.net :: View topic

6thelement · Posted: Mon Feb 23, 2015 5:50 am Post subject:

Hello,
Here is the design problem I am trying to solve, my understanding on it and would need your insight on this.

1. Data gets inserted into DB application tables which triggers an event in event table. - DB trigger would do the work.

2. WMB polling on event table and gets notified about the event. - DB input node is the choice here. Read Event as a separate transaction.

3. WMB intercepts the event, extracts the information and calls the application table through a stored procedure/view - DB Input node(Build Message) would do this work. May be one additional compute node to do these steps from Build Message.

4. WMB receives the resultset, transforms the request to CSV format and puts it into a queue. - DB Input node(Build Message) would do this work. May be the same additional compute node of above point to do these steps from Build Message.

5. WMB needs to move the event from event table to an archive table through a stored procedure/view - May be calling from End Event?

WMB is on an AIX machine and ODBC file is updated with DSN connections to the Oracle DB.
Couple of more queries.
1. Why does the DB input node pallet is asking for a Database definition and its bit confusing on what JDBC driver to choose.
2. The complete infrastructure is running on a Load Balancing environment and so there is a chance that the same events can be picked up by different DB input nodes. Is there anyway we can do some record locking through ESQL where the events will not be processed by any other instance unless the lock is released by End Event. I understand that Read Event runs on a separate transaction then Build Message/End Event.

Is the problem sound familiar and is DB input node best way to handle in IIB?