Welcome
Developing
Developing EGL applications
Enterprise Generation Language (EGL) is a programming language that you can use to focus on business problems instead of software technologies. Within the Rational® development environment, you can use EGL wizards and other tools to write complex applications with minimal effort.
EGL Generation Guide
The EGL Generation Guide covers the process of converting EGL code to Java™ or COBOL source code, including the processes and the files involved. This section is intended for a developer who will generate or deploy EGL applications.
Overview of Java™ generation
Preparing for external deployment
Deploying to a non-JEE environment
Setting up the TCP/IP listener for a called non-J2EE application

Overview
Getting started
Installing
Upgrading and migrating
EGL Code Accelerator for IBD
Developing
- Model driven development of EGL code
- Generating source code from UML models
  You can use transformations to create source code from a UML model. First you must create a transformation parameters file and then apply those parameters to a model.
- Generating the EGL Dependency Graph from EGL projects
- Generating Source Code from OpenAPI Documents
- Developing EGL applications
  Enterprise Generation Language (EGL) is a programming language that you can use to focus on business problems instead of software technologies. Within the Rational® development environment, you can use EGL wizards and other tools to write complex applications with minimal effort.
  - How to use this documentation
  - Additional information about EGL
    The most recent EGL documentation is in the IBM Business Developer documentation.
  - EGL Programmer's Guide
    The EGL Programmer's Guide covers using EGL within the Eclipse Integrated Development Environment (IDE), as well as some of the common programming tasks that EGL developers perform.
  - EGL Generation Guide
    The EGL Generation Guide covers the process of converting EGL code to Java™ or COBOL source code, including the processes and the files involved. This section is intended for a developer who will generate or deploy EGL applications.
    - Introduction to EGL generation and deployment
      After you write and test EGL source code, you generate Java™, JavaScript™, or COBOL code for a target platform.
    - Generation using the Eclipse workbench
    - Generation using the EGL software development kit (SDK)
    - Generating from the workbench batch interface
      The workbench batch interface is a feature that lets you generate and deploy EGL output from a batch environment that can access the workbench.
    - Generating with an Ant script
      You might create an Ant script that cleans a workspace and causes an automatic build and generation. To help you save processing time, the product provides a Java™ VM argument to include in the Ant script.
    - Creating headless EGL build
      You can have multiple Ant tasks for a headless build. With headless builds, EGL builds can be managed more efficiently and EGL can support Agile programming better.
    - Ant tasks for headless build
      Ant tasks are required to create an Ant script that is to be used in a headless EGL build. Besides the Ant tasks defined by Eclipse, Rational® Application Developer, and the ant-contrib library, IBM Business Developer also provide several Ant tasks for your use.
    - EGL Generation Results view
    - Writing Java™ code to capture details of code generation
      You can now write Java™ code to produce a report or otherwise respond to events at generation time.
    - Creating and maintaining a build file
    - Build Descriptor part
      A build file (.eglbld extension) can contain multiple Build Descriptor parts. Each Build Descriptor part controls the generation process for a particular set of circumstances.
    - Overview of build descriptor options
    - Overview of linkage options part
    - Resource associations part
    - Overview of .ir files
    - Overview of the EGL deployment descriptor editor
      The EGL deployment descriptor editor updates the EGL deployment descriptor file. For a description of how that XML file is used, see Introduction to EGL generation and deployment. For a description of how to create such a file, see Creating an EGL deployment descriptor.
    - VSAM support
    - Data conversion
    - Generation output
      This topic outlines the output generated by EGL, including the control files that affect preparation or external deployment.
    - Name aliasing
    - Build plan
    - Build scripts
    - Build server
    - Deploying EGL projects on CICS® Liberty Profile
      You can deploy EGL web projects on a CICS® Liberty profile.
    - Generating and deploying a web service on CICS®
      This topic describes how to generate and deploy a web service on z/OS® CICS®. Aside from setting up the relevant EGL build parts, you must set the following CICS definitions: TRANSACTION, TCPIPSERVICE, and PIPELINE.
    - Deploying a web service requester to CICS®
      You can generate and deploy a logic part that runs on z/OS® CICS® and accesses a web service.
    - Special considerations for generating EGL or SOAP services for z/OS® CICS®
    - Special considerations for accessing SOAP services from IBM® i COBOL programs
      Special considerations apply to accessing SOAP services from EGL-generated COBOL programs on IBM® i. For an overview of the runtime architecture, see Overview of EGL support for SOA.
    - Special considerations for generating EGL or REST services for z/OS® CICS®
    - Special considerations for deploying COBOL SOAP services on IBM® i
      Deploying COBOL SOAP services on IBM® i requires that you generate outputs for both Java™ and COBOL. For an overview of the generated output and the runtime architecture, see Overview of EGL support for SOA.
    - Generating web transactions
      Use EGL web transactions to migrate VisualAge® Generator web transactions to EGL.
    - Overview of Java™ generation
    - Build descriptor options used with JavaScript™
      This topic lists the build descriptor options used with JavaScript™, which is the generated language for EGL Rich UI.
    - Overview of COBOL generation
    - Build descriptor options
    - Linkage options part
  - EGL Language Reference
    The EGL Language Reference covers the fundamental use of the language, including its concepts, syntax, and keywords. This volume is intended for a developer writing EGL applications with some experience in procedural programming.
  - Rational® COBOL Runtime Guide for zSeries®
    This manual provides information about customizing and administering the IBM® Rational® COBOL Runtime.
  - IBM Business Developer EGL Server Guide for IBM® i
    This manual provides information about customizing and administering EGL Server for IBM® i on the host.
  - Generation for VSE Feature Reference
    This reference manual provides z/VSE-specific information about developing and generating EGL programs in the VSE environment.
- Source code analysis with code review
  With code review, you can create configurations of coding rules for EGL source code. You can then run the configurations to check the source code for consistency with the rules.
- Responsive Design Support in IBD
  What is Responsive Design? Responsive design is an approach for creation of web pages that automatically scales its content and elements to match the screen size on which it is viewed. So, instead of designing multiple websites for different devices with variable screen sizes, we can design just one website that scales up or down automatically, to match the device it’s being viewed on.
- Containerizing an EGL RUI Application
Samples
Troubleshooting and support
EGL runtime error messages
Reference
Glossary
Using the help
Notices for IBM Business Developer documentation

Setting up the TCP/IP listener for a called non-J2EE application

If you are using TCP/IP to communicate with a called non-J2EE Java™ program, you must configure a standalone Java™ program called TcpipListener for that program. Specifically, you must follow these steps:

Make sure that the classpath used when running TcpipListener contains fda7.jar, and the directories or archives that contain the called programs; and
Set the tcpiplistener.port to the port number where TcpipListener receives data.

You can start the standalone TCP/IP listener in either of two ways:

To start the listener from the command line, run the program as follows:
```
java com.ibm.javart.calls.listener.TcpipListener propertiesFile
```
propertiesFile
The fully qualified path to the properties file used by the TCP/IP listener. If you do not specify a properties file, the listener attempts to open the following file in the current directory:
```
  tcpiplistener.properties
```
To start the listener from the workbench, use the launch configuration for a Java™ application. In this case, you can specify the name of the properties file in the program arguments of the launch configuration. Alternatively, if you are using the filetcpiplistener.properties as a default, that file should not be in a folder, but should be directly under the project that you specified when you created the launch configuration.