Use the mqsilist command to list information about one or more integration nodes and their deployed resources.
>>-mqsilist-----------------------------------------------------> >--+-------------------------------------------------+----------> +- -a --------------------------------------------+ '-| brokerSpec |--+-----------------------------+-' '- -e --integrationServerName-' >--+-------------------+--+-----------------------+--+------+---> '- -d --detailLevel-' '- -k --applicationName-' '- -r -' >--+---------------------+--+-------------------+---------------> '- -v --traceFileName-' '- -w --timeoutSecs-' >--+-------------------+--------------------------------------->< '- -y --libraryName-' brokerSpec |--+- integrationNodeName ---------+----------------------------| +- -n --integrationNodeFileName-+ +- -i --ipAddress-- -p --port---+ '-+- -i --ipAddress-+-----------' '- -p --port------'
If you specify this command with no parameters, a summary is returned for integration nodes that are created in the current installation on this computer.
The current installation is associated with the command console that you opened (on Windows), or the mqsiprofile that is active (on Linux and UNIX systems).
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. 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 over a secured channel, you must specify the keystore and truststore password for the connection that is using the IBM_JAVA_OPTIONS environment variable. For more information, see Resolving problems when running commands.
Use this option for connections to remote integration nodes that do not require advanced connection parameters.
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 secured integration 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. 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.
If you specify this option on a computer on which you installed versions earlier than Version 7.0, only integration nodes are listed for those versions, if they exist. The level of detail corresponds to -d 0 for these earlier integration nodes, even if you specify (or allow to default) a different level of detail on this command. To view information about other components that you created in earlier versions, you must use the corresponding version of the mqsilist command.
You cannot use this option to list information about remote integration nodes and their resources.
While integration servers are starting, they might report a PID of 0.
The specified integration node must be active for message flow information to be returned.
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.
mqsilist -d 0
Message BIP8099I is generated.
mqsilist IBNODE -i tcp://hostname.example.com -p 7906
mqsilist IBNODE -e default -k myApplication
mqsilist IBNODE -e default -k myApplication -y myISLibrary
mqsilist IBNODE -e default -y shlib1
mqsilist IBNODE -e default -k myApplication -d2
mqsilist IBNODE -e default -k myApplication -r
mqsilist IBNODE
Message BIP1286I is generated.
mqsilist -a -r -d2
When an integration node is a multi-instance integration node in Standby mode, BIP1280I and BIP1292I are generated.
When an integration node is a multi-instance integration node in Active mode, BIP1280I, BIP1292I, and BIP1288I are generated.
When an integration node is a multi-instance integration node that is being started as a WebSphere® MQ service, BIP1296I and BIP1298I are generated.