Gaming News | Gaming Opinion | Playstation 4 | Xbox One | PS Vita | Film | Media

JBoss JMX console or the HTML Adaptor?

If you had ever worked with the Extension Consoles of the Java Management of the first generation (like the JBoss JMX console or the HTML Adaptor) in the clustered environment, then you haven’t actually seen the potential of the JMX client technology. Managing the clustered application by traversing to the JMX console of every application is a highly error-prone and manual. A clustered or distributed application environment requires a JMX console to be centralized.

In this case, there are several questions on the access control such as: Who has to be granted the permission to access the exposed information through the managed beans (MBeans)? Who has to be permitted to modify the changes during the runtime? A crystal clear requirement for a fine-grained control for access is prevalent. The administrators should be capable of giving just the read-only access to the quality assurance and development teams while still retaining a complete access in the operations/administration group.

You may have made use of the log files in the past to sketch the runtime behavior of the application. Or else you may have wrote few interfaces of custom management to obtain the information on runtime, perform the administrative process of the runtime, or might be for sending the alerts when anything goes wrong. The JMX makes it pretty easy to instrument the applications using the Java objects, MBeans that represent the manageable resources. By the MBeans, the applications that are JMX-enabled can be monitored and managed using the JMX clients.

jManage is a command-line and Web-based, open source JMX client which is constructed based on the actual needs of the production environments. This provides a centralized console to manage the distributed application and application clusters environments. This tool even provides fine-grained access control, Simple Network Management Protocol (SNMP) support, security, graphs and alerts. jManage assists the custom remoting protocols for Websphere 5+, JBoss 3.2+, Weblogic 6+, along with the basic Remote API protocol for JMX.


With the J2SE 5.0, one can now manage and monitor the Java Virtual Machine through the MBeans. The MBeans are available for classloading, memory, threading etc., allowing one to:
• Get the thread dumps by making use of a JMX client
• Graph the non-heap or heap usage of memory
• See how the garbage collection is operating, or run the GC (Garbage Collector) if you wish
• Turn on the tedious classloading logs
• Look at the JDK loggers that are configured and modify the log level without having to restart the application

Choose the management interface

The applications that are configured in jManage could be managed using any one of these interfaces:
• Web interface: This is the easiest interface to use. Just traverse your browser to the jManage server, log in with your log in details, and make use of the simple WYSIWYG interface.
• Command line interface: If you wish to set up the automated scripts, then this is the interface that is suitable for you.
• Java API: The jManage can be accessed through a set of the APIs of Java, which allows the jManage to be utilized as the backend system and even permits the applications to get themselves registered when they come online.

If you want to learn about anything then you are recommended enlightened wealth institute to get success in you study.

Leave a Comment