If security is enabled for the queue manager, you must
enable certain authorities in the queue manager for the Rational® Integration Tester MQ
exit resources to access the Rational Integration Tester intercept
queue.
Recording authorities
To enable
Rational Integration Tester record
the required messages in the queue manager, the following permissions
must be enabled in the queue manager.
Note: Before changing the queue
manager authorities, use the dmpmqaut command to
back up the existing queue manager authorities.
Table 1. MQ
recording authorities for RITUserName. The following
permissions are required for the RITUserName user to record the messages
in the queue manager.Object |
Permissions |
Queue manager:
|
- connect
- inquire
- display
- create (namelist)
|
Namelist:
|
|
Namelist:
|
|
Queue:- SYSTEM.DEFAULT.MODEL.QUEUE
- transport_recording_model_queue_name
Note: The object is configured in the Model Queue field
on the Recording tab of the MQ physical transport.
|
|
Queue:- SYSTEM.ADMIN.COMMAND.QUEUE
|
|
Table 2. MQ recording authorities for PuttingApplicationUserName. The following permissions are required for the PuttingApplicationUserName
user to record the messages in the queue manager.Object |
Permissions |
Queue manager:
|
|
Namelist:
|
|
Queue:- AMQ.**
- AMQ.mirror_queue_prefix.**
Note: - The object is configured as a queue prefix in the Recording tab
of the MQ physical transport.
|
|
A sample script
SetExitRecordingAuthorities.bat that
configures the required permissions in the queue manager is available
in
<Rational Test Control Panel installation
directory>/tools/IBM/WebSphereMQ/dist/IBMWebSphereMQdist.zip location.
Topology discovery authorities
To enable
Rational Integration Tester perform
discovery for the queue manager, the following permissions must be
enabled in the queue manager.
Note: Before changing the queue manager
authorities, use the dmpmqaut command to back up
the existing queue manager authorities.
Table 3. MQ discovery
authorities for RITUserName. The following permissions
are required for the RITUserName user to observe the messages in the
queue manager.Object |
Permissions |
Queue manager:
|
- connect
- inquire
- display
- create (namelist)
|
Namelist:
|
|
Namelist:- COM.GREENHAT.OBSERVATION*
|
|
Queue:- SYSTEM.DEFAULT.MODEL.QUEUE
- transport_observation_model_ queue _name
Note: The object is configured in the Advanced tab
of the MQ observation point.
|
|
Queue:- SYSTEM.ADMIN.COMMAND.QUEUE
|
|
Table 4. MQ discovery authorities for PuttingApplicationUserName. The following permissions are required for the PuttingApplicationUserName
user to observe the messages in the queue manager.Object |
Permissions |
Queue manager:
|
|
Namelist:- COM.GREENHAT.OBSERVATION*
|
|
Queue:- AMQ.*.*
- AMQ.observation_QPrefix.*
Note: The object is configured as a queue prefix in the Advanced tab
of the MQ observation point.
|
|
A sample script
SetExitDiscoveryAuthorities.bat that
configures the required permissions in the queue manager is available
in
<Rational Test Control Panel installation
directory>/tools/IBM/WebSphereMQ/dist/IBMWebSphereMQdist.zip location.
Sift and Pass through with dynamic queue authorities
To
enable sift and pass through capability in the queue manager, the
following permissions must be enabled in the queue manager.
Note: Before
changing the queue manager authorities, use the dmpmqaut command
to back up the existing queue manager authorities.
Table 5. Sift
and Pass through with dynamic queue authorities for RITUserName. The following permissions are required for the RITUserName user
to enable the sift and pass through option in the queue manager.Object |
Permissions |
Queue manager:
|
- connect
- inquire
- display
- setall
- create (namelist)
|
Namelist:
|
|
Namelist:
|
|
Queue:
|
|
Queue:
|
|
Queue:- SYSTEM.DURABLE.MODEL.QUEUE
- diverted_queue_model_name
Note: Object is configured on the Stubbing tab
of the MQ physical transport with Use Sift & Pass Through
with Dynamic Queues option. This corresponds to the model
queue that is configured in the Diverted Queue section.
|
|
Queue:- SYSTEM.DEFAULT.MODEL.QUEUE
- stub_queue_model_name
Note: The object is configured on the Stubbing tab
of the MQ physical transport with Use Sift & Pass Through
with Dynamic Queues option. This corresponds to the model
queue that is configured in the Stub Queue section.
|
Note: Permission required on the SYSTEM.DEFAULT.MODEL.QUEUE for
specifying the custom queue.
|
Queue:- SYSTEM.ADMIN.COMMAND.QUEUE
|
|
Table 6. Sift and Pass through with dynamic queue authorities
for PuttingApplicationUserName. The following permissions
are required for the PuttingApplicationUserName user to enable the
sift and pass through option in the queue manager.Object |
Permissions |
Queue manager:queue_manager_name |
|
Namelist:
|
|
Queue:
|
|
Queue:
|
|
A sample script
SetSiftAndPassThroughWithDynamicQueuesAuthorities.bat that
configures the required permissions in the queue manager is available
in
IBMWebSphereMQdist.zip location.
Rational Integration Tester API
Exits are provided with Rational Test Control Panel.
For information, see Rational Integration Tester tool packages
Sift and Pass through with fixed queue authorities
To
enable sift and pass through capability in the queue manager, the
following permissions must be enabled in the queue manager.
Note: Before
changing the queue manager authorities, use the dmpmqaut command
to back up the existing queue manager authorities.
Table 7. Sift
and Pass through with fixed queue authorities for RITUserName. The following permissions are required for the RITUserName user
to enable the sift and pass through option in the queue manager.Object |
Permissions |
Queue manager:
|
- connect
- inquire
- display
- setall
- create (namelist)
|
Namelist:
|
|
Namelist:
|
|
Queue:
|
|
Queue:- stubbed_queue_namestubbed_queue_suffix
Note: The suffix is set in the Stub Queue section
on the Stubbing panel of the MQ physical transport
with the fixed queue option. For example: REQUEST.STUB
|
|
Queue:- stubbed_queue_namedivert_queue_suffix
Note: The suffix is set in the Divert Queue section
on the Stubbing panel of the MQ physical transport
with the fixed queue option. For example: REQUEST.DIVERT
|
|
Queue:reply_queue_name |
|
Queue:- SYSTEM.DEFAULT.MODEL.QUEUE
Note: Object is configured on the Stubbing tab
of the MQ physical transport with Use Sift & Pass Through
with Fixed Queues option. This corresponds to the model
queue that is configured in the Stub Queue section.
|
|
Queue:- SYSTEM.ADMIN.COMMAND.QUEUE
|
|
Table 8. Sift and Pass through with fixed queue authorities
for PuttingApplicationUserName. The following permissions
are required for the PuttingApplicationUserName user to enable the
sift and pass through option in the queue manager.Object |
Permissions |
Queue manager:
|
|
Queue:- stubbed_queue_namestubbed_queue_suffix
Note: The suffix is set in the Stub Queue section
on the Stubbing panel of the MQ physical transport
with the fixed queue option.
|
|
Queue:- stubbed_queue_namedivert_queue_suffix
Note: The suffix is set in the Divert Queue section
on the Stubbing panel of the MQ physical transport
with the fixed queue option.
|
|
Namelist:
|
|
A sample script
SetSiftAndPassThroughWithFixedQueuesAuthorities.bat that
configures the required permissions in the queue manager is available
in
IBMWebSphereMQdist.zip location.
Rational Integration Tester API
Exits are provided with Rational Test Control Panel.
For information, see Rational Integration Tester tool packages