Previous Topic: CFB ServerNext Topic: Client Manager

Anatomy of a DP Application › Communications and Middleware › Communications Runtime

Communications Runtime

Clients use a communications runtime to facilitate the processing of cooperative flow to a given target server execution environment. A server execution environment dictates, which transport protocols, a given client can use. Some server execution environments support only one transport protocol, while others support more than one.

CA Gen supports the following transport protocols corresponding to each server execution environment:

Server Execution Environment

Supported Transport Protocols

z/OS CICS

LU6.2

TCP/IP

MQSeries

ECI

z/OS IMS

LU6.2

TCP/IP

MQSeries

 

Windows Transaction Enabler

TCP/IP

Web Services

 

 

Windows .NET Component Services

.Net
Remoting

 

 

 

Windows MQSeries

MQSeries

 

 

 

UNIX Transaction Enabler

TCP/IP

*Web Services

 

 

UNIX Tuxedo

Tuxedo
ATMI

TCP/IP

 

 

UNIX MQSeries

MQSeries

 

 

 

Java EE EJB

Java RMI

 

 

 

Java EE EJB Web Services

Web Services

 

 

 

NonStop Pathway

RSC/MP

 

 

 

Note: * Transaction Enabler Web Services is not supported in Linux.

Some client execution environments limit which communications runtimes they offer.

Note: For more information about determining which communication runtime is offered for a particular client execution environment, see the current version of CA Gen Technical Requirements document.

For more information about how a CA Gen client selects a communications runtime, see Overriding Communications Support at Execution Time.

The following sections describe each type of communication runtime that CA Gen offers: