Use the mqsideploy command on Windows, Linux, and UNIX systems to make a deployment request to an integration node or independent integration server.
Some parameters have alternative long names; for example: -p and --admin-port are alternative parameter names of the port number for the administration REST API. The long names available are listed in the Parameters section.
>>-mqsideploy--+-integrationNodeName-----------+----------------> +- -n --integrationNodeFileName-+ +- -i --ipAddress-- -p --port---+ '-+- -i --ipAddress-+-----------' '- -p --port------' >--+--------------------------------------------------------------+--> '- -e --integrationServerName--+- -a --BARFileName--+------+-+-' | '- -m -' | '- -d --deployedObjects-------' >--+-------------------+--+---------------------+-------------->< '- -w --timeoutSecs-' '- -v --traceFileName-'
>>-mqsideploy--+- -n --integrationNodeFileName-+----------------> '- -i --ipAddress-- -p --port---' >--+- -a --BARFileName--+------+-+--+-------------------+-------> | '- -m -' | '- -w --timeoutSecs-' '- -d --deployedObjects-------' >--+---------------------+------------------------------------->< '- -v --traceFileName-'
The file can be used to connect to a independent integration server if the connection details do not include a node name (integrationNodeName) and the host and port are for a independent integration server.
Use this option if multiple users want to connect to the same integration node or integration server, or if you are using advanced connection parameters such as SSL. To learn more about creating and using a .broker file, see Connecting to an integration node by creating a .broker file.
If you want to run a command that uses SSL to administer a remote integration node or integration server over a secured channel, you must specify the keystore and truststore password for the connection that is using the IBM_JAVA_OPTIONS environment variable.
To connect to a specific remote integration node by name, you can additionally prefix integrationNodeName. You cannot use -n integrationNodeFileName in the same command.
For an integration node, any parameters that you omit assume default values.
To connect to a independent integration server, the value is the host that you specified in the adminRestApiHost property in the server.conf.yaml configuration file for the integration server.
If you want to connect to a secured integration node or server as a specific user, provide the security credentials as a URI in the following format: tcp://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format.
To connect to a independent integration server, the value is the port that you set for the adminRestApiPort property in the server.conf.yaml configuration file; by default this is set to 7600.
Other parameters:
mqsideploy -i localhost -p 7601 -a C:\Users\IBM_ADMIN\IBM\ACET11\workspace\AppConnectToIIB\AppConnectToIIB.bar
You must also identify an integration server to deploy to; for example, by either specifying -i and -p parameters for a independent integration server, or by specifying an integration node and the -e parameter for an integration server.
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.
For an integration node, set this parameter to a value greater than the sum of the node configuration timeout parameters ConfigurationChangeTimeout and InternalConfigurationTimeout, 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.
mqsideploy -n b1.broker -e default -a mybar.bar -m -w 600
mqsideploy --integration-node-file b1.broker --integration-server default --bar-file mybar.bar --clear --timeout-seconds 600
mqsideploy -i my.host -p 7600 -a C:\workspace\MyApp\MyApp.bar -m -w 600
mqsideploy --admin-host my.host --admin-port 7600 --bar-file C:\workspace\MyApp\MyApp.bar --clear --timeout-seconds 600
mqsideploy -n b1.broker -e default -d top.cmf:dictionary.bar
mqsideploy --integration-node-file b1.broker --integration-server default --resources-to-delete top.cmf:dictionary.bar