Additional configuration steps if the HCL OneTest API user cannot be given queue create permission

As of release 9.2, HCL OneTest™ API 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. HCL OneTest API attempts to create these queues automatically when they are first accessed. If you do not allow HCL OneTest API 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 HCL OneTest API to create the queues. The RITDEFN job contains commands for creating the queues manually, if you prefer to predefine them. Note that the WebSphere® MQ exit on z/OS exit itself has not changed since release 9.1.1. Only the jobs within RIT.PROC were updated in HCL OneTest API release 9.2.1.1.

In the distributed WebSphere MQ environment, if you do not allow HCL OneTest API 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.

Distributed WebSphere MQ
  • Mirror queue recording: com.greenhat.intercept_LCK
  • Sift-and-pass-through stubbing: rit.divert.rules_LCK
  • Topology discovery: COM.GREENHAT.OBSERVATION_LCK
z/OS (Queue manager not in a queue sharing group)
  • 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)

All of the following queues must be created as shared queues:
  • 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.
Feedback