| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Deploying Topology and Broker Configuration |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Thu Sep 21, 2006 4:23 am Post subject: Deploying Topology and Broker Configuration |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Hey guys,
I have har time understanding deploy of topology. Topology, as the name suggest is a architecture or a graphical representation of how broker, topics, and eg are arran ged in the domain connection. How a topology is deployed?
Similarly, a could not understand what exactly is broker configuration deployment.
The doc says,
| Quote: |
Deploying a broker configuration
The broker configuration deployment overview explains when you might want to deploy a broker configuration
|
The broker configuration deployment overview says:
| Quote: |
Broker configuration deployment
A broker configuration deployment informs a broker of various configuration settings, including the list of execution groups, multicast and inter-broker settings.
When to use it
If you have modified multicast or inter-broker settings in the Message Brokers Toolkit or in a Configuration Manager Proxy application.
When not to use it
If you have used the mqsichangeproperties command to change publish/subscribe settings directly on the broker component. In this case, a broker configuration deployment overwrites any changes you have made to the settings.
If you are adding execution groups. In this case, the first time you deploy a broker archive (bar) file, the execution group is automatically initialized.
|
does it mean when we make changes in the broker then it has to redeployed. does it mean this?
what about topology deployment? is topology any object we can deploy? the reading doc does not help me to understand.
thanks in adavance for your help |
|
| Back to top |
|
 |
| jeevan |
| Posted: Thu Sep 21, 2006 7:14 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
[modified for clarity ]
Hey guys,
I have very hard time understanding a few terminologies in Message Broker. Two of them are deploy of topology and broker configuration.
Topology, as its name suggests, is an architecture or a graphical representation of how broker, topics, and execution groups are arranged in the domain connection. How a topology is deployed?
What is a topology deployment? Is topology an object? if not how can we deploy a topology ?
The reading red books and other doc does not help much in understanding this clearly.
Similarly, I could not understand what exactly is broker configuration deployment.
The doc says,
| Quote: |
Deploying a broker configuration
The broker configuration deployment overview explains when you might want to deploy a broker configuration
|
The broker configuration deployment overview says:
| Quote: |
Broker configuration deployment
A broker configuration deployment informs a broker of various configuration settings, including the list of execution groups, multicast and inter-broker settings.
When to use it
If you have modified multicast or inter-broker settings in the Message Brokers Toolkit or in a Configuration Manager Proxy application.
When not to use it
If you have used the mqsichangeproperties command to change publish/subscribe settings directly on the broker component. In this case, a broker configuration deployment overwrites any changes you have made to the settings. If you are adding execution groups. In this case, the first time you deploy a broker archive (bar) file, the execution group is automatically initialized.
|
Does it mean that when we make changes in the broker, it has to be redeployed?
Thanks in adavance for your help |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Sep 21, 2006 7:57 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hmm, a tricky one to answer completely. First, take a look at my longer comment regarding what a topology deploy is here: http://www.mqseries.net/phpBB2/viewtopic.php?t=21374
In a nutshell, topology deployment is used for deploying pubsub information ONLY. i.e. if you want to share subscriptions between brokers.
Outside of publish/subscribe, the only reason you would ever need to initiate a topology deployment is if you have attempted to delete a broker from the toolkit and as a result, there was a problem with the broker clearing itself up.
Broker configuration deployment is automatically initiated if you make any changes to the broker's configuration (for example, multicast parameters) in the tooling. You can also initiate it manually by using the Config Manager Proxy API or mqsideploy utility.
99.9% of the time a BAR file deployment is all that you'll ever need to care about, in v6, anway. In previous versions topology deployment was required a lot more. - it was a leftover artefact from the big-red-button days of the v2.1 Control Center.
Hope this helps. Let me know if you need any more information. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Sep 21, 2006 9:53 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Thank you very much for your detailed reply. It is very much useful.
I still have one more questinon regarding BROKER COINFIG DEPLOY. What exactly is broker configuration deploying in term of physical object ? I mean, I did not find any parameter in the deploy command such as broker config:
| Quote: |
Command Options [mqsideploy]
'-b brokerName' name of broker to deploy to.
'-e executionGroupName' name of execution group to deploy to.
'-bar BARFileName' deploy the specified Broker Archive file.
'-topology' deploy Topolougy configuration to all brokers.
'-topics' deploy Topics configuration to all brokers.
'-cancel' cancel all outstanding deploy requests.
'-complete' deploy complete data (default is delta).
'-rmMsgFlow msgFlowName' remove specified deployed message flow.
'-rmMsgSet msgSetName' remove specified deployed message set.
'-w timeoutValue' value in seconds to wait for the broker to reply to the deplo
y request.
'-r' read any log records associated with previous deploys.
'-connection cfgParameterFileName' Configuration Manager connection parameters
(.configmgr)
|
Does this mean that deploy broker config is deploying the broker itself? Or is there any object/configuration file to be deployed? |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Sep 22, 2006 3:00 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
When you do a broker configuration deploy, the Config Manager sends down a set of property values. There's no 'file' involved, it's just a message concocted by the Config Manager that is then sent to the broker.
Most broker properties that you can change in the toolkit are deployed in this way - such as the multicast parameters. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
