WildFly Management Interfaces: Difference between revisions
No edit summary |
|||
| Line 22: | Line 22: | ||
=JMX Management Beans= | =JMX Management Beans= | ||
The management API is also exposed as JMX Management Beans. These Management Beans are referred to as ''core mbeans''. Prior to | The management API is also exposed as JMX Management Beans. These Management Beans are referred to as ''core mbeans''. Prior to WildFly, the management functionality was primarily JMX based. With WildFly, the core management does not rely on JMX to perform operations, JMX exposed beans are now just an alternative mechanism, in addition to the native and HTTP interfaces. [JBoss7 Remoting#JBossRemotingAndJMXAccess]. | ||
<font color=red>Questions: Does JMX read/write the same core management functionality? Explain that in more details.</font> | |||
Revision as of 00:07, 10 February 2016
Internal
Overview
WildFly core management functionality is exposed via two different management interfaces (the terms management interfaces and management APIs are used interchangeably):
- Native API - used by the Management CLI
- HTTP API - used by the Management CLI and the web-based Management Console.
These two interfaces offer distinct ways to access the same core management system.
Diagram
Configuration
Security
JMX Management Beans
The management API is also exposed as JMX Management Beans. These Management Beans are referred to as core mbeans. Prior to WildFly, the management functionality was primarily JMX based. With WildFly, the core management does not rely on JMX to perform operations, JMX exposed beans are now just an alternative mechanism, in addition to the native and HTTP interfaces. [JBoss7 Remoting#JBossRemotingAndJMXAccess].
Questions: Does JMX read/write the same core management functionality? Explain that in more details.