User exits, API exits, and IBM MQ installable services

This topic contains links to information about using and developing these programs.

For an introduction to how we can use user exits, API exits, and installable services to extend queue manager facilities, see Extending queue manager facilities.

For information on writing and compiling exits and installable services, see the subtopics.

• Writing exits and installable services on UNIX, Linux and Windows
  We can write and compile exits without linking to any IBM MQ libraries on UNIX, Linux and Windows.
• Installable services and components for UNIX, Linux and Windows
  This section introduces the installable services and the functions and components associated with them. The interface to these functions is documented so that you, or software vendors, can supply components.
• Installable services and components on IBM i
  Use this information to learn about the installable services and the functions and components associated with them. The interface to these functions is documented so that you, or software vendors, can supply components.
• Writing and compiling API exits on Multiplatforms
  API exits let you write code that changes the behavior of IBM MQ API calls, such as MQPUT and MQGET, and then insert that code immediately before or immediately after those calls.
• Channel-exit programs for messaging channels
  This collection of topics contains information about IBM MQ channel-exit programs for messaging channels.
• Writing data-conversion exits
  This collection of topics contains information about how to write data-conversion exits.
• Referencing connection definitions using a pre-connect exit from a repository
  IBM MQ MQI clients can be configured to look up a repository to obtain connection definitions using a pre-connect exit library.
• Writing and compiling publish exits
  We can configure a publish exit at the queue manager to change the contents of a published message before it is received by subscribers. We can also change the message header, or not deliver the message to a subscription.
• Writing and compiling cluster workload exits
  Write a cluster workload exit program to customize the workload management of clusters. We might take the cost of using a channel at different times of day, or message content, into account when routing messages. These are factors that are not considered by the standard workload management algorithm.

Parent topic: Developing MQI applications with IBM MQ

Related information

• Channel-exit programs for MQI channels
• API exit reference
• Installable services interface reference information
• Installable services interface reference information on IBM i