ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMQI - 'Continuous' flow to export data from DB

Post new topic  Reply to topic
 WMQI - 'Continuous' flow to export data from DB « View previous topic :: View next topic » 
Author Message
Testo
PostPosted: Mon Jul 19, 2004 6:12 am    Post subject: WMQI - 'Continuous' flow to export data from DB Reply with quote

Centurion

Joined: 26 Feb 2003
Posts: 120
Location: Italy - Milan

We are wondering how we could use a message flow to continuously check on a DB for records with a certain status and in case they are found, we would start the 'real part' of the message flow, that is SELECT from DB, mapping and routing.

Obviously, this could be done with an external module (C++ or Java) but we are developing on W2K to deploy on OS390, so our scope is to avoid any external object from the broker: WMQI flows are particularly suitable with porting from one platform to another.

Any experience like this one? Any hints?

We know this is not the intended use for WMQI but any help would be appreciated.

Cheers,
Andrea Tedone
IBM IT Specialist
Back to top
View user's profile Send private message Send e-mail MSN Messenger
jefflowrey
PostPosted: Mon Jul 19, 2004 6:59 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's a bad idea to code a message flow to stay in a continuous loop. The execution group the flow was part of would not respond to the config mgr, therefore the broker would not respond.

You could write a separate program that would constantly dump messages on a queue, to cause the message flow to run. But that's the same as writing a separate program to poll the database.

You might instead look at a stored procedure in the database, that would be triggered on an insert or update. Depending on your database environment, this could put a message to a queue.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Testo
PostPosted: Mon Jul 19, 2004 7:09 am    Post subject: Reply with quote

Centurion

Joined: 26 Feb 2003
Posts: 120
Location: Italy - Milan

jefflowrey wrote:
It's a bad idea to code a message flow to stay in a continuous loop. The execution group the flow was part of would not respond to the config mgr, therefore the broker would not respond.



I know that a never ending loop inside a flow (e.g. a WHILE(TRUE) loop) is not feasible. My idea, in fact, is the following: when the system is started up every day, a message containing the 'today date' in a specific format is processed, and for any occurences, a check on the DB is performed. Then, in a certain manner that I'm not able to figure out, I should pause it for a configurable time (something like 10-15 seconds) then the message is written to the ouput queue that is defined to be exactly the input queue.

At the end of the story, it's similar to a loop but not exactly the same....

What do you think?! (I know it's still a bad idea but maybe more feasible?!)

Cheers,
Andrea
Back to top
View user's profile Send private message Send e-mail MSN Messenger
jefflowrey
PostPosted: Mon Jul 19, 2004 7:25 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It is more feasible... although still not a great idea.

There used to be an Timer node support pack. It might do the "pausing" that you want.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JLRowe
PostPosted: Mon Jul 19, 2004 7:31 am    Post subject: Reply with quote

Yatiri

Joined: 25 May 2002
Posts: 664
Location: South East London

A java input node may be suitable for the job, another alternative is the WBI JDBC adaptor which will quite happily poll a table for changes.
Back to top
View user's profile Send private message Send e-mail
JT
PostPosted: Mon Jul 19, 2004 8:44 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Just a thought, but have you looked at a database triggering mechasnim in conjunction with a messaging API.

We have a similar requirement, to invoke WBI message flows when a database event occurs. Rather than coding a JAVA "database listener", we're investigating the Oracle Advanced Queueing feature: Messaging Gateway.
Back to top
View user's profile Send private message
kirani
PostPosted: Mon Jul 19, 2004 10:35 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Testo wrote:
Then, in a certain manner that I'm not able to figure out, I should pause it for a configurable time (something like 10-15 seconds) ..


Configuration manager will not respond within this timeout period. Thus, it will affect your broker operations.
As others have suggested you can either write a plug-in Input node or use DB messaging feature to trigger your message flow.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMQI - 'Continuous' flow to export data from DB
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.