| Author |
Message
|
| meaton78 |
 Posted: Thu Oct 23, 2008 10:23 am Post subject: Select message flows not visible in Broker Toolkit |
 |
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
I have three flows that are not visible in the Broker Toolkit, however, I can see them running MQSILIST BROKER -e EG. Is there any way for me to force any kind of synchronization so I can manage those flows through the toolkit?
Broker Version 6.0
Toolkit version 6.0.2 |
|
| Back to top |
|
 |
| broker_new |
| Posted: Thu Oct 23, 2008 10:40 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
[mqsireportproperties <broker> -e <execution group> -o AllMessageFlows –a]
mqsireportproperties FADWBID1 -e CS_FLOWS -o AllMessageFlows -a
From the list (See image below), look for the entries with a matching message flow label, and then check the corresponding UUID’s.
If there is no entry for the flow shown in the configuration manager database this is the flow we should remove from the configuration manager database.
If there are entries shown on the broker that correspond with those in the configuration manager database, identify those on the broker that do not match the UUID from the configuration manager database. These are the ‘old’ duplicate entries that we want to delete from the broker.
Now that you have the message flow UUID that you want to remove, manually send a deployment message to the Broker, whilst the second is to manually delete the message flow row from the broker database.
It is possible to manually send a deployment message to the SYSTEM.BROKER.ADMIN.QUEUE of the Broker's queue manager with the following message data:
<Broker label="LHPIEV5" uuid="BrokerUUID" version="1">
<Change>
<ExecutionGroup label="EgLabel" uuid="EgUUID"/>
</Change>
<ExecutionGroup label="EgLabel" uuid="EgUUID">
<Delete>
<MessageFlow uuid="MsgFlowUUID"/>
</Delete>
</ExecutionGroup>
</Broker>
Replacing "BrokerUUID", "EgLabel", "EgUUID" and "MsgFlowUUID" with the real values. For example:
The message must have:
MQMessageFormat = MQSTR
MsgType of Request in the MQMD
Specify the ReplyQmgr and ReplyQ (which can be any queue).
This will safely remove the message flow from the database as would a normal deployment from the configuration manager.
The ReplyToQ can be checked to see the result of the configuration change request.
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| meaton78 |
| Posted: Fri Oct 24, 2008 4:45 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
| Thanks so much. I was able to remove the three flows by putting the messages to the Admin queue. |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Nov 17, 2008 7:42 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi , I tried to do the same, but it seems like I am missing something vital.
I sent this message to the admin queue. it didn't work.
I added start flags <broker> and <Executiongroup>
to the xml.
I used rfhutil tool to put in the message and thereby setting the the msgtype and the other things mentioned. But it did not work.
Is there something missing in this description?
_________________
Erik |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 17, 2008 7:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Just "Remove Deployed Children" using the Toolkit, and then redeploy the flows that should be running. |
|
| Back to top |
|
|
| Erik |
| Posted: Mon Nov 17, 2008 7:57 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
This is a quite complicated operation.
I'd prefer to find a way to just delete the ghost flows I have without touching other peoples work.
Any other ideas?
_________________
Erik |
|
| Back to top |
|
|
| meaton78 |
| Posted: Mon Nov 17, 2008 8:05 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
| Can you post the xml that you used? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 17, 2008 8:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Erik wrote: |
This is a quite complicated operation.
I'd prefer to find a way to just delete the ghost flows I have without touching other peoples work.
Any other ideas? |
If you mean with complicated using a hammer to swat a fly, yes.
However this is really easy.
You should have your bar files in version control and you should know which version of which bar file goes into which execution group....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Erik |
| Posted: Tue Nov 18, 2008 2:22 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
| meaton78 wrote: |
| Can you post the xml that you used? |
This is what I tried with, and I also set the message properties as stated above.
<Broker>
<Broker label="ANT_BROKER" uuid="658cc217-0e01-0000-0080-a89b72340e05" version="1">
<Change>
<ExecutionGroup label="GROUP A" uuid="08efc517-0e01-0000-0080-a89b72340e05"/>
</Change>
<ExecutionGroup>
<ExecutionGroup label="GROUP A" uuid="08efc517-0e01-0000-0080-a89b72340e05"/>
<Delete>
<MessageFlow uuid="0ff1979b-1d01-0000-0080-9458d93d1a6b"/>
</Delete>
</ExecutionGroup>
</Broker>
_________________
Erik |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 18, 2008 3:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remove the standalone broker tag in the 1st line
<Broker>
What you have is a malformed XML.
The next line with the attributes is sufficient to define the broker.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Erik |
| Posted: Tue Nov 18, 2008 4:21 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
| fjb_saper wrote: |
Remove the standalone broker tag in the 1st line
<Broker>
What you have is a malformed XML.
The next line with the attributes is sufficient to define the broker.
Have fun |
Done: but there is still something going wrong here, I must say that XML is not my best skill.
this is what I get in the backoutqueue.
Broker uuid="658cc217-0e01-0000-0080-a89b72340e05" label="ANT_BROKER" version="1">
<OverallCompletionCode result="failure">
<LogEntry catalog="BIPv600" number="2051">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
<Insert type="string" text="uuid"/>
</LogEntry>
<LogEntry catalog="BIPv600" number="2051">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
<Insert type="string" text="ExecutionGroup"/>
</LogEntry>
<LogEntry catalog="BIPv600" number="2087">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
</LogEntry>
</OverallCompletionCode>
</Broker>
_________________
Erik |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 18, 2008 4:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This is what you have:
Broker uuid="658cc217-0e01-0000-0080-a89b72340e05" label="ANT_BROKER" version="1">
This is what you need:
<Broker label="ANT_BROKER" uuid="658cc217-0e01-0000-0080-a89b72340e05" version="1">
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Erik |
| Posted: Tue Nov 18, 2008 4:43 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
I am so sorry, it seemed cut&pasted missing the first character.
Here is the answer I get in the ReplyToQueue.
This is the result of running the above XML without the standalone <Broker> tag.
<Broker uuid="658cc217-0e01-0000-0080-a89b72340e05" label="ANT_BROKER" version="1">
<OverallCompletionCode result="failure">
<LogEntry catalog="BIPv600" number="2051">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
<Insert type="string" text="uuid"/>
</LogEntry>
<LogEntry catalog="BIPv600" number="2051">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
<Insert type="string" text="ExecutionGroup"/>
</LogEntry>
<LogEntry catalog="BIPv600" number="2087">
<Insert type="string" text="ANT_BROKER"/>
<Insert type="string" text="658cc217-0e01-0000-0080-a89b72340e05"/>
</LogEntry>
</OverallCompletionCode>
</Broker>
_________________
Erik |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 18, 2008 4:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
use an XML validator: you had an extra <ExecutionGroup> in there just like you had an extra <Broker> in there and you cannot close the tag at the end of the second execution group as you have operations on its components... / children... I would seriously suggest you follow Jeff's Hammer method... and take an XML class.
<Broker label="ANT_BROKER" uuid="658cc217-0e01-0000-0080-a89b72340e05" version="1">
<Change>
<ExecutionGroup label="GROUP A" uuid="08efc517-0e01-0000-0080-a89b72340e05"/>
</Change>
<ExecutionGroup label="GROUP A" uuid="08efc517-0e01-0000-0080-a89b72340e05">
<Delete>
<MessageFlow uuid="0ff1979b-1d01-0000-0080-9458d93d1a6b"/>
</Delete>
</ExecutionGroup>
</Broker>
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 18, 2008 5:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You may be able to do this easier with the ConfigMgr Proxy API Exerciser, than by trying to misuse an undocumented private and unsupported XML interface to the Broker.
At no point is any of this an exercise in good systems management, unless you use presupplied and supported tools under a thought out, documented and repeatable procedure.
If you are having to do this very often, then you need to rethink your deployment procedures and deployment architecture such that it is NOT a complicated procedure to remove the children and redeploy an EG. |
|
| Back to top |
|
|
|
|
