Home

 

Platform support for extended transactional clients

WebSphere MQ extended transactional clients are available for all the platforms that support a base client, apart from Linux (POWER platform). Table 1 lists the supported external transaction managers for each platform.

Table 1. The supported external transaction managers for each extended transactional client platform

Extended transactional client platform	Supported external transaction managers
AIX	BEA Tuxedo, V8.1 TXSeries,  V5.1 WebSphere Application Server, V5.1 WebLogic, V8.1
HP-UX	BEA Tuxedo, V8.1 TXSeries,  V5.1 WebSphere Application Server, V5.1 WebLogic, V8.1
Linux (x86 platform)	BEA Tuxedo, V8.1 WebSphere Application Server, V5.1 WebLogic, V8.1
Linux (zSeries platform)	BEA Tuxedo, V8.1 WebSphere Application Server, V5.1
Solaris	BEA Tuxedo, V8.1 TXSeries,  V5.1 WebSphere Application Server, V5.1 WebLogic, V8.1
Windows systems	BEA Tuxedo, V8.1 TXSeries,  V5.1 WebSphere Application Server, V5.1 Microsoft transaction server (MTS)/COM+ WebLogic, V8.1

A client application that is using an extended transactional client can connect to a queue manager of the following WebSphere MQ V6.0 products only:

• WebSphere MQ for AIX

• WebSphere MQ for HP-UX

• WebSphere MQ for iSeries

• WebSphere MQ for Linux (x86 platform)

• WebSphere MQ for Linux (zSeries platform)

• WebSphere MQ for Solaris

• WebSphere MQ for Windows

• WebSphere MQ for z/OS

Even though there is no extended transactional client that runs on i5/OS or z/OS, a client application that is using an extended transactional client can still connect to a queue manager that runs on i5/OS or z/OS.

For each platform, the hardware and software requirements for the extended transactional client are the same as those for the WebSphere MQ base client. A programming language is supported by an extended transactional client if it is supported by the WebSphere MQ base client and by the transaction manager you are using.

Client applications that are written in Java and use WebSphere Application Server as the transaction manager can use only WebSphere MQ JMS to access the resources of a queue manager. This is because only WebSphere MQ JMS supports the Java Transaction API (JTA). To support WebSphere MQ JMS applications, a WebSphere MQ base client must include WebSphere MQ Java.

 

Home