IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Scenario 8: Troubleshooting application response time in an XD cell

Due to external resource the response time for one of applications in the XD cell degrades below the service policy goal. Annette the level 2 operator, receives an e-mail to indicate that the Application Requests Above Goal situation triggered. This situation triggers when the rate of requests above goal is greater than 0.5%.

  1. In the Tivoli Enterprise Portal navigation tree, Annette follows the workspace link for the triggered situation. The XDVEAppReqAboveGoalPercentHigh Event workspace is displayed.

  2. Annette navigates by a link from the XDVEAppReqAboveGoalPercentHigh Event workspace to the Application workspace.

  3. The Application workspace displays On Demand Router Statistics (ODR) for the selected application module, transaction, class, and protocol summarized over all ODRs in the cell.

  4. From the Application workspace, Annette observes that the average overall response time is 20 seconds and the average server service time is also 20 seconds. This indicates, that some problem is occurring with the handling requests by this application.

  5. To see the deployment targets hosting the application and ascertain which of the deployment targets is contributing to the slow response time, Annette drills down to the Deployment Targets workspace using the Per Deployment Targets link.

  6. The Deployment Targets workspace displays a single deployment target for this application: DynCluster. Annette drills down to this dynamic cluster using the link and then to servers belong to the dynamic cluster.

  7. The servers for the dynamic cluster performance are displayed. From this view, Annette observes that both servers in the dynamic cluster have similar loading. Annette drills down to each server and observes that both have requests higher than the set goal of 10 seconds.

  8. Annette drill downs to Server Diagnostic for one of servers using the link, which opens the data collector workspace for that server. Annette observes in the workspace that the “sleeperEAR” application is displaying a critical red symbol.

  9. Annette double-clicks the application, this opens the Request Analysis workspace.

  10. From the Request Analysis workspace, Annette navigates to the MSVE using the Diagnostic In-Flight Request Search link. From the MSVE, Annette can navigate to the thread for the selected request and view the request call stack.

  11. Annette uses an external ticketing tool to forward the ticket with details to Jim, the Middleware/Application Support SME.

  12. Jim reviews the information and determines that the application waits for response from an external system. Jim researches and resolves the external system issue and restores the application response time before it impacted the majority of the users.


Parent topic:

Scenarios