Configure an extended transactional client

This collection of topics describes how to configure the extended transactional function for each category of transaction manager.

For each platform, the extended transactional client provides support for the following external transaction managers:

    XA-compliant transaction managers
    The extended transactional client provides the XA resource manager interface to support XA-compliant transaction managers such as CICS and Tuxedo.

    Microsoft Transaction Server (Windows systems only)
    On Windows systems only, the XA resource manager interface also supports Microsoft Transaction Server (MTS). The IBM MQ MTS support supplied with the extended transactional client provides the bridge between MTS and the XA resource manager interface.

    WebSphere Application Server
    Earlier versions of IBM WebSphere MQ supported WebSphere Application Server Version 4 or Version 5, and required you to carry out certain configuration tasks to use the extended transactional client. WebSphere Application Server Version 6 and later includes a IBM WebSphere MQ or IBM MQ messaging provider, so we do not need to use the extended transactional client.

  • Configure XA-compliant transaction managers
    First configure the IBM MQ base client, then configure the extended transactional function using the information in these topics.
  • Microsoft Transaction Server
    No additional configuration is required before we can use Microsoft Transaction Server (MTS) as a transaction manager. However, there are some points to note.

Parent topic: Configure connections between the server and client