| Author |
Message
|
| sjensen |
 Posted: Fri Apr 08, 2005 12:43 am Post subject: mqsiservice and setting broker UUID |
 |
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
I believe it is possible to set the brokers UUID using mqservice but I can't seem to find the component name.
I think is should be something like
| Code: |
| mqsiservice <component_name> <-r UUID> <broker> |
but I am not sure and have not been able to locate any documentation.
Many thanks for all help
Stefan |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Apr 08, 2005 3:23 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Why do you want to do this?
AFAIK this will break the communication between broker and configmgr.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| JT |
| Posted: Fri Apr 08, 2005 6:22 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
Syntax:
mqsiservice [-v] [componentName [-r label=value]] [-m messageNumber [-c messageCatalog]]
Explanation:
Reports the component's product version and its locale. Allows a specific message from the message Catalog to be produced. Command Options
'v' is the product version information. 'componentName' is the name of the component to query for its registry data. 'r' (label=value) Sets the registry key 'label' to 'value', (label=) Sets the registry key 'label' to null, (label) deletes the registry key 'label'. The 'r' option flag is destructive; be sure to keep a backup. 'm' is a message number to output. 'c' is the name of the message catalog to use.
|
In your case, the componentName would be the name of the broker and I believe the label would be BrokerUUID.
But as Michael asked, why? Perhaps there's a better solution. |
|
| Back to top |
|
|
| _dave_ |
| Posted: Fri Apr 08, 2005 6:38 am Post subject: |
|
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
Location: IBM Hursley
|
mqsiservice is not intended to be used in the mainstream. It can be very destructive if used incorrectly and can make any of your WMQI components unusable.
It is normally only used when specifically requested by IBM service.
This is why you don't find any information regarding it in the manuals.
As MichaelDag says, changing a Broker UUID will most certainly break the link between
the Configuration Manager and the Broker.
Could you explain what the problem is and what you want to do? Perhaps we can help out  |
|
| Back to top |
|
|
| sjensen |
| Posted: Mon Apr 11, 2005 3:16 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
Sorry I've been unable to get on the net 
I was looking at this as a potential fail back solution after an upgrade and to satisfy my curiosity 
Looks like it might be the delte,recrete the broker and redeploy all the flows.
Thanks
Stefan |
|
| Back to top |
|
|
| shra_k |
| Posted: Fri Apr 15, 2005 3:14 am Post subject: |
|
|
Apprentice
Joined: 30 Dec 2002
Posts: 37
|
Well, it is not possible to set the broker UUID using any commands , this is allocated by the configmgr and is communicated to the broker when the first deploy is done to the new broker.
Inorder to maintain consistency between the configmgr and broker, users are not allowed to change this unique value that is generated.
All communication identification between the broker and configmgr is not done using the broker lable/name but using the UUID. |
|
| Back to top |
|
|
| Lillian |
| Posted: Tue Jul 26, 2005 2:00 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
for DRP purposes we are building dedicated servers to be be backups for the current. in the restore procedure we use the db2 dabase backups of both the config and the broker.
will this command work to ensure that the registry entries and db2 entries are in sync ie to ensure that the Broker uuid in the registry on config is the same as in the tables?
Regards
Lillian |
|
| Back to top |
|
|
| Lillian |
| Posted: Tue Jul 26, 2005 3:07 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
| ps: we are still on wmqi 2.1 CSD08, broker on solaris. Will mqsiservice still work? |
|
| Back to top |
|
|
| sjensen |
| Posted: Tue Jul 26, 2005 3:16 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
mqsiservice will work for WMQI 2.1 on Solaris. I've used it to change the Broker UUID for testing. The Broker works fine with the new UUID but bear in mind it is not supported.
Cheers
Stefan |
|
| Back to top |
|
|
|
|
