| Author |
Message
|
| techno_freak |
 Posted: Tue Jan 11, 2011 2:07 am Post subject: Identical Broker |
 |
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
Hey Guys,
Need a direction to accomplish task to create identical broker for existing one.
Which inlcude all broker properties, CM & EGs ,
How can i fetch broker properties. I hav tried mqsicreateproperties but doesn't work out.. let meknow the best way to do it. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Jan 11, 2011 2:32 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
IMHO, you are starting from the wrong point. I call this the 'County Mile Syndrome'
You are out in the countryside and you ask a local for directions. Theire answer starts with 'I wouldn't start htom here'.
You should have the broker build tightly controlled and scripted. Then creating a duplicate is just a matter of editing a few files and away you go.
The scripts should be stored in a tool sich as ClearCase, SVN or Git
This is all SOP in most professional broker shops.
_________________
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 |
|
|
| mqmatt |
| Posted: Tue Jan 11, 2011 4:04 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Do implement the practices smdavies99 mentions; it will make your life a lot easier.
However, from where you are today:
To take backups in V6.x, you need to take copies of the broker's system database, filesystem ($MQSI_WORKPATH) and registry ($MQSI_REGISTRY on UNIX platforms). For the ConfigMgr, you need to run the mqsibackupconfigmgr command.
To take backups in V7, you just need to run the mqsibackupbroker command. This copies everything you need into a zip file.
Additionally on all versions, if you care about transient state for aggregations, collections etc., then you need to also take backups of the SYSTEM.BROKER.* queues. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 11, 2011 6:40 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 11, 2011 6:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Hudson is a good automated Configurator, once you have the artifacts smdavies talks about stored in your source control system. |
But not entirely relevant to the OP's requirement for building a broker from scratch.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 11, 2011 7:18 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 11, 2011 7:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| It would be relevant if the OP would establish the artifacts as smdavies describes and addresses the shortfall in the build process. |
My points were:
1) The OP asked about creating a broker using an existing broker as a template not building & deploying bar files. Nothing was said about automating the process and, for an infrequently performed procedure like broker builds it's enough to have the scripts stored safely in a repository.
2) I know a number of sites rebuild their environments as part of the delivery process and I'm sure in the utopia in which you work they rebuild everything from the OS upwards for each push to development. Many other sites make do with pushing bar files out. So it's an assumption on your part that this broker build is part of a deploy.
It also sounds more like your crusade to make the world a better place than offering advice on the question asked. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 11, 2011 7:41 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Fair point Vitor.
To directly address the OP's query, the reason you cannot simply copy files from one place to the other to duplicate a Broker instance is that each Broker instance, each Execution Group instance, and each Message Flow instance is encoded at BAR deployment time with a UUID, which is part of the directory file structure naming convention. So trying to simply take Broker A, move the files and rename to some other name, Broker B, wouldn't exactly work. There is not an automated tool to do this, you cannot invoke mqsi utilities to help.
This leads into smadavies point: you can't (or shouldn't) get there from here. Your in the country, and before you can get to where you want to go, you need to be in the city.
Therefore, as I was attempting to suggest to the OP, you can improve the ability of your build practices to do what you want, if you create the artifacts smdavies describes, store them in a source control system, then put in place a firm but flexible build process that could potentially use a tool to help you automate the builds. As smdavies said, then its just a matter of applying a few BAR file overrides, or changing a few things in some config files, and you can create Broker B quickly and easily.
I hope this additional dialogue helps relate my suggestion better to the OP's original query and the first response.
Really, I mean no harm. I am friend and not foe. As BF2 commander would say, "Artillery YOUR area." Means take cover, incoming.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 11, 2011 8:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| There is not an automated tool to do this, you cannot invoke mqsi utilities to help. |
| mqmatt wrote: |
| To take backups in V7, you just need to run the mqsibackupbroker command. This copies everything you need into a zip file. |
 |
|
| Back to top |
|
|
| techno_freak |
| Posted: Tue Jan 11, 2011 7:56 pm Post subject: |
|
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
Hey Guys,
Thaks a ton for your reply..
Now i am in situation where i have to replicate broker(we are assuming only properties) on Mainframe. Plan whcih i have in mind is:-
- Create broker , CM and EG of same name on anothe MF.
- Fetch properties of existing broker and replicate it.
- I have list of EGs of existing broker which i can define and deploy bar files from cvs.
If this plan is not suffiecient to replicate broker, what are other points i have to consider.
Challenge is how can i fetch properties of broker do i need to use # mqsicreateproperties ... if yes what do i need to consider all objects to fetch from this command.
Regards
Techno Freak |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 12, 2011 1:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
... There is no "mqsicreateproperties" command.
There is an mqsireportproperties command.
But getting back to the earlier points.
If this is a *brand new* broker that you want to duplicate (and you have just said that it is, and that there are two brand new brokers!), then you should WRITE A SCRIPT to SET the properties on the first broker.
Then you can modify the script for the name of the second broker and run it on that one, and they will then be the same.
I repeat.
WRITE A SCRIPT. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 12, 2011 5:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| If this is a *brand new* broker that you want to duplicate (and you have just said that it is, and that there are two brand new brokers!), then you should WRITE A SCRIPT to SET the properties on the first broker. |
Consider this:
If you want to make a cake identical to the one you have, is it easier to investigate the cake & determine how much flour, butter and other ingredients were used, how long it was baked and so forth or is it easier to find the cook book?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 12, 2011 6:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| If this is a *brand new* broker that you want to duplicate (and you have just said that it is, and that there are two brand new brokers!), then you should WRITE A SCRIPT to SET the properties on the first broker. |
Consider this:
If you want to make a cake identical to the one you have, is it easier to investigate the cake & determine how much flour, butter and other ingredients were used, how long it was baked and so forth or is it easier to find the cook book? |
More importantly, if you want to make two new identical cakes, is it easier to bake one, and then investigate how you made it...
or follow the same recipe twice? |
|
| Back to top |
|
|
|
|
