![]() ManagementHome home = (ManagementHome)PortableRemoteObject.narrow(obj,ManagementHome.class) Starting with J2EE 1.4, all application servers were forced to expose standardized management and monitoring APIs via a dedicated Management EJB component (MEJB) and Java Management Extensions (JMX), for example: JSR 77 (J2EE Management) is a useful but forgotten standard. It also describes the GlassFish monitoring API, which provides a read-only facility for accessing the Java Virtual Machine (JVM), the GlassFish application server, and the GlassFish application server's metrics and counters. ![]() ![]() This article describes the GlassFish management API, which allows you to manipulate the GlassFish application server's configuration, including its monitoring capabilities. For unknown reasons, both capabilities have been ignored for years, but the DevOps movement is making these built-in monitoring and management capabilities interesting again. Also, our ignorance about easily accessible information for application servers, such as monitoring data, is surprising.Īpplication servers have emitted useful monitoring data and provided basic management capabilities for 10 years, ever since J2EE 1.4 was released in November of 2003. ![]() IT is all about streamlining and automation, so it is somewhat ironic that we developers still tolerate repetitive and boring manual tasks, such as deployment. Exploit the built-in monitoring and management capabilities of GlassFish to automate application deployment and gain insight into application performance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |