Platform configurations and communication protocol considerations

This topic describes the different platform configurations to which the IMS resource adapter can be deployed, as well as the supported communication protocols specific to each platform.

The communication protocol you use depends on the platform configuration of WebSphere® Application Server and IMS™. The IMS resource adapter can be deployed to WebSphere Application Server for distributed platforms (AIX®, HP_UX, Linux, Linux for z/OS®, Solaris, or Windows®) and to WebSphere Application Server for z/OS. The IMS resource adapter, deployed in WebSphere Application Server, can communicate with IMS Connect using either the TCP/IP or Local Option communication protocol. Where TCP/IP uses sockets, Local Option provides non-socket access (an MVS™ program call) to IMS Connect from WebSphere Application Server for z/OS.

The following table describes the relationship between the different platform configurations, communication protocols, and global transaction support:

Platform of WebSphere Application Server with IMS resource adapter Supported communication protocol Global transaction (two-phase-commit) support
AIX TCP/IP Yes*
HP_UX TCP/IP Yes*
Linux TCP/IP Yes*
Linux for zSeries® and S/390® TCP/IP Yes*
Solaris TCP/IP Yes*
Windows TCP/IP Yes*
z/OS, OS/390® TCP/IP

Local Option

Yes*

Yes 

* Global transaction support with TCP/IP requires IMS Connect 2.1 or later.

Related concepts
Prerequisites for using the IMS resource adapter
Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.