Introduction › CA Gen Applications Before Java Generation

CA Gen Applications Before Java Generation

CA Gen has evolved from an application development tool that generates block mode and batch applications into one that generates client/server applications. Client/server applications are divided into the following elements:

• GUI—The graphical user interface.
• Client Procedure Steps—Responsible for handling the GUI events and performing some of the application logic, usually related to the flow of the application, and can include database accesses. Utilizing middleware, Client Procedure Steps invoke Server Procedure Steps to perform the balance of the application's functionality.
• Server Procedure Steps—Responsible for executing the bulk of the business logic and database accesses. Server Procedure Steps do not have a user interface. If allowed by the TP monitor, a Server Procedure Step can invoke other Server Procedure Steps.

For Windows-based GUI applications, the GUI and Client Procedure Steps are generated in the C language for execution on a Microsoft Windows platform. The Server Procedure Steps are generated in COBOL for execution on the IBM mainframe, or in the C language for execution on Microsoft Windows, selected Linux, UNIX, or NonStop platforms.

The GUI Clients can communicate with the servers using one of many communications runtimes, including:

• The CA Gen Client Manager
• TCP/IP
• Oracle Tuxedo (Tuxedo)
• WebSphere MQ
• ECI
• Web Services

Note:

• Not all servers support all the above communications methods.
• For more information about cooperative flows, see the Distributed Processing – Overview Guide.