Configuring a queue manager to use the API exit

To configure a queue manager to use the API exit, you can either use MQ Explorer (for Microsoft Windows and Linux systems) or modify the qm.ini file for the queue manager (for Microsoft Windows and Linux systems ).

For details, see Configuring a queue manager by using the WebSphere MQ Explorer and Configuring a queue manager by modifying the qm.ini file.
Note: You need to have read/write permissions to the IBM® WebSphere® MQ installation on the server that is hosting the queue manager that is to be configured. In addition, you must restart the queue manager after completing the procedure.

For externally hosted or managed WebSphere® MQ servers

When you cannot configure an HCL OneTest API MQ exit for your WebSphere® MQ server because the server is externally hosted or managed, the alternative is to use a local queue manager as a bridge:
  • The exit is installed on the local queue manager.
  • HCL OneTest API or HCL OneTest Virtualization sends requests to, and picks up responses from, the local queue manager.
  • The new local WebSphere® MQ queue manager forwards messages to, and receives replies from, the external server.

Although this process requires advanced WebSphere® MQ configuration, an experienced WebSphere® MQ administrator can set it up for you. For more information, see Queue name resolution.