The eG Java BTM employs an advanced ‘tag-and-follow’ technique to trace the complete path of each business transaction to a web application, end-to-end. When doing so, it auto-discovers the application servers the transaction travels through, and also automatically ascertains what remote service calls were made by the transaction when communicating with the servers. In the process, the eG Java BTM measures the following:
- The total response time of each transaction;
- The time spent by the transaction on each application server;
- The time spent by the transaction for processing every external service call (including SQL queries);
Using these analytics, the eG Java BTM precisely pinpoints the slow, stalled, and failed transactions to the web application, enables administrators to accurately isolate where – i.e., on which application server – the transaction was bottlenecked, and helps them figure out exactly what caused the bottleneck – an inefficient or errored query to the database? A slow HTTP/S call to another application server? a time-consuming POJO / JMX method execution? a slow SAP JCO/async call? By quickly leading administrators to the source of transaction failures and delays, the eG Java BTM facilitates rapid problem resolution, which in turn results in the low downtime of and high user satisfaction with the web application.