IBM Tivoli Composite Application Manager for Application Diagnostics, Version 184.108.40.206
The Request Name enables the user to assign alternate request identifiers that are more meaningful and appropriate to the chosen programming model of the application.
The Request Name is provided because the Request String is just one way of identifying requests. There is data that is within the request that is not represented by the Request String. Furthermore, requests can be rather cryptic, so mapping them to something more immediately recognizable or understandable is useful.
For example, a Web request can be mapped by:
- URI: /account/login
- Servlet Class Name: com.cyanea.web.AccountServlet
- Struts Class Name:
http://www.cyanea.com/account/execute/login.do --> com.cyanea.web.account.LoginAction
- Custom Naming Scheme: account.login
When the installed Request Mapper is invoked, data is passed into this plug-in class to assist the custom code developer to make a decision. This data includes the Request Object and the Session Object in the case of a URL-based request.
Parent topic:Data used by the Request Mapper