|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
mqsideploy.exe vs mqsideploy.bat |
« View previous topic :: View next topic » |
Author |
Message
|
murdeep |
Posted: Wed May 19, 2010 10:32 am Post subject: mqsideploy.exe vs mqsideploy.bat |
|
|
Master
Joined: 03 Nov 2004 Posts: 211
|
Anyone ever notice that the parms of mqsideploy.exe and mqsideploy.bat are not in sync? Notice the -d and -rm and many others.
WTF IBM?
====>
C:\WINDOWS\system32>mqsideploy.exe
BIP8841I: Deploys publish/subscribe neighbors, topics, or BAR file configuration data to the specified brokers.
Syntax 1 (deploy publish/subscribe neighbors):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -l [-m] [-w timeoutValue] [-v traceFileName
]
Syntax 2 (deploy topics hierarchy):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -t [-m] [-w timeoutValue] [-v traceFileName
]
Syntax 3 (deploy BAR file):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -b brokerName -e executionGroupName -a BARF
ileName [-m] [-w timeoutValue] [-v traceFileName]
Syntax 4 (deploy broker configuration):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -b brokerName [-w timeoutValue] [-v traceFi
leName]
Syntax 5 (remove previously deployed objects):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -b brokerName -e executionGroupName -d depl
oyedObjects [-w timeoutValue] [-v traceFileName]
Syntax 6 (cancel deployment):
mqsideploy (-n cfgParameterFileName | ([-i ipAddress] [-p port] [-q qMgr])) -c [-b brokerName] [-w timeoutValue] [-v tr
aceFileName]
Command options:
'-n cfgParameterFileName' Configuration Manager connection parameters (.configmgr)
'-i ipAddress' IP address or hostname of the Configuration Manager (default is "")
'-p port' port number of the Configuration Manager (default is 1414)
'-q queueManager' queue manager of the Configuration Manager (default is "")
'-b brokerName' name of broker to which to deploy
'-e executionGroupName' name of execution group to which to deploy
'-a BARFileName' deploy the specified Broker Archive file
'-d deployedObjects' remove a colon-separated list of deployed objects from the execution group
'-c' tells the Configuration Manager to stop waiting for broker responses to currently outstanding deploy requests, acr
oss the domain or on the specified broker. Use this flag with caution; any subsequent responses to cancelled deploys wil
l be ignored by the Configuration Manager, meaning that the status reported by the Configuration Manager may be incorrec
t.
'-l' deploy publish/subscribe neighbor (topology) configuration to all brokers
'-t' deploy topics hierarchy to all brokers
'-m' deploy complete information (default is to perform incremental deploy; changes to the deployed state)
'-w timeoutValue' value in seconds to wait for the broker to reply to the deploy request
'-v traceFileName' send verbose internal trace to the specified file.
<====
====>
C:\WINDOWS\system32>mqsideploy.bat
BIP1032I: Deploys pub/sub topology, topics or BAR file configuration data to the specified broker(s).
Syntax:
mqsideploy.bat (-connection cfgParameterFileName | (-i ipAddress -p port -q qMgr)) ((-b brokerName [([-e executionGroup
Name ((-bar BARFileName [-complete]) | -rm deployedObjects)]) | -cancel]) | (-topology [-complete]) | (-topics [-complet
e]) | -cancel) [-w timeoutValue] [-v traceFileName]
Command Options:
'-connection cfgParameterFileName' Configuration Manager connection parameters (.configmgr)
'-i ipAddress' ip address of Configuration Manager.
'-p port' port number of Configuration Manager.
'-q queueManager' queue manager of Configuration Manager.
'-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.
'-rm deployedObjects' colon separated list of deployed objects to remove from the execution group.
'-cancel' tells the Configuration Manager to stop waiting for broker responses to currently outstanding deploy requests
, across the domain or on the specified broker. Use this flag with caution; any subsequent responses to cancelled deploy
s will be ignored by the Configuration Manager, meaning that the status reported by the Configuration Manager may be inc
orrect.
'-topology' deploy pub/sub neighbor configuration to all brokers.
'-topics' deploy topics hierarchy to all brokers.
'-complete' clear existing data before deployment (vs. deploy incremental changes).
'-w timeoutValue' value in seconds to wait for responses.
'-v traceFileName' send verbose internal trace to the specified file.
<==== |
|
Back to top |
|
 |
mqmatt |
Posted: Wed May 19, 2010 11:52 pm Post subject: Re: mqsideploy.exe vs mqsideploy.bat |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
Indeed.
It's historical; the mqsideploy command originally came from a V2.1 supportpac called IC01.
Later, the command was brought into the main product and the command syntax was made consistent with the other commands. The older syntax is there for compatibility.
I would expect the old syntax to be removed sooner rather than later. If you're planning a move to V7, then you'll need to change your scripts anyway (to point to the broker rather than the CM.) |
|
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
|
|
|
|