Previous Topic: Hand-Written .NET ClientsNext Topic: The 32K Limit


Server-to-Server Flows

In server-to-server flows, a CA Gen-generated .NET Server can invoke another CA Gen-generated .NET Server using the DCOM Communications Runtime. This runtime is used specifically to support server-to-server cooperative flows as .NET Remoting does not support distributed transactions. For simplicity, the CA Gen Workstation Toolset does not call out the DCOM Communications Runtime separately. Rather, the CA Gen displays only .NET Remoting but use DCOM when appropriate.

Note: CA Gen DCOM Cooperative Flow cannot be used on client-to-server flows. Also note that server-to-server flows may not pass easily through the firewall.

The calling CA Gen .NET Server can be in the same machine as the target CA Gen .NET Server, or it can be located elsewhere on the network (as supported by the .NET Framework). The target CA Gen .NET Server can start its own transaction context, or it can extend the transaction context of the calling CA Gen .NET Server as specified in the CA Gen model.

CA Gen-generated .NET Servers can invoke a CA Gen C or CA Gen COBOL servers using the CA Gen TCP/IP, Web Services, or MQSeries communications runtime.

Distributed transactions are not supported when servers are executing within different environments (TP systems).

Calling non-CA Gen-generated .NET Servers (services components) can be accomplished through External Action Blocks.