Debugging an EGL batch program
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 the setup is straightforward,
you need to adjust some values:
- Set the value of the J2EE build descriptor option to NO when you use the launch configuration.
- Adjust Java™ property values
to conform to differences in accessing a relational database:
- For J2EE, specify a string like jdbc/MyDB,
which is the name to which a data source is bound in the JNDI registry.
You can specify that string in the following ways:
- By setting the sqlJNDIName build descriptor option; 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, specify a connection URL like jdbc:db2:MyDB.
You can specify that string in the following ways:
- By setting the sqlDB build descriptor option; 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.
- For J2EE, specify a string like jdbc/MyDB,
which is the name to which a data source is bound in the JNDI registry.
You can specify that string in the following ways:
For information on EGL debugger commands, see EGL debugger controls. For more information on how build descriptor settings affect the EGL debugger, see How build descriptor settings affect the EGL debugger. For information on Secondary Authentication ID, see Secondary Authentication ID.