Diagnosing application issues - what do you need?
lfarmer 120000D5WY Visits (7181)
Imagine you are the developer of a critical WebSphere application and need to find the root cause of poor application response time. What are your requirements for a diagnostic tool?
You want to avoid having to recreate the problem, however you may not have access to the server where the application is deployed and you probably won't be permitted to run a debugger. You need a lightweight tool that can be installed quickly on the server by the application support or operations team that does have access. Then they can gather the diagnostic information for you to process remotely. The data collection component should be installable in minutes, and not rely on a monitoring infrastructure that requires separately installed database servers etc.
Once you have the diagnostic data on your desktop you need a tool that will quickly guide you to the root of the problem. The tool should be able to narrow the problem to inefficient API calls or poorly written methods. Ideally the tool should integrate with your IDE so you can link directly to the application source and address the problem.
One such tool is IBM Application Performance Diagnostics (APD) Lite. This powerful yet lightweight tool can be deployed quickly to help optimize the performance of your WebSphere Application Server and WebSphere Portal applications. APD Lite is comprised of two components:
1. The monitored application server is instrumented with a data collector component, that can integrate with existing Tivoli tools but is not reliant on any monitoring infrastructure
2. The user interface is distributed as an Eclipse Rich Client Platform (RCP) application and as an plug-in that integrates with your Eclipse IDE
APD Lite is available for download from the Continuous Open Beta site: