IBM Tivoli Composite Application Manager for Application Diagnostics, Version

Default request mapping behavior

From the application server perspective, there are two major types of requests: JSP and Servlet. These calls come either from a Web server, or from an application server other than itself.

We call this request, usually expressed in the form of a string, the ORS. The ORS is composed of the URI plus the query string.

A unique ORS can be used to represent a specific application function such as log in, check out, and log out, this might not always be the case. Other styles of application design use different programming techniques to represent the underlying function, while still maintaining a simple, uniform ORS throughout a series of interactions. When monitoring applications that use such a design, you can use the Request Mapper to distinguish among these different interactions that use the same ORS.

In addition, when performing workload characterization and understanding resource consumption, an analyst might sometimes find that it is neither possible nor effective to break down consumption simply by ORS, especially if there are too many of them. Aggregation of consumptions based on classification of ORS is more desirable.

The Request Mapper functionality is designed to resolve these types of problems. When an application server receives a request (ORS), the Request Mapper enables the ORS to be rewritten into two other strings before it is passed on to ITCAM for Application Diagnostics:

If no request mapper is used, the Application Monitor maps the incoming ORS onto a Request Name and an Application Name using the following rule:

Request Name     = ORS without the host nameApplication Name
     = URI of ORS  

In-flight Request Search is conducted on the Request Name. Server Activity Display uses Request Name for the display. Performance Analysis and Reporting performs decomposition by Application Name.

Parent topic:

Request Mapper