You
can invoke the EGL debugger
from an EGL-generated Java™ program
or wrapper, so you can use the EGL debugger when you work on a partly
deployed
application. The program needs a call statement that you then associate
with
the callLink element of a linkage options
part.
Similarly, you must associate the wrapper with a callLink element.
In either case, the element must specify the remoteComType property
as DEBUG.
Programs running in JEE
To
invoke the EGL debugger
from an EGL-generated program or wrapper that runs in JEE, follow
these steps:
- Make sure you have added a linkage options part
to your build file. For
instructions on how to do this, see Adding a linkage options part to an EGL build file.
- Edit the callLink element to include
the remoteComType property.
To edit the callLink element, see Editing the callLink element of a linkage options part.
For details on setting the remoteComType property,
see remoteComType in callLink element.
- Make sure that the program to be debugged is running in the same
server
as its caller.
- Add the EGL debugger JAR files to the server.
Make sure the server is
running in debug mode.
- Run the program in the debugger.
Programs not running in JEE
Different rules apply when the called program to be debugged does
not run
in JEE. When this is the case, the caller of the program might be
running
anywhere, including on a remote system. Follow these steps:
- Start
a listener program. Start a listener by using an EGL Listener launch
configuration that has only one configurable setting, a port number.
The default
port number is 8346.
- If multiple EGL Listeners are running
at the same time, you must specify
a different port for each EGL Listener. You might also need to specify
a different
port if port 8346 is being used by another application or if a firewall
prevents
use of that port. To specify a different port number, see Creating an EGL Listener launch configuration.