Restriction:
Remote debugging is only supported on AIX, Solaris, HP-UX, and Windows.
Note: This section describes how to debug a program running on one machine from a debugger user interface on another machine. It does not describe how to debug the server code for WebSphere Application Server Enterprise Edition objects.
The debugger allows you to run the debugger user interface and the debug engine on separate machines. These separate machines can be running different operating systems. When you start the debugger for remote debugging, you first start a debug engine daemon. This daemon waits for a connection from the debugger user interface. Once a connection is established, you can begin to debug your program.
To start debugging a remote interpreted Java program from the command line:
Alternatively, you can use a command line after starting the debug engine to issue the idebug command, using the remote debug parameters. If you use this method to make the connection, you must specify the -qhost parameter and the -qlang parameter for the language you are debugging. For information on the idebug command parameters, see the related topic below.
Restriction: The above method does not apply when debugging
interpreted Java programs on Solaris. To debug an interpreted Java program
running on Solaris, see the related topic below.
Tip: The debug engine is terminated if the debugger cannot load the program you want to debug. Also, the debug engine is terminated when the program you are debugging runs to completion or is terminated manually. To prevent these situations use the -multi option of the irmtdbgj command.
Warning: When debugging your interpreted Java program remotely, communication between the debugger and the program being debugged may be terminated prematurely by the JVM. If this happens, you will need to reload your program. To reload your program, select File > Load Program and enter the required information in to the Load Program dialog.
Starting
the debugger for debugging compiled languages remotely