Channel exits

The channel exits available to the WebSphere MQ client environment on OS/2 Warp, UNIX systems, Windows, Windows 3.1, and Windows 95 are:

  • Send exit

  • Receive exit

  • Security exit

Channel exits are not available on DOS systems.

These exits are available at both the client and the server end of the channel. Exits are not available to your application if you are using the MQSERVER environment variable. Exits are explained in the WebSphere MQ Intercommunication manual.

The send and receive exit work together. There are several possible ways in which you can use them:

  • Splitting and reassembling a message

  • Compressing and decompressing data in a message

  • Encrypting and decrypting user data

  • Journaling each message sent and received

You can use the security exit to ensure that the WebSphere MQ client and server machines are correctly identified, as well as to control access to each machine.

 

Path to exits

This applies to WebSphere MQ clients on AIX, HP-UX, Linux, OS/2 Warp, Solaris, Windows 95, and Windows 98.

An mqs.ini file is added to your system during installation of the WebSphere MQ client. A default path for location of the channel exits on the client is defined in this file, using the stanza: 

  ClientExitPath:
    ExitsDefaultPath=<defaultprefix>/exits

Where <defaultprefix> is the value defined for your system in the DefaultPrefix stanza of the mqs.ini file.

On Windows 2000, Windows NT, and Windows XP, this stanza is added to the Registry.

When a channel is initialized, after an MQCONN or MQCONNX call, the mqs.ini file, or Registry, is searched. The ClientExitPath stanza is read and any channel exits that are specified in the channel definition are loaded.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.