| Author |
Message
|
| neeha_kashyap120 |
 Posted: Mon Apr 06, 2009 12:29 pm Post subject: Procedures or Subflow nodes? |
 |
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
Hi
We use some procedures that are common to all flows some of which involve database lookups and some dont. I wanted to checkout the possibility of using subflow node instead of the common procedures.
Are there any advantages of using subflows over common procedures if both are intended to do the same thing?
Thanks
Neeha
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
 |
| p.cradwick |
| Posted: Tue Apr 07, 2009 12:11 am Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Don't know about advantages, but I have a collection of Database subflows that I use repeatedly because it is easy to implement database retry scenarios within the subflow. This would be awkward to do using procedures. Also (by now) they are well tested!
Peter |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 07, 2009 12:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
At the risk of being obvious, it's really the right thing for the right task. I'm not aware of any obvious advantages / disadvantages of one or the other from a product perspective, and will stand correction there, but there are some tasks which are suited for subflows, others which are easier as procedures.
Purely personally, this site has all the auditing, logging and control functions implemented as sub-flows, opperated at a message level by their containing flow, with common message handling held as procedures.
I offer no comment as to the perfection or superiority of this arrangement, simple quoting it as an example. Other solutions are possible and may offer advantages in other situations.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Hari |
| Posted: Tue Apr 07, 2009 12:29 pm Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
I agree with Vitor....
Also, if you can achieve the same results with both of them, but if the subflow involves additional parsing et al....then i could take the procedure route.
Also I dont think you can make database calls using a stand alone procedure (with just the .esql in the broker schema).
My 2 cents. |
|
| Back to top |
|
|
| neeha_kashyap120 |
| Posted: Wed Apr 08, 2009 9:02 am Post subject: |
|
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
Thanks for all your replies.
Hari, what did you mean by "we cannot make database calls using ESQL alone"? I couldnt understand what you were referring to.
I only use ESQL statements to make these calls, is there a better way?
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Apr 08, 2009 9:15 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| You can use the database nodes also, but like you, I normally just use ESQL. |
|
| Back to top |
|
|
| Hari |
| Posted: Wed Apr 08, 2009 10:19 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
[quote="neeha_kashyap120"]
Hari, what did you mean by "we cannot make database calls using ESQL alone"? I couldnt understand what you were referring to.
[/quote]
I meant to say that you cannot make database calls if you only have an .esql file and no .msgflow files (no nodes defined). |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 08, 2009 10:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can call a procedure in an ESQL file that is kept in a project that only has ESQL files in it.
That procedure can call database functions.
The DSN will be taken from whatever Compute node is invoking the ESQL that is calling the procedure. Or the DSN can be specified in the ESQL procedure itself, per normal ESQL methods.
You can't call *any* thing in Broker, including database nodes, if you don't have at least one .msgflow file. |
|
| Back to top |
|
|
|
|
