IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsireportdbparms command

Use the mqsireportdbparms command to list all parameters that are set for a specific broker.

Supported platforms

Windows
Linux and UNIX systems
z/OS®. Run this command by customizing and submitting BIPSDBP.

Purpose

You can use the mqsireportdbparms command to identify if parameters are set on a broker. If security credentials are set for the broker, 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 that use the following resources:

A CICSConnection configurable service
A data source name (DSN) that is accessed from a message flow
An EmailServer configurable service
An FtpServer configurable service
An IMSConnect configurable service
A JDBCProvider configurable service
A JMS or JNDI resource, for example a JMSProviders configurable service
Kerberos Key Distribution Center (KDC) client credentials for SOAPRequest nodes with a WS-Security policy set and bindings that specify Kerberos
Lightweight Directory Access Protocol (LDAP) bind credentials for the broker's security manager
An SMTP configurable service
The broker keystore password
An account name, with a user name and password, for the WebSphere® Adapters
A WebSphere Service Registry and Repository (WSRR) configurable service
A WXSServer configurable service
SOAPRequest nodes

You can also return what security credentials are set on a broker, and identify if you have the correct password; see Checking the security credentials that are used by an integration node.

Syntax


>>-mqsireportdbparms--BrokerName-------------------------------->

>--+--------------------------------------------------------------+-><
   '- -n--ResourceName--+- -u--UserId-- -p--Password------------+-'   
                        +- -i--SSHIdentityFile-- -r--Passphrase-+     
                        '- -------------------------------------'

Parameters

All parameters that can be set by using the mqsisetdbparms command, see mqsisetdbparms command.

Authorization

For information about platform-specific authorizations, see the following topics:

If you have enabled broker administration security, you must also set up the authority detailed in Tasks and authorizations for administration security.

Ensure that the registry is appropriately secured to prevent unauthorized access.

Examples

Checking whether there are security credentials associated with resources

The following example shows the use of the command to see whether there are associated security credentials with a specific resource:

mqsireportdbparms broker_name -n ftp::server

The command returns any associated security credentials for the specified resource. If there are no credentials that are set, then a warning is displayed.

You can also check whether security credentials are associated with any resources of a specific type:

mqsireportdbparms broker_name -n ftp

The command returns if any of the resources of that type have associated security credentials. If there are no credentials that are set, then a warning is displayed.

Testing if a password for a resource is associated with a specific integration node.

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 IB9NODE -n SFTP::server -u user_id -i SSH_identity -r password

If you are testing a connected data source (that is not SFTP):

mqsireportdbparms IB9NODE -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 was last started.

an09156_.htm |

Last updated Friday, 21 July 2017