Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Portland DemoCamp Presentations"

(Here's a list of currently submitted abstracts.)
Line 10: Line 10:
  
 
There's a lot left to do. Suggestions on what to do next and how to do it are strongly encouraged. Suggestions about how to do what we've done better are also encouraged!
 
There's a lot left to do. Suggestions on what to do next and how to do it are strongly encouraged. Suggestions about how to do what we've done better are also encouraged!
 +
 +
'''Application Performance Diagnosis of Distributed Java Applications
 +
 +
[mailto:joe.hoffman@dynatrace.com Joe Hoffman]'''
 +
 +
The dynaTrace Diagnostics tool will be used to analyze a multi-tier application which spans across multiple Java and .NET tiers.  The goal will be to dig down into the details of the  system while it is under load, and determine the root cause of its sluggishness.  The dynaTrace Diagnostics client GUI is built upon Eclipse and is the center of this demonstration.  By observing this demonstration, one can see a good example of how to build powerful client GUIs based upon Eclipse.

Revision as of 10:14, 18 November 2007

Return to Portland Demo Camp

Here's a list of currently submitted abstracts.

An Automated Build System for Eclipse/ECF

Ted Kubaska

This demo shows an automated build system implemented for the Eclipse ECF project. The system uses cruisecontrol and ant, runs on an OSU machine. It checks out code from the Eclipse repository, performs a headless build, and uploads the file to the eclipse/ecf web site. In addition extra builds are performed from a repository located on another OSU machine and made available from a web site hosted by that machine. The demo also shows how the automated build system can be remotely administered.

There's a lot left to do. Suggestions on what to do next and how to do it are strongly encouraged. Suggestions about how to do what we've done better are also encouraged!

Application Performance Diagnosis of Distributed Java Applications

Joe Hoffman

The dynaTrace Diagnostics tool will be used to analyze a multi-tier application which spans across multiple Java and .NET tiers. The goal will be to dig down into the details of the system while it is under load, and determine the root cause of its sluggishness. The dynaTrace Diagnostics client GUI is built upon Eclipse and is the center of this demonstration. By observing this demonstration, one can see a good example of how to build powerful client GUIs based upon Eclipse.

Back to the top