When a message is put on a remote queue, the queue security that is performed by the local queue manager depends on how the remote queue is specified when it is opened. For example:
DEFINE QREMOTE(BANK7.CREDIT.REFERENCE) RNAME(CREDIT.SCORING.REQUEST) RQMNAME(BNK7) XMITQ(BANK1.TO.BANK7)
In this case, a profile for BANK7.CREDIT.REFERENCE, must be defined in the MQQUEUE class.
For example, the transmission queue BANK1.TO.BANK7 is defined on queue manager MQS1. An MQPUT1 request is then issued on MQS1 specifying ObjectName as BANK1.INTERBANK.TRANSFERS and an ObjectQMgrName of BANK1.TO.BANK7. In this case, the user performing the request must have access to BANK1.TO.BANK7.
When the message gets to the remote queue manager it might be subject to additional security processing. For more information, see the WebSphere MQ Intercommunication manual.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsav0498 |