Use the mqsideploy command on z/OS® to make a deployment request to a local integration node.
>>-mqsideploy--| brokerSpec |-----------------------------------> >-- e= --integrationServerName--+- a= --BARFileName--+------+-+--> | '- m= -' | '- d= --deployedObjects-------' >--+-------------------+--+---------------------+-------------->< '- w= --timeoutSecs-' '- v= --traceFileName-' brokerSpec |--+- integrationNodeName ---------+----------------------------| +- n= --integrationNodeFileName-+ +- i= --ipAddress-- -p --port---+ '-+- i= --ipAddress-+-----------' '- p= --port------'
Synonym: dp
>>-+-deploy-+---------------------------------------------------> '-dp ----' >-- e=integrationServerName --+- a=BARFileName --+---------+-+--> | '- m=yes -' | '- d=deployedObjects ----------' >--+------------------+--+-------------------+----------------->< '- w=timeoutValue -' '- v=traceFileName -'
Use this option if multiple users want to connect to the same integration node, or if you are using advanced connection parameters such as SSL.
If you want to run a command that uses SSL to administer a remote broker over a secured channel, you must specify the keystore and truststore password for the connection using the IBM_JAVA_OPTIONS environment variable. See Resolving problems when running commands for further information.
If you are connecting to a remote integration node, you can additionally prefix integrationNodeName to explicitly set which integration node to connect to. You cannot use -n integrationNodeFileName in the same command.
Parameters that you omit assume default values:
If you want to connect to a remote host name, provide the security credentials as a URI in the following format: protocol://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.
The BAR file can be in a local or remote file system, if the user ID or the integration node that is running the command can access the file and read it.
You can specify objects of all types, but if you specify an ambiguous object name (for example, "top", when both "top.dictionary" and "top.cmf" are deployed to the same integration server), the entire command fails with the message BIP1089. In these circumstances, you must specify the fully qualified name of the objects to remove; for example, "top.dictionary:top.cmf".
The default operation is a delta or incremental deployment. Use the -m parameter to override the default operation and run a complete deployment.
You can set this parameter to a value in the range 1 - 2 145 336 164. If you do not provide a timeoutValue value, or you set a value less than 1 or greater than 2 145 336 164 is specified, an error is returned.
Set this parameter to a value greater than the sum of the configuration timeout parameters ConfigurationChangeTimeout and InternalConfigurationTimeout that you specified for the integration node, if you want to ensure that a response is received within the timeoutValue period. If you set a smaller value, the response returned might indicate that the state of the deploy request is unknown.
In previous versions of IBM® Integration Bus, you might have used the q= parameter for this command to define a connection to a queue manager. A queue manager connection is no longer used to connect to an integration node. The q= parameter is now deprecated, and is ignored if used. If you use the q= parameter, a BIP1922 warning is displayed.
The following examples show the use of the n= parameter to define the connection parameters for the integration node. If the integration node is on the local computer, you can specify it by name.
mqsideploy n= INODE1.broker e= default a= mybar.bar m= w= 600
mqsideploy n= INODE1.broker e= default d= top.cmf:bar.dictionary
F IB01NODE,dp e=default,a=flows.bar