Browse Prior Art Database

Simplify use of Java Platform Debugger Architecture to debug remote Java programs Disclosure Number: IPCOM000012903D
Original Publication Date: 2003-Jun-09
Included in the Prior Art Database: 2003-Jun-09
Document File: 1 page(s) / 41K

Publishing Venue



Disclosed is a unique way to simply the debugging of remote java program on IBM iSeries using Java Platform Debugger Architecture (JPDA) from IDE(Integrated Development Environment). The methodology disclosed here automatically launches the remote Java program with debug mode. Effectively replaces typical JPDA usage comprising of cumbersome interelated steps with one step.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Page 1 of 1

  Simplify use of Java Platform Debugger Architecture to debug remote Java programs

Typically developers of RPG/COBOL programs familiar with use of green-screens face significant hurdles when moving to a web-based Java Development Platform.

The Eclipse Integrated Development Environment (IDE) provides a generic way to debug remote Java programs. However, IDE requires several cumbersome interrelated steps and there is a need to replace these with one step.

Java Platform Debugger Architecture (JPDA) is supported by the Eclipse based IDE.

Eclipse based IDE implements Java Debug Interface ( JDI ). Users can connect to, and debug any remote application running on a remote Java Virtual Machine Debugger Interface ( JVMDI ) which is compliant with VM through IDE. However the generic way to use JDI is cumbersome for typical iSeries legacy program developers. The typical scenario includes the steps of: Go to iSeries "green-screen" to start class in remote VM. Java Debug Wire Protocol (JDWP) port and tedious options must be specified. This causes execution of the program to halt until a connection is established with debug client on this port. IDE debugger client is then started which tries to connect to the above specified port.

Once a connection is sensed, the remote class starts to run until a breakpoint is hit, or the program terminates.

The disclosed idea effectively automates the whole process described above. The debugging of remote Java program on iSeries from IDE is...