| Author |
Message
|
| Adi3 |
 Posted: Fri Jan 12, 2007 1:05 pm Post subject: Queues under Execution Group |
 |
|
Novice
Joined: 19 Dec 2006
Posts: 15
|
I have set of message flows under execution group 'Test'. I created a new flow with input q 'IN' and deployed under the same.
When I tried to test the new flow by placing a message in q 'IN', I found some old flow is having a input q 'IN' and its getting executed.
I would like to know which flows are using q 'IN' under execution group 'Test' (by command line).
Please don't say open all the message flows and look at input node.  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jan 12, 2007 1:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can't, not really.
GET disable the queue, and look for errors in the broker log. That may tell you which flow it is.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jan 12, 2007 2:44 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I have seen a command mqisreportproperties (don't know the exact command anymore) somewhere (can't find the code right now...) where you can query the broker and drill down to nodes and find the input / output queues...
it's somewhere, just dig... (and have fun too)
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| pathipati |
| Posted: Fri Jan 12, 2007 6:49 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
Hi Michael,
I don't think mqsireportproperties will display queue level information.(I tried with most of the options)
Let us know if you find something  |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Jan 13, 2007 2:01 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I am sure I have seen queue information, does it report messageflow properties? (I haven't used the command myself, just saw the output...)
the group I worked in put all the queue information in promoted properties for ease of changing before deployment to a specific environment
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| pathipati |
| Posted: Sat Jan 13, 2007 3:39 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| I'll try and will post the results here.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Jan 13, 2007 6:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It might report promoted properties.
In terms of ease of changing before deployment to a specific environment... there's a new mqsiapplybaroverrides command in the 6.0.2.0 tooling.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Jan 13, 2007 8:14 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
yeah I saw that... but that works with change AAA to BBB principle, not change var1 to BBB or CCC or DDD
a bit disappointing...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Jan 13, 2007 8:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Michael Dag wrote: |
yeah I saw that... but that works with change AAA to BBB principle, not change var1 to BBB or CCC or DDD
a bit disappointing... |
I think it's a complicated problem. Or at least, more complicated than it looks.
In order to get any kind of real precision, like "change VAR1 to BBB on this node and VAR1 to CCC on that node", you have to use the URI values in the broker.xml...
BUT there isn't a clear and direct mapping between the nodes and properties that are visible in the Toolkit to the URI values that are in the broker.xml. For example, the HTTP Request node displays the request url property as something like "Web Service Destination" or some such - but the URI value is "flowname#nodename.URLIndicator" or similar.
And then there's the kind of situation where someone has one flow that needs to be deployed into multiple execution groups, where each EG or each Broker needs a different set of overrides applied....
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
