Quest on Thursday at BEAWorld launched an upgraded, consolidated version of its PerformaSure and JProbe tools for managing J2EE application performance.
The new and renamed Quest Application Assurance Solution for Java and Enterprise Portals, designed to link real end-user transactions to their performance impact on Java applications and Web portals, helps developers measure and optimize the performance of Java applications and portals before they are released into production.
New in the integrated tool set is the ability for developers to diagnose problems in portals, perform memory analysis and automate performance blueprinting.
“Weve taken the data we have and mapped it up into the workflow theyre used to working in,” said Brad Micklea, manager of Java product management for Quest Software Inc. in Toronto.
The enhanced software also automatically maps application interdependencies, and correlates user transactions to application code or resource contention problems.
The ability to automatically map dependencies and track them as they change through time is a big step forward, according to Rich Ptak, principal at Ptak, Noel & Associates in Amherst, N.H.
“Change is becoming much more frequent—especially with J2EE [Java 2 Platform, Enterprise Edition] applications. Being able to correlate changes in dependencies and integrate that into your monitoring model is key,” Ptak said.
On Monday Quest will follow up with the launch of its enhanced Performance Management for Java Applications and Enterprise Portals. The Irvine, Calif., company added the ability to customize dashboards according to the users role.
The portal-style dashboards allow users to mix and match how they want to view performance data. Performance diagnostics are connected to root cause analysis in the new release.
Quest will also claim a first in the new release with the ability to continuously monitor and detect memory leaks while continuing to present low-level detail, according to Micklea. The software provides diagnostics around real-time memory leaks by isolating the end-user transaction, application and Java Class causing the leak.
