Preparing for installation
In addition, before using the functionality contained in MVMA that pertains to IBM WebSphere MQ, you must complete some additional WebSphere MQ related setup tasks on each of the WebSphere MQ queue managers you plan to administer.
MVMA requires access to a server connection channel on each of the queue managers you plan to manage. It is your responsibility to create or provide this channel.
To define a server connection channel on IBM WebSphere MQ monitored queue managers
Because MVMA connects as an MQ client and uses an administrative userid, it is necessary to grant middleware administrators the appropriate permissions. In particular, it is necessary to define Channel Authentication (CHLAUTH) objects to permit the connection from MVMA.
An example of such an MQSC command is shown below. This specific command shown would allow connections from any IP address beginning with 192.169 and run those connections under the userid
Such commands should be executed from the MQSC console, although the specifics of this will vary by platform. For example, on Windows or Linux you would execute
runmqsc QMgrName where
QMgrName is the name of the target MQ queue manager. Then enter the MQSC commands in the displayed prompt. Consult the relevant IBM documentation for details.
SET CHLAUTH(MVMA.SVRCONN) TYPE(ADDRESSMAP) MCAUSER(usera) ADDRESS(192.169.*) AMQ8877: WebSphere MQ channel authentication record set. DIS CHLAUTH(MVMA.SVRCONN) ALL CHLAUTH(MVMA.SVRCONN) TYPE(ADDRESSMAP) DESCR( ) CUSTOM( ) ADDRESS(192.169.*) MCAUSER(USERA) USERSRC(MAP) CHCKCLNT(ASQMGR) ALTDATE(2015-05-15) ALTTIME(14.09.46)
The user ID specified in the MCAUSER field must be a member of the 'mqm' group on the platform on which the WebSphere MQ queue manager runs:
- If MVMA is installed on a Linux platform with the user ID mqm, 'MCAUSER' is not needed.
- In some cases, if the product is installed on Windows, a MCAUSER parameter such as MUSR_MQADMIN must be specified.