Here is a snapshot of the table listing the applications For example, if there is ejb embedded in a war, the sniffer list will show both 'war' and 'ejb'. Under the application tree node, all apps will be listed, and when user clicks on the app, the right frame will show all the sniffers associated with this app. This is because any deployed application can have multiple sniffers. We will not group the deployed applications into EAR, WebApp, EJB jar as we did in V2. Listing of applications in the tree node will be changed. Same for the case when user specifies the directory. Gui will pass the bundle to the backend (upload to server side if needed), leaving the backend to determine what type of applications is deployed.
Glassfish monitoring rar#
This includes war, ear, jar, rar files, including wars with ejb jars.
For this release, all Java EE application types will be supported. In v3 prelude, only war deployment is supported. This will be supported for web application only as no other container team has approached the GUI team for such support.Ī table will be provided that listed out all the customized and, the default value specified in the deployment descriptor, and allows user to override that. Ĭonsole will provide the UI for user to edit the and of the deployment descriptor as specified in the above one pager. This is based on the Application Management One Pager. This will include both the configuration and viewing of the monitor data. There will be support for monitoring of the JRuby container. Appropriate UI widgets will be used so user can configure the properties spelled out in 4.7.1.1 section of the one pager.īased on the scripting one pager, there is not enough info at this point regarding the configuration for Jython/Django application. Console will provide UI to do the deployment and listing of the deployed apps. Another plugin to support administration and application configuration for Django applications. One plugin is to support administration and application configuration for JRuby framework (Rails, Merb). There will be 2 plugin modules implemented by the GUI team. This is based on the Scripting Support One Pager. See section 4.4 for features which are NOT in scope for this release.
Glassfish monitoring full#
This release will include full support for Java EE 6 features. Able to host the Online Help set online is a risk factor.Without this refactoring, there is a significant risk that problem areas in our application may impact the schedule (namely Tree-breadcrumb issues, and frameset issues). While this work has the possibility of impacting timelines, it is expected that that will not be the case.
Glassfish monitoring update#