| Author |
Message
|
| KIT_INC |
 Posted: Tue Jan 14, 2014 10:27 am Post subject: cloning a message borker |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
I am running WMB V7004 on Linux and I have a need to create a broker on a new machine with identical configuration.
PC1 running with QM1 and MB1 (exisitng)
PC2 running with QM2 and MB2 (new)
I read the mqsibackuproker and the mqsirestorebroker commands. But they only work if the Broker name is the same. I cannot have the same name for the new broker.
I tried to open up the zip file created by mqsibackuproker to see if I can change the broker name , zip it back and use it with the mqsirestorebroker, but I receive messages asking for password during the unzip. I understand that this is probably an unsupported way evening if I can change the zipped file.
What is the recommended way or if any one has found a way to do this instead of having the create and redeploy everything from scratch for the new broker. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 14, 2014 10:34 am Post subject: Re: cloning a message borker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| KIT_INC wrote: |
| What is the recommended way or if any one has found a way to do this instead of having the create and redeploy everything from scratch for the new broker. |
Simply retrieve the scripts that you employed to create QM1 & MB1 from your source control system, edit the names as needed (a global find and replace works well) and rerun them.
Of course, if you're got a general script and the names are parameters, you don't even need to change it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Tue Jan 14, 2014 10:57 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Everything was created before my time. I wish that there is such central repository. There are build books for every application deployed (somewhere in the shop) which probably contains DSN or config services required. The only thing that is easy to find is the bar files which are in source control. others are difficult. That's why I was hoping that backup and restore will help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 14, 2014 11:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| KIT_INC wrote: |
| That's why I was hoping that backup and restore will help. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 14, 2014 11:34 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You have an excellent opportunity to develop those very handy and frankly essential scripts that will build your broker from first principles.
Don't forget that you can use the various mqsi* utilties to get your existing configuration details that will help you out.
Then put them in BOTH your source control system AND in your toolbox.
Take your time and document them well and they will be very useful in the future.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
