BIP0914E |
BIP1046E with MQ reason code 2059 |
Check that the Configuration Manager's
queue manager and listener are running, and that the correct port is specified
for the queue manager. (The WebSphere MQ documentation
describes the WebSphere MQ return codes.)
|
BIP0889E |
BIP1047E |
Check that the Configuration Manager is
running. Check the system event log to ensure that the Configuration Manager is
available for use, and correct any errors that are shown.
|
BIP0915E |
BIP1046E with MQ reason code 2035 |
Check that the Message Broker Toolkit local
user ID is created on the Configuration Manager system.
If it is not, create it.Check if the Message Broker Toolkit local
user ID that is created on the Configuration Manager system
is authorized to connect to the Configuration Manager's
queue manager. - Use the WebSphere MQ dspmqaut command
to determine what WebSphere MQ authorities the
user has.
- If necessary, add the Message Broker Toolkit local
user ID to the mqm group on the Configuration Manager system.
|
BIP0991E with BIP1711W specifying
that the user cannot view the Configuration Manager Proxy |
BIP1047E |
Add an access control list (ACL) entry to the Configuration Manager for
the user with the Message Broker Toolkit local user
ID. For example, if USERA connects to the Message Broker Toolkit on COMPUTERA,
which belongs to DOMAINA, and is trying to connect to Configuration Manager CMA:- USERA must exist as a user on the Configuration Manager system
and belong to the mqm group
- USERA could have one of the following ACL entries:
- To create an ACL entry for USERA to connect with full Configuration Manager Proxy authority from any computer or domain,
issue the following command:
mqsicreateaclentry CMA -u USERA -a -x F -p
- To create an ACL entry for USERA to connect with full Configuration Manager Proxy authority from COMPUTERA only,
issue the following command:
mqsicreateaclentry CMA -u USERA -m COMPUTERA -x F -p
- To create an ACL entry for USERA to connect with full Configuration Manager Proxy authority from DOMAINA only,
issue the following command:
mqsicreateaclentry CMA -u USERA -m DOMAINA -x F -p
If a domain name and computer name match, and an ACL entry specified
the -m parameter, connection from either the domain or
computer is acceptable because they are not considered to be different users.
ACLs are necessary for all connections to the Configuration Manager,
so the user who issues a command such as mqsideploy from
the command line must also have appropriate ACL entries. |