Use the mqsilist command to list information about one or more integration nodes or integration servers, and their deployed resources.
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.
>>-mqsilist--+-------------------------------+------------------> +-integrationNodeName-----------+ +- -n --integrationNodeFileName-+ +- -i --ipAddress-- -p --port---+ '-+- -i --ipAddress-+-----------' '- -p --port------' >--+-----------------------------+--+------+--------------------> '- -e --integrationServerName-' '- -a -' >--+-------------------+--+-----------------------+--+------+---> '- -d --detailLevel-' '- -k --applicationName-' '- -r -' >--+---------------------+--+-------------------+---------------> '- -v --traceFileName-' '- -w --timeoutSecs-' >--+-------------------+--------------------------------------->< '- -y --libraryName-'
>>-mqsilist--+- -n --integrationNodeFileName-+--+------+--------> '- -i --ipAddress-- -p --port---' '- -a -' >--+-------------------+--+-----------------------+--+------+---> '- -d --detailLevel-' '- -k --applicationName-' '- -r -' >--+---------------------+--+-------------------+---------------> '- -v --traceFileName-' '- -w --timeoutSecs-' >--+-------------------+--------------------------------------->< '- -y --libraryName-'
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).
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:
You cannot use this option to list information about remote integration nodes and their resources.
The specified integration node must be active for message flow information to be returned.
In previous versions of IBM App Connect Enterprise, 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 INODE -i tcp://hostname.example.com -p 7906
mqsilist INODE --admin-host tcp://hostname.example.com --admin-port 7906
mqsilist -i my.host -p 7600
mqsilist --admin-host my.host --admin-port 7600
BIP1275I: Application 'AppConnectToIIB' on integration server 'ISIPL101' is running. BIP1275I: Application 'OnPremLogger' on integration server 'ISIPL101' is running. BIP1275I: Application 'Transformation_Map' on integration server 'ISIPL101' is running. BIP1877I: REST API 'CustomerDatabaseV1' on integration server 'ISIPL101' is running. BIP1877I: REST API 'LeadXML' on integration server 'ISIPL101' is running. BIP1877I: REST API 'LeadXML2ACoIC' on integration server 'ISIPL101' is running. BIP1875I: Service 'TemperatureConverter' on integration server 'ISIPL101' is running. BIP8071I: Successful command completion.
The following commands show examples of use for the default integration server of the integration node, IBNODE:
mqsilist INODE -e default -k myApplication
mqsilist INODE --integration-server default --application myApplication
mqsilist INODE -e default -k myApplication -y myISLibrary
mqsilist INODE --integration-server default --application myApplication --library myISLibrary
mqsilist INODE -e default -y shlib1
mqsilist INODE --integration-server default --library shlib1
mqsilist INODE -e default -k myApplication -d 2
mqsilist INODE --integration-server default --application myApplication --detail 2
mqsilist INODE -e default -k myApplication -r
mqsilist INODE --integration-server default --application myApplication --recursive
mqsilist INODE
Message BIP1286I is generated.