Database to J2EE Monitoring

How can a DBA manage a database supporting J2EE apps if he/she has limited visibility into the database requests those apps are making? Poor visibility into the true impact of J2EE applications that rely on their Oracle databases puts DBAs at a disadvantage and hinders efforts to improve performance. Having a truly relevant view of database performance requires a perspective that includes not only what is happening distinctly within the J2EE application server, the web server and the database but the correlation between them.

Ignite for Java exposes every step of the Web/J2EE/Oracle database interaction, showing the DBA exactly what is impacting database performance and application users. Ignite provides a unique database-oriented view of exactly what the application is doing, from user request through Java methods, down to SQL execution.

Problems can then be isolated and quantified within the database, J2EE app server and the web server, and ultimately down to each SQL statement executed between the User Request and User Response.

Steps monitored:

• SQL statements executed and individual Wait-Events occurring in the Oracle database
• Java method that calls on the J2EE server
• Transaction requests from the Web Server

This proactive monitoring is designed to optimize the impact on the customer experience, the most relevant goal of performance analysis.