| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ESQL and DatabaseRetrieve Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gadzi |
 Posted: Fri Jun 04, 2010 1:57 am Post subject: ESQL and DatabaseRetrieve Node |
 |
|
Newbie
Joined: 04 Jun 2010
Posts: 4
|
Hi,
I need to pass the DataSourceName and QueryElements to a DatabaseRetrieve Node from within ESQL. Is there a way of doing this?
Thank you for your assistance |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Sat Jun 05, 2010 7:21 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Compute node to Database Retrieve node.
you can do everything in ComputeNode right, it could be much more easier
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Gadzi |
| Posted: Mon Jun 07, 2010 2:43 am Post subject: |
|
|
Newbie
Joined: 04 Jun 2010
Posts: 4
|
One would expect to get hold of the DatabaseRetrieve properties from within ESQL, since the DatabaseRetrieve node appears to be a child or variant of the Database node.
Once again, I ask is it possible to get a handle of the DatabaseRetrieve node properties within ESQL?
The info center does not have any leads in this regard, please assist  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 07, 2010 5:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I believe that it is not possible to do what you want to do with this node in the manner that you wish to do it.
There is sometimes a tendancy in message broker development to try and overgeneralize a solution - to make a "router subflow" for example that will take any set of inputs and make a routing decision based on a dynamic set of criteria when the actual business process will only ever have three different possible routes that it needs to take.
So unless you actually need to have more than, say, 10 different sets of Datasource and query Elements values - you're almost certainly attempting to overgeneralize your solution. If you have less than that, just put in the appropriate number of statically configured DatabaseRetrieve nodes and use flow logic to call the correct one. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jun 07, 2010 5:58 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You could try using mqsichangeproperties to declare these values to your flow through a JDBC provider Data Source Name. The DSN would be static in your flow, but you have the flexibility to point to a different data source at deployment time. So different environments (Sandbox, Dev, Test, Prod) would have access to the corresponding different DSNs, because you would modify your BAR file prior to deploying to each environment. Also check mqsicreateconfigurableservice command, that might give you some insight how to do what you want.
Another option is to create subflows, that each subflow has a single DatabaseRetrieve node. Say you have ten subflows, then route your request to one of the ten.
One thing you will soon realize: think in simple terms. Don't over complicate the solution. mqjeff is correct in his opinion about over generalizing leads to failure. The Broker takes many small baby steps quickly, similar to the tortoise. Taking fast large jumps like the hare will tyre you out. The tortoise always wins. Think in simple terms. Do many simple things instead of one large thing.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| 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
|
|
|
|
