Additional configuration steps if the Rational® Integration Tester user cannot be given queue create permission
As of version 9.2.0, Rational® Integration Tester uses queues that are named COM.GREENHAT.INTERCEPT_LCK, COM.GREENHAT.INTERCEPT.<QMGR>_LCK, RIT.DIVERT.RULES_LCK, and RIT.DIVERT.RULES.<QMGR>_LCK. Which of these queues is required depends on your environment. Rational® Integration Tester attempts to create these queues automatically when they are first accessed. If you do not allow Rational® Integration Tester to create queues, then you must predefine these queues.
On z/OS, the jobs within the RIT.PROC dataset contain sample statements for creating the required security profiles to allow Rational® Integration Tester to create the queues. The RITDEFN job contains commands for creating the queues manually, if you prefer to predefine them.
In the distributed WebSphere® MQ environment, if you do not allow Rational® Integration Tester to dynamically create queues, your system administrator must create the required locking queues in advance.
The queues that are used for locking depend on the WebSphere® MQ environment.
- Mirror queue recording: com.greenhat.intercept_LCK
- Sift-and-pass-through stubbing: rit.divert.rules_LCK
- Topology discovery: COM.GREENHAT.OBSERVATION_LCK
- Mirror queue recording: COM.GREENHAT.INTERCEPT_LCK
- Sift-and-pass-through stubbing: RIT.DIVERT.RULES_LCK
z/OS (Queue manager in a queue sharing group)
- Mirror queue recording: COM.GREENHAT.INTERCEPT_LCK, COM.GREENHAT.INTERCEPT.<QMGR>_LCK for each queue manager in the group
- Sift-and-pass-through stubbing: RIT.DIVERT.RULES.<QMGR>_LCK for each queue manager in the group
- Note: Topology discovery for WebSphere® MQ is not currently supported for WebSphere® MQ on z/OS.