Use the mqsireportdbparms command to list all parameters that are set for an integration node or integration server.
You can use the mqsireportdbparms command to identify if parameters are set on an integration node or integration server. If security credentials are set for an integration node or integration server, you can check that a password that is associated with a user ID is what you expect by entering a password. The command returns if the input password is correct or not.
mqsireportdbparms can list the set parameters for integration nodes or integration servers that use the following resources:
You can run the mqsireportdbparms command while the integration node or integration server is running. If you changed a property for a resource on an integration node or integration server that is currently running, then the latest value is reported by the command with a warning to confirm that the change will not be in effect until the integration node or integration server is next restarted.
>>-mqsireportdbparms--+-integrationNodeName-+-------------------> '- -w --workDir-------' >--+--------------------------------------------------------------+->< '- -n--ResourceName--+- -u--UserId-- -p--Password------------+-' +- -i--SSHIdentityFile-- -r--Passphrase-+ '- -------------------------------------'
All parameters that can be set by using the mqsisetdbparms command, see mqsisetdbparms command.
The following examples show the reporting of security credentials at the integration server level. You can view security credentials for the integration node by specifying the name of an integration node instead of a work directory.
mqsireportdbparms -w workDir -n *
The command returns output similar to that shown in the following example:mqsireportdbparms -w c:\workdir\ACEServ1 -n *
BIP8180I: The Resource name 'jdbc::JDBC' has userID 'dbaccess'
BIP8180I: The Resource name 'kafka::KAFKA::integrationServer1' has userID 'kafkasrv1acc'
BIP8180I: The Resource name 'ldap::LDAP' has userID 'ldapaccess'
BIP8180I: The Resource name 'ldap::ldap.mydomain2.com' has userID 'ldapd2acc'
BIP8180I: The Resource name 'mq::othermq' has userID 'remmqacc'
BIP8180I: The Resource name 'mq::QMGR::MQMV8' has userID 'mq8acc'
BIP8180I: The Resource name 'mqtt::pubsubDefault' has userID 'mqttacc'
BIP8071I: Successful command completion.
mqsireportdbparms -w workDir -n mq::*
The command returns output similar to that shown in the following example:BIP8180I: The Resource name 'mq::othermq' has userID 'remmqacc'
BIP8180I: The Resource name 'mq::QMGR::MQMV8' has userID 'mq8acc'
mqsireportdbparms -w workDir -n mq::QMGR::MQ8
The command returns output similar to that shown in the following example:BIP8180I: The Resource name 'mq::QMGR::MQ8' has userID 'user001'
BIP8071I: Successful command completion
mqsireportdbparms -w workDir -n mq::QMGR::*
The command returns output similar to that shown in the following example:BIP8180I: The Resource name 'mq::QMGR::MQ8' has userID 'user001'
BIP8071I: Successful command completion
mqsireportdbparms -w workDir -n kafka::KAFKA::*
The command returns output similar to that shown in the following example:BIP8180I: The Resource name 'kakfa::KAKFA::integrationServer1' has userID 'kafka1'
mqsireportdbparms -w workDir -n ftp::server
The command returns any associated security credentials for the specified resource. If no credentials are set, then a warning is displayed.
mqsireportdbparms -w workDir -n ftp
The command returns if any of the resources of that type have associated security credentials. If no credentials are set, then a warning is displayed.
The following examples show the use of the command to test if a password is associated with a specific resource.
If you are testing a connected SFTP resource:
mqsireportdbparms -w workDir -n SFTP::server -u user_id -i SSH_identity -r password
If you are testing a connected data source (that is not SFTP):mqsireportdbparms -w workDir -n userdb -u user_id -p password
where userdb represents the connected resource, user_id represents the user ID and password represents the password that is being tested for the resource:
The command returns if the password is correct or incorrect, and if the password was changed since the integration node or integration server was last started.
mqsireportdbparms -w workDir -n salesforce::securityIdentity1 -u myUserID -p password
The command returns output similar to that shown in the following example:BIP8180I: The resource name 'salesforce::securityIdentity1' has userID 'myUserID'.
BIP8209I: The resource name 'salesforce::securityIdentity1' has client identity 'identity1'.
BIP8210I: The resource name 'salesforce::securityIdentity1' has client secret 'secret1'.
BIP8201I: The password you entered, 'password' for resource 'salesforce::securityIdentity1' and userId 'myUserID' is correct.
BIP8071I: Successful command completion.
mqsireportdbparms -w workDir -n loopback::securityIdentity1 -u myUserID -p password
The command returns output similar to that shown in the following example:BIP8180I: The resource name 'loopback::securityIdentity1' has userID 'myUserID'.
BIP8209I: The resource name 'loopback::securityIdentity1' has client identity 'identity1'.
BIP8210I: The resource name 'loopback::securityIdentity1' has client secret 'secret1'.
BIP8201I: The password you entered, 'password' for resource 'loopback::securityIdentity1' and userId 'myUserID' is correct.
BIP8071I: Successful command completion.
mqsireportdbparms -w workDir -n loopback::securityIdentity1 -u myUserID -p password
The command returns output similar to that shown in the following example:BIP8180I: The resource name 'loopback::securityIdentity1' has userID 'myUserID'.
BIP8209I: The resource name 'loopback::securityIdentity1' has client identity 'identity1'.
BIP8210I: The resource name 'loopback::securityIdentity1' has client secret 'secret1'.
BIP8201I: The password you entered, 'password' for resource 'loopback::securityIdentity1' and userId 'myUserID' is correct.
BIP8071I: Successful command completion.
mqsireportdbparms -w workDir -n kafka::KAFKA::integrationServer1 -u myKafkaUserID1 -p myKafkaPassword
The command returns output similar to that shown in the following example:BIP8180I: The resource name 'kafka::KAFKA::integrationServer1' has userID 'myKafkaUserID1'.
BIP8201I: The password you entered, 'myKafkaPassword' for resource 'kafka::KAFKA::integrationServer1' and userId 'myKafkaUserID1' is correct.
mqsireportdbparms -w workDir -n rest::myBasicAuthAndApiKey
The command returns output similar to that shown in the following example:$ mqsireportdbparms -w c:\workdir\ACEServ1 -n rest::myBasicAuthAndApiKey
BIP8180I: The resource name 'rest::myBasicAuthAndApiKey' has userID 'myUserID'.
BIP8214I: The resource name 'rest::myBasicAuthAndApiKey' has API key 'C664C588-885A-4F07-9390-9CD7A4F8A89F'.
For more information about connecting to secured REST APIs, see Configuring security credentials for connecting to a REST API.