Using CA Continuous Application Insight › Native MQ CAI › Configure the Native MQ CAI API Exit

Configure the Native MQ CAI API Exit

After you install the API exit, provide information such as the module and the entry point.

Follow these steps:

1. Go to WebSphere MQ Explorer or open the qm.ini configuration file.
2. Configure the queue manager to run an API exit.
   • Set the Name attribute to any descriptive name.
   • Set the Function attribute to EntryPoint. This value is case-sensitive.
   • Set the Module attribute to the API exit file that you installed (for example, /var/mqm/exits/iTKO_MQ_Pathfinder_linux).
   • If you want Native MQ CAI to generate log files, set the Data attribute to the directory where the log files are written.
3. Restart the queue manager.
4. Send a test message to a queue.
5. Browse the ITKO_PATHFINDER queue and verify that the test message was mirrored.

Example: qm.ini API Exit Configuration on AIX

Add the following lines to /var/mqm/qmgrs/[QueueManager]/qm.ini, where [QueueManager] is the name of the queue manager in your environment:

ApiExitLocal:
   Module=/var/mqm/exits64/iTKO_MQ_Pathfinder_aix
   Name=Pathfinder
   Sequence=100
   Function=EntryPoint

This example applies to an AIX system that has 64-bit kernel packages installed. If the system is a pure 32-bit, change the Module attribute to /var/mqm/exits/iTKO_MQ_Pathfinder_aix.

You could copy iTKO_MQ_Pathfinder_aix and iTKO_MQ_Pathfinder_aix_r into both /var/mqm/exits/ (32-bit libraries) and /var/mqm/exits64/ (64-bit libraries). Configure the Module attribute with a relative path such as Module=iTKO_MQ_Pathfinder_aix. This action enables WebSphere MQ to pick up the correct version of the libraries based on the default ClientExitPath attribute path that is defined in the global WebSphere MQ configuration file (/var/mqm/mqs.ini). The /var/mqm/mqs.ini file looks like the following example:

   DefaultPrefix=/var/mqm
ClientExitPath:
   ExitsDefaultPath=/var/mqm/exits
   ExitsDefaultPath64=/var/mqm/exits64