METHOD AND APPARATUS FOR MONITORING RUNTIME OF PERSISTENCE APPLICATIONS

• US 20100122239A1
• Filed: 11/10/2008
• Published: 05/13/2010
• Est. Priority Date: 11/10/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Neufeld, Andrea, Jayasinghe, Robin de Silva, Theobald, Dietmar
• Granted Patent: US 8,356,288 B2
• Time in Patent Office: Days
• US Class Current: 717/131
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/348 Circuit details, i.e. tracer hardware
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/87 Monitoring of transactions

Abstract

A monitoring method and apparatus monitors a runtime application to collect and display static and dynamic data concerning software entities and database operations in a runtime environment. In one embodiment, monitoring classes are used to collect monitoring data from at least one PersistenceUnit (PU) and at least one PersistenceContext (PC) associated with the PU of an application the uses an in implementation of a Java Persistence Application Programming Interface (JPA). A Java Management Extension (JMX) MBean communicates with the monitoring classes to expose monitoring data outside the runtime environment.

Claims

1. A monitoring system comprising:

an application using an implementation of a Java Persistence Application Programming Interface (JPA) including at least one PersistenceUnit (PU) and at least one PersistenceContext (PC) associated with the PU;

a first software layer of monitors to gather monitoring data from the PU and the associated PC;

a second software layer to collect monitoring data from the first software layer of monitors at a central point comprising a monitor service; and

a third layer comprising a Java Management Extension (JMX) MBean to expose monitoring data collected at the central point.

2. A system according to claim 1 further including a user interface communicating with the JMX MBean to expose the monitoring data to a user.

3. A system according to claim 1 further wherein the first and second software layers are contained within a JPA container and the JMX MBean is outside of the JPA container.

4. A system according to claim 2 further wherein the user interface is integrated in a further administrator and monitoring tool.

5. A system according to claim 4 wherein the Administrator and Monitoring tool includes navigation to database independent SQL monitoring, and the JMX MBean is reachable by the same navigation used to reach the database independent SQL Monitoring.

6. A system according to claim 1 wherein the monitoring data gathered by the PU and PC monitors includes static metadata about a given JPA application stored in the PU and volatile, dynamic data that represents an application'"'"'s state regarding its object persistence stored in the PC.

7. A system according to claim 1 further including an active PC data structure to hold data relating to active PCs that have an extended lifetime.

8. A system according to claim 1 wherein a monitored PC has a lifecycle beginning with a TX begin event and ending with a TX commit event, a PC monitor for the PC is registered at the beginning of the lifecycle, and the data from the PC monitor is dumped and the PC monitor unregistered at the end of the lifecycle.

9. A system according to claim 6 wherein the static metadata includes a list of entities per PU, persistence fields per entity, and a list of named queries.

10. A system according to claim 6 wherein the PU monitors aggregated data for database operations including create, read, update and delete (CRUD) operations on JPA entities, operations for relationship navigation, and Java Persistence Query Language (JPQL) and native queries.

11. A system according to claim 6 wherein the dynamic data is collected during runtime of an application and includes CRUD operations'"'"' execution time aggregated by managed entities and operation type, and execution time aggregated by query, lifetime of a PC, and number of managed entities at transaction end.

12. A system according to claim 1 wherein the monitors are Java classes that hold internal data structures with the monitored data.

13. A system according to claim 12 wherein the Java classes are accompanied by proxied versions of themselves, wherein the proxied versions execute calls to the monitors and delegate to target methods.

14. A system according to claim 1 wherein a static method is monitored using a slim object handed over to each monitored static method through an interface that offers methods to start and stop monitoring database operations.

15. A software system comprising:

a Java Persistence Application Programming Interface (JPA) container including at least one persistence unit (PU) having an associated persistence context (PC);

at least one PU monitor associated with the PU to collect monitoring data from the PU;

at least one Object Relational Persistence (ORP) monitor in the JPA container to collect monitoring data from the at least one PU monitors; and

at least one Java Management Extension (JMX) MBean communicating with the at least one ORP monitor to expose monitoring data to components outside the JPA container.

16. A monitoring system comprising:

one or more software components to collect monitoring data about an application in a run-time environment, the monitoring data including static data and dynamic data about the application;

a user interface providing navigation to display monitoring information including or derived from the monitoring data, the monitoring information including;

persistence units (PU);

persistence contexts (PC);

entities;

relationships;

named/dynamic queries; and

caches.

17. A monitoring system according to claim 16 further wherein the monitoring information is displayed in a hierarchy including current persistence units displayed in a PU view, and wherein the persistence contexts, entities, relationships, named/dynamic queries, and caches are displayed to show details of a PU selected from the PU view.

18. A monitoring system according to claim 16 further wherein:

the monitoring information about the PUs includes summary data about a number and lifetime of created PCs and an average number of entities per PC;

the monitoring information about the PCs includes a start time, number of managed entities and creates, reads, updates and deletes (CRUDs);

the monitoring information about the entities includes name, number of fields, number of CRUDs, and CRUD-time;

the monitoring information about the relationships includes declaring and target entity, declaring field, cardinality, number of (DB) operations and operation time;

the monitoring information about the named/dynamic queries includes text, Structured Query Language-text, number of executions and execution time; and

the monitoring information about caches includes type of the cache, current and maximum size, number of hits and requests and hit ratio.