This section discusses how to create an overall monitoring strategy, including monitoring to understand these dimensions: The response times perceived by end users; the basic health of the systems that participate in an end-to-end user request; and the resource usage of applications.
Use the links provided in this topic to learn about monitoring capabilities.
Follow these shortcuts to get started quickly with popular tasks.
To analyze Web site response from a client viewpoint, use Tivoli® Monitoring for Transaction Performance.
Monitoring overall system health is fundamentally important to understanding the health of every system involved with your system. This includes Web servers, application servers, databases, back-end systems, and any other systems critical to running your Web site.
Monitoring, optimizing, and troubleshooting WebSphere® Application Server performance can be a challenge. This article gives you a basic strategy for monitoring with an understanding of the application view.
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.
This page provides a starting point for finding information about the dynamic cache service, which improves performance by caching the output of servlets, commands, web services, and JavaServer Pages (JSP) files.
This page provides a starting point for finding information about SIP applications, which are Java programs that use at least one Session Initiation Protocol (SIP) servlet written to the JSR 116 specification.
This page provides a starting point for finding information about web services.
This page provides a starting point for finding information about Java Transaction API (JTA) support. Applications running on the server can use transactions to coordinate multiple updates to resources as one unit of work, such that all or none of the updates are made permanent.