2.2.4 JMX usage scenarios
Some of the more common JMX usage scenarios you will encounter are:
- Internal product usage: All WAS administration clients use JMX:
WebSphere console
wsadmin scripting client
Admin client Java API
- External programmatic administration In general, most external users will not be exposed to the use of JMX. Instead, they will access administration functions through the standard WAS administration clients.
However, external users would need to access JMX in the following scenarios:
External programs written to control the WAS run time and its resources by programmatically accessing the JMX API.
Third-party applications that include custom JMX MBeans as part of their deployed code, allowing the applications components and resources to be managed through the JMX API.