com.sun.enterprise.admin.monitor.callflow.Agent
This interface exposes the call flow agent API. This is intended to be called by various container trap points. An implementation of the call flow agent would collect the data supplied, and persist it, for later querying and analysis. Further, it is possible to set filters, based on client side attributes such as caller IP address and caller security principal (USER). The trap point call sequence has a specific order: { requestStart, addRequestInfo*, requestInfoComplete, (startTime, (webMethodStart|ejbMethodStart))*, ((ejbMethodEnd|webMethodEnd), endTime)*, requestEnd } Data schema: Tables RequestStart: { RequestId, Timestamp, CallerIPAddress, RemoteUser } RequestEnd : { RequestId, Timestamp } StartTime : { RequestId, TimeStamp, ContainerTypeOrApplicationType } EndTime : { RequestId, TimeStamp, ContainerTypeOrApplicationType } MethodStart : { MethodName, RequestId, Timestamp, ComponentType, ThreadId, AppId, ModuleId, ComponentId, TransactionId, SecurityId } MethodEnd : { RequestId, Timestamp, Exception }
@author Ram Jeyaraman, Harpreet Singh, Nazrul Islam, Siraj Ghaffar
@date March 21, 2005