| Author |
Message
|
| RatherBeGolfing |
 Posted: Mon Jan 22, 2007 6:14 am Post subject: |
 |
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
Hate to keep pleading ignorance here, but we're just beginning the exercise to migrate our v5 installation of wbimb to v6. We've run thru all the steps in the redbook to upgrade db2, apply fixpacks, migrate components, etc. This UUID issue is a brick wall to us.
Thank you Matt for the note about redeploying message flows - we'll definitely need to do that - this is in our DEV (sandbox) environment, so we still have the authorities to do that ourselves (sox) 
We have been a microsoft shop for so long, we don't even know how to spell Java here!! So, when you advise me to "...use the SetUUID method..." you may as well ask me to fly the space shuttle!!!
Any specific instructions you could give would be handy. In the meantime, we'll wrestle with the documentation and/or consider calling IBM consulting services. 
_________________
Cheers,
Larry
MQ Certifiable |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Jan 22, 2007 7:40 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
If you're unsure about what you're doing, then you shouldn't be using the setUUID() method at all.
If you follow the documented process for deploying and deleting resources (which isn't that difficult), then you should never run into UUID mismatch problems. But if you do, then it's a lot more foolproof to simply delete the affected object (in both the toolkit and the runtime) and recreate it. ...which isn't as drastic an operation as it sounds, as you should already have all of the resources you need to hand (message flows, dictionaries, even BAR files etc.).
-Matt |
|
| Back to top |
|
|
| pathipati |
| Posted: Mon Jan 22, 2007 8:29 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Quote: |
| Glad it worked for you, but do read the documentation for the setUUID() method. Importantly, any message flows that you had deployed to that broker will not be monitored by the Config Manager until you redeploy them. |
for me I haven't deployed to the broker before setting UUID, why bcaz that is brand new broker to which I was unable to connect using my ConfigMgr without setting UUID.. |
|
| Back to top |
|
|
| emileke |
| Posted: Fri Jan 26, 2007 12:32 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
How and where do u set the "setUUID() method"
_________________
Emile M Kearns |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Jan 26, 2007 4:44 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
It's part of the Config Manager Proxy; see the Java Programming APIs section of the broker's start menu.
My above comment holds. If the API needs explaining, you probably shouldn't use it; recreate your broker instead. |
|
| Back to top |
|
|
| emileke |
| Posted: Sun Jan 28, 2007 8:40 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
I actually used the API to delete the broker and it work so my problem is solved, thank you all who responded.
_________________
Emile M Kearns |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Mar 12, 2008 1:48 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
Use the API Proxy to "remove all traces of a previously deleted broker"
You can only do this with the API Proxy Exerciser...
Enjoy |
How do I find the UUID for a previously deleted broker?
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| emileke |
| Posted: Wed Mar 12, 2008 10:39 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
If you have setup the WMB logging , you will see an error in the mqsi log
_________________
Emile M Kearns |
|
| Back to top |
|
|
| rmah |
| Posted: Thu Mar 13, 2008 9:41 am Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| emileke wrote: |
| If you have setup the WMB logging , you will see an error in the mqsi log |
negative. when i try to deploy config. topology, nothing shows up in /var/log/messages or /var/mqsi/user.log. Only this via Toolkit:
BIP1520I: The Configuration Manager has initiated a deployment operation.
The Configuration Manager received a request to deploy configuration data and has consequently asked the following brokers to change their configuration: mqbroker_01 mqbroker_01
As you can see , there are 2 broker's with the same name. One is old which I'd like to delete from the config. manager repository...
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
|
|
