mqsistop command - Windows, Linux, and AIX systems
Use the mqsistop command to stop the specified integration node, or integration servers that are managed by an integration node. The command can also be used to stop any components that are deployed to either an integration server that is managed by an integration node, or to an independent integration server.
Purpose
The mqsistop command stops an integration node that is running. It does not stop a queue manager that is associated with the integration node. To stop the associated queue manager, use the command line. For more information, see the topics on starting and stopping a queue manager in the IBM® MQ documentation.
Depending on which parameters you specify with the command, you can stop one, or all of the integration servers, applications or message flows under the integration node.
An integration node cannot be stopped by using the mqsistop command with the -n | --integration-node-file parameter. This syntax can be used only to stop components under the integration node, for example an integration server. To stop an integration node, use the mqsistop command with the integrationNodeName parameter.
Usage notes
- If your installation of IBM App Connect Enterprise is version 12.0.0.0 or later, you can run either the mqsistop command, or the equivalent ibmint stop command. For more information , see ibmint stop command.
Syntax
Some parameters have alternative long names; for example, -e and --integration-server are alternative parameter names of the integration server. The long names available are listed in the Parameters section.
Syntax for use with integration nodes
Syntax for use with independent integration servers
Parameters
- integrationNodeName
- (Required) Specify the name of the integration node that you want to stop.
On Linux® and AIX® systems, all names are case-sensitive.
- -s | --admin-host hostname -p | --admin-port port
- Specify the hostname and port of the independent integration server where the
components that you want to stop are deployed.
On Linux and AIX systems, all names are case-sensitive.
- -n | --integration-node-file filename
-
File containing integration node connection parameters (*.broker)
Other parameters:
- --https
- (Optional) Specifies that HTTPS will be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.
- --no-https
- (Optional) Specifies that HTTPS will not be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.
- --cacert cacertFile
- (Optional) Specifies the path to the certificate file (in either PEM, P12, or JKS format) to be
used to verify the integration node or server. If no cacert file is specified and default admin-ssl
is enabled, the cacert file defaults to the default pem file for admin-ssl.
- The --cacert parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --cacert when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
- The --cacert parameter can be set only if the
--admin-host parameter is specified without a URI, or if a URI is specified
that starts with
ssl://.
- --cacert-password cacertPassword
- (Optional) The password for password-protected cacert files.
- The --cacert-password parameter is valid only if HTTPS is used for the connection and if the --cacert parameter has been set. You cannot set it together with the --no-https parameter.
- The --cacert-password parameter can be set only if the
--admin-host parameter is specified without a URI, or if a URI is specified
that starts with
ssl://.
- --insecure
- (Optional) Specifies that the certificate that is returned by the integration node or server
will not be verified.
- The --insecure parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --insecure when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
- The --insecure parameter can be set only if the
--admin-host parameter is specified without a URI, or if a URI is specified
that starts with
ssl://.
- -e | --integration-server integration server name
- (Optional) Specify the name of the integration server that you want to stop.
On Linux and AIX systems, all names are case-sensitive.
- --all-integration-servers
-
(Optional) Indicates all integration servers under the specified integration node.
- -k | --application application name
-
(Optional) Name of an application that is deployed to the specified integration server.
- --all-applications
-
(Optional) Indicates all applications that are deployed to the specified integration server.
- -y | --librarylibrary
-
(Optional) Static library name.
- -f | --flow messageflow
-
(Optional) message flow name.
- --all-flows
-
(Optional) Indicates all message flows.
- -w |--timeout-seconds timeoutSeconds
-
(Optional) The number of seconds before the action is aborted.
- --immediate
-
(Optional) Indicates to the integration node to shut down immediately. Specify this flag only if you previously tried, and failed, to stop the integration node in a controlled fashion by using the mqsistop command without the --immediate flag.
- --detail-level
- This parameter controls the detail level of response messages.
- 0 = display summary information
- 1 = display standard information (default)
- 2 = display detailed information
Responses
- BIP8012 Unable to connect to system components.
- BIP8013 Component does not exist.
- BIP8016 Component cannot be stopped.
- BIP8030 Unable to modify user privileges.
- BIP8071 Command successfully completed
Examples
mqsistop IBNODEmqsistop INODE -e intServermqsistop INODE --all-integration-serversmqsistop INODE -e intServer -k testAppmqsistop INODE -e intServer -k testApp -f testFlowmqsistop --admin-host localhost --admin-port 7600 --application testAppmqsistop --admin-host localhost --admin-port 7600 --application testApp --flow testFlow