Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/DesignDocs/332312"
< EclipseLink | DesignDocs
m (→Requirements Details) |
m (→Scope) |
||
| Line 12: | Line 12: | ||
==Scope== | ==Scope== | ||
*The scope of this issue is limited to the primary EE application servers that we currently support via JMX. These are WebLogic, WebSphere, GlassFish and JBoss. We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container. | *The scope of this issue is limited to the primary EE application servers that we currently support via JMX. These are WebLogic, WebSphere, GlassFish and JBoss. We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container. | ||
| + | ===Session Management=== | ||
| + | ===Unified Metadata=== | ||
| + | *Metadata mappings from Annotations and ORM XML | ||
| + | *JPA 2.0 Metamodel | ||
| + | ===Session Cache=== | ||
| + | ===Query Cache=== | ||
| + | ===Dependency Injection Reference=== | ||
| + | *Spring, Session, Message-Driven and Singleton beans that reference or have injections of EMFs or EMs | ||
| + | ===L1 Cache=== | ||
| + | ===L2 Cache=== | ||
| + | ===JDBC Database Configuration=== | ||
| + | ===Extensibility and Multitenancy=== | ||
| + | *Management of shared schemas | ||
==Requirements== | ==Requirements== | ||
Revision as of 20:23, 15 February 2011
Contents
EclipseLink Application Management, Analytics, Diagnostics and Performance
Problem Statement
- This enhancement details work that will be done to enhance our basic JMX management API and add additional support for diagnostics and analytics reporting. We will also look at adding features that will enable developers to more accurately capture runtime performance and diagnostics information, as well as tools to interpret that data.
- There are two issues to this enhancement that separately deal with management and diagnostics reporting.
Management API
- Our existing runtime JMX management API that is exposed through the services MBean in any of the SUN JConsole, JRockit JRMC, Oracle JRF Enterprise Manager or JBoss web based console is sufficient but needs to be enhanced.
Diagnostics API
- Our existing runtime performance monitoring API could be enhanced with more JVM reporting - ideally that would not itself add overhead. This type of monitoring is currently done with JRockit - however it does not specifically target the JPA runtime API.
Scope
- The scope of this issue is limited to the primary EE application servers that we currently support via JMX. These are WebLogic, WebSphere, GlassFish and JBoss. We may also extend support to SE applications and EJB 3.1 Lite containers running exclusively in the web container.
Session Management
Unified Metadata
- Metadata mappings from Annotations and ORM XML
- JPA 2.0 Metamodel
Session Cache
Query Cache
Dependency Injection Reference
- Spring, Session, Message-Driven and Singleton beans that reference or have injections of EMFs or EMs
L1 Cache
L2 Cache
JDBC Database Configuration
Extensibility and Multitenancy
- Management of shared schemas
Requirements
- Before we can decide on how and where we will enhance our management, analytics and diagnostics support we need to answer the following questions.
- Q1) What do we currently provide
- Q2) What are we going to with existing enhancment requests and how will we merge these with new requirements.
Existing Enhancment Requests
Requirements Details
- Official high level requirements
- R1: Address critical open issues general to all application servers
- R2: Expand platforms that we support JMX management on
- R2.1: Expand support for JMX management of JPA based applications to SE clients
- R2.2: Expand support for JMX management of JPA based applications to JEE6 EJB3.1 container managed deployments
- R2.3: Verify security manager support for MBeans in WebSphere and JBoss
Manageability Requirements
- Make MBeans change session aware
- Introduce Admin Role MBeans
- Investigate Scripting support for configuration changes (WLS for WebLogic, Python for WebSphere, ? for JBoss, ? for GlassFish)
WebLogic Specific Requirements
- WebLogic Server has several monitoring API join points that we can use either at the WebLogic MBean level or through events exposed to JRMC for servers running on the JRockit JVM. We will need to work closely with the WLS team to finalize the interfaces between EclipseLink and WLS.
- R: Expose Runtime monitoring through a new MBean or the new generic PerformanceProfiler MBean
- This MBean would be exposed in EM?
- R: Expose MBean spanning multiple servers?
- R: Expose MBean spanning multiple L2 caches
Generic Server Requirements
- Ideally, any new API should be available to all supported EE servers (not just WebLogic) and optionally SE clients.
- R: Expose PerformanceProfiler/PerformanceMonitor events through a new MBean generic to all EE servers