Notice: This Wiki is now read only and edits are no longer 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 (→EclipseLink Application Analytics, Monitoring, Performance and Diagnostics) |
m (→EclipseLink Application Analytics, Monitoring, Performance and Diagnostics) |
||
Line 7: | Line 7: | ||
*Official high level requirements = 1) Make our management framework better | *Official high level requirements = 1) Make our management framework better | ||
*R1: Address critical open issues general to all application servers | *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 | ||
+ | |||
===Constraints=== | ===Constraints=== | ||
===Assumptions=== | ===Assumptions=== |
Revision as of 10:58, 11 February 2011
Contents
EclipseLink Application Analytics, Monitoring, Performance and Diagnostics
Problem
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.
Requirements
- Official high level requirements = 1) Make our management framework better
- 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