Setting up the J2EE runtime environment for EGL-generated code

EGL-generated Java™ programs and wrappers run on a J2EE 1.4 server such as WebSphere® Application Server v6.0, on the platforms listed in Runtime configurations.

Your primary tasks when embedding generated Java classes into a J2EE module are as follows:
  1. Place output files in a project, in either of two ways:
    • Generate into a project, as is the preferred technique; or
    • Generate into a directory, then import files into a project.
  2. Place a linkage properties file in the module (see Deploying a linkage properties file).
  3. Eliminate duplicate jar files.
  4. Export an enterprise archive (.ear) file, which may include Web application archive (.war) files and other .ear files; for details on the procedure, see the help pages on export.
  5. Import the .ear file into the J2EE server that will host your application; for details on the procedure, see the documentation for your J2EE server.
You may need to fulfill these tasks as well:

Related concepts
Development process
Generation of Java code into a project
Java program, PageHandler, and library
Linkage options part
Linkage properties file
Runtime configurations

Related tasks
Deploying Java applications outside of J2EE
Deploying a linkage properties file
Eliminating duplicate jar files
Generating deployment code for EJB projects
Processing Java code that is generated into a directory
Providing access to non-EGL jar files
Setting deployment-descriptor values
Setting the JNDI name for EJB projects
Setting up a J2EE JDBC connection
Setting up the J2EE server for CICSJ2C calls
Setting up the TCP/IP listener for a called appl in a J2EE appl client module
Understanding how a standard JDBC connection is made
Updating the deployment descriptor manually
Updating the J2EE environment file

Related reference
Java runtime properties (details)
Linkage properties file (details)

Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.