IDDE (IBM Monitoring and Diagnostic Tools for Java - Interactive Diagnostic Data Explorer) has been placed on the Eclipse Marketplace and thus can be easily installed into your own Eclipse. It is still available on ISA (IBM Support Assistant), but this post will discuss the new way of installing it on your previously installed Eclipse, regardless of the platform you are running on.
I have Eclipse Kepler EE Edition installed on my 64 Bit Ubuntu and so from Help->Eclipse Marketplace put IDDE into the Find box and press Go. Hopefully it points you to IBM Monitoring and Diagnostic Tools for Java - Interactive Diagnostic Data Explorer (IDDE). Click Install and go through the various stages of a typical Eclipse plugin install, including restarting Eclipse. Don't be tempted to open the IDDE perspective just yet, take a read of how I have it set up first. This isn't the way everyone uses it, but it's the way that fits in with my requirements.
On my system I have a directory tree that contains all the dumps and traces I've collected and am currently working on. The root of this tree is /data/dumps. So, in my Eclipse in the default Java (or Java EE) perspective I create a General project that points to this directory, which is outside my Eclipse workspace.
To do this it's File->New->Project.. Open the General twistie and select Project and click Next. I give it the name "dumps", deselect the "Use default location" and use the Browse to get to /data/dumps as the directory for this general project, and click Finish.
Now that we have a project pointing to all the dumps we have on our workstation, with the project selected, we can now open the IDDE perspective (Window->Open Perspective or just click the Open Perspective button).
The window on the left will show the PD Navigator. This is a view of all the files and directories in the general project that we created earlier. Remember, if you add a file or create a directory outside of Eclipse the changes won't appear until you press the Refresh button (the two yellow arrows).
Linked sources and RemoteSystemsTempFiles will be discussed on a later post, for now just look at the 3 subdirectories in this example, and the files that are visible in the subdirectory (dumps/home) that is expanded.
There are two core files, a javacore and a heapdump. In the actual directory on the disk there are other files but these are not artifacts recognised by IDDE so they are not displayed. Notice I have expanded the two core files, the first has already been looked at using IDDE and thus it is flagged with Resume Investigation. IDDE has found an Investigation Log in the directory that related to this core file so will use it when the core file is looked at again. The Investigation Log has the same name as the artifact (the core file) with .idde as a suffix. This is a plain text file that can be viewed and changed using a normal editor. It can also be emailed to a colleague showing the diagnostic progress that has been made on the core file. If someone else has a copy of the dump they can place this Investigation Log (idde file) in the same directory and IDDE will use it as a starting point when it opens the dump.
The second core file hasn't been looked at yet so it says Start Investigation. If the twistie is expanded (or double click the Start Investigation) the dump will be opened in an editor window in the main part of the screen.
Notice the filename of the file that is being edited is the Investigation Log in that it has the same name as the core file but with a .idde suffix. Also the first couple of lines in the file are greyed out as they just contain meta data about the core file that IDDE uses.
We can now start entering commands and viewing the output. Commands start with an exclamation mark and can start at any position on a line. With the cursor placed at the end of the command, press Ctrl-Enter and the command will be executed against the dump and the output placed in the Investigation Log. A good place to start is the !javaoverview command.