The outermost request that needs to be monitored is called an edge request. This involves a request that enters the application server from an outside client, for example invoking a Servlet/JSP or a call to an EJB business method through the Object Request Brokers (ORB). However, sometimes this request might not be of interest as it might be a generic call like when Apache Struts applications are involved. In such cases, a custom request might be defined to act as an edge request. In ITCAM for Application Diagnostics, edge requests are tracked starting at L1 monitoring level.
A request that is invoked within another request is called a nested request. For example, a JDBC call like getConnection() invoked from within an EJB business method is a nested request. In ITCAM for Application Diagnostics, nested requests are tracked starting at L2 monitoring level.
Custom requests are defined for application-specific operations that do not fall under the normal pre-defined J2EE operations. A custom request defines a user-specified class and method as the start and end point of a request. If it is enclosed in another request like a Servlet or EJB request, then it becomes a custom nested request.