Generating web transactions

Use EGL web transactions to migrate VisualAge® Generator web transactions to EGL.

The web transaction user interface is intended for migration from VisualAge® Generator only. It is possible to write new code using web transactions, but this code is not efficient.

EGL web transactions use the following configuration files:
  • Java™ runtime properties, as described in Overview of Java™ runtime properties
  • The linkage properties file, as described in "Web transaction linkage properties"
Web transaction applications involve two kinds of EGL parts:
  • EGL records with the VGUIRecord stereotype
  • EGL programs with the VGWebTransaction stereotype

EGL treats the VGUIRecord differently depending on whether you are generating code for Java™ or COBOL. When you generate a VGWebTransaction program for COBOL, the program automatically includes the information in the associated VGUIRecord, and displays the record as it would a form in Text UI. In Java™ generation, the VGUIRecord generates a .jsp file that becomes the user interface for the customer; that .jsp file is used to generate a Java™ bean on the server. Therefore, web transactions produce an actual web interface in Java™, but not in COBOL.

Deployment of web transaction applications involves setting up the gateway servlet, as noted in Gateway servlet parameters.