Introduction › EJB Server Generation › Client-to-Server Flows

Client-to-Server Flows

Java Web Client and Java Proxy Clients

CA Gen Java Web Clients and CA Gen Java Proxy Clients communicate with CA Gen EJB Servers using the CA Gen Java RMI Communications Runtime. Rather than using the CA Gen Common Format Buffer, the CA Gen Java RMI Communications Runtime uses the data interchange and remote invocation mechanisms native to Java. Specifically, the runtime serializes the import and export views and invokes the target EJB using the Remote Method Invocation (RMI) feature of Java.

CA Gen Java Web Clients and CA Gen Java Proxy Clients communicate with CA Gen EJB Web Service Servers using the CA Gen Java Web Services Middleware Runtime. The CA Gen Java Web Services Middleware Runtime uses SOAP. Specifically, the runtime converts the import and export views as XML and communicates with the target EJB Web Service using HTTP.

ASP.NET Internet clients and .Net Proxy Clients

CA Gen ASP.NET Internet clients and .Net Proxy Clients communicate with CA Gen EJB Web Service Servers using the CA Gen .Net Web Services Middleware Runtime. The CA Gen .Net Web Services Middleware Runtime uses SOAP. Specifically, the runtime converts the import and export views as XML and communicates with the target EJB Web Service using HTTP.

MFC GUI Clients, C and COM Proxy Clients

The CA Gen C-language GUI Clients as well as the CA Gen C and COM Proxy Clients communicate with CA Gen EJB Web Service Servers using the CA Gen C Web Services Middleware Runtime. The CA Gen C Web Services Middleware Runtime uses SOAP. Specifically, the runtime converts the import and export views as XML and communicates with the target EJB Web Service using HTTP.

The CA Gen C-language GUI Clients as well as the CA Gen C and COM Proxy Clients cannot communicate directly with EJB Servers using Java RMI. Rather, these clients must use one of two facilities to convert their server requests to use the CA Gen Java RMI Communications Runtime. These facilities are defined below:

• CFB Server—A Java program that can run on any Java Platform in the network. Client systems connect to the CFB Server using the TCP/IP Communications Runtime. The CFB Server converts the client request into a Java RMI call. The CFB Server requires a local copy of the target EJB portable interface definition files.
• C to Java RMI Coopflow—Performs the conversion and Java RMI call on the client system. Accordingly, the client system must have a Java Virtual Machine installed and a local copy the target EJB portable interface definition files.

Note: For more information about cooperative flows, see the Distributed Processing – Overview Guide.

In client-to-server flows, the client does not pass its transaction context to the server. Therefore, CA Gen generated EJB Servers start its own transaction context.

Handcrafted Clients

Hand-written Java applications may interoperate with generated CA Gen EJB Servers without utilizing a CA Gen-generated Proxy. The interface of the CA Gen-generated EJB Server will perform all required data validations prior to executing the target procedure step.