Once you are logged in, you see a multi-pane window that consists of:
Banner – contains links that allow the user to log out, and to obtain online help.
Footer – displays the user who is currently logged in.
Details view (right pane) – displays detailed information about a selected item in the tree view, and allows you to perform operations on services.
Tree view (left pane) – contains a hierarchical overview of the various components that are accessible through the console. There is a node under JMX Browser for each host server that the console knows about. Under each of these nodes are the following folders:
Services The Services folder contains all the services that have been installed. A service is simply an MBean with a well-defined lifecycle that has been registered with the ServicesManager MBean. All services have the same interface presented through the Systems Management Console. For each service, you can view basic information about it, and perform a number of operations on it, such as starting it, or viewing its log file.
Events The Events folder allows you to view events that have been recorded on the JMX agent. These are events that correspond to JMX notifications, raised by certain system components.
MBeans The MBeans folder provides access to the underlying MBeans, including those MBeans that are displayed as services. For information about the MBeans whose attributes you can configure and whose operations you can perform, see “Accessing MBeans”.
You can highlight a node in the tree view, and see details associated with it in the property view.
When you are logged in to the Systems Management Console, the MBeans and services that are visible are determined by the J2EE roles that you have been granted. A service can be associated with certain read and update roles. This means that users must be granted these roles before they can view, or perform operations on, the service. For example, the EAServer service might have a read role called ReadX, as well as the default Admin Role. To view the EAServer service, users must be granted either the ReadX role or the Admin Role. By default, a service can be operated on only by someone who has the Admin Role—see “Managing user roles”.
