Platform configurations and communication protocol considerations

Depending on your platform configuration, different protocols are possible.

The communication protocol you use depends on the platform configuration of WebSphere® Application Server and IMS™. The IMS TM 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 TM Resource Adapter, deployed in WebSphere Application Server, can communicate with IMS Connect using either the TCP/IP or Local Option communication protocol. Whereas TCP/IP uses sockets, Local Option provides non-socket access (an MVS™ program call) to IMS Connect from WebSphere Application Server for z/OS.

If you want to use global transaction support for your IMS and WebSphere Application Server, see Two-phase commit prerequisites for more information. 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 

Related concepts
Prerequisites for using the IMS TM resource adapter

Feedback