EGL Reference Guide for iSeries
When you are in the Workbench, the EGL debugger lets you debug EGL code
without requiring that you first generate output. These categories are
in effect:
- To debug page handlers, as well as programs used in a J2EE context, you
can use the local WebSphere Application Server test environment in debug
mode--
- You must use that environment for all code that runs under J2EE in a Web
application.
- You may use that environment for programs that run in a batch application
under J2EE.
- To debug other code (batch applications that do not run under J2EE;
or text applications), use a launch configuration that is outside of the
WebSphere Test Environment. In this case, you can start the debug
session with a few keystrokes.
If you are working on a batch program that you intend to deploy in a J2EE
context, you can use the launch configuration to debug the program in a
non-J2EE context. Although your setup is simpler, you need to adjust
some values:
- You need to set the value of the build descriptor option J2EE to NO when
you use the launch configuration.
- Also, you need to adjust Java property values to conform to differences in
accessing a relational database--
- For J2EE you specify a string like jdbc/MyDB, which is the name
to which a data source is bound in the JNDI registry. You specify that
string in these ways:
- By setting the build descriptor option sqlJNDIName; or
- By placing a value in the EGL SQL Database Connections preference page, in
the Connection JNDI Name field; for details, see Setting preferences
for SQL database connections.
- For non-J2EE you specify a connection URL like
jdbc:db2:MyDB. You specify that string in these
ways:
- By setting the build descriptor option sqlDB; or
- By placing a value in EGL SQL Database Connections preference page, in the
field Connection URL; for details, see Setting preferences for SQL
database connections.
A later section describes the interaction of build descriptors and EGL
preferences.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.