O'Reilly logo

IBM WebSphere: Deployment and Advanced Configuration by Roland Barcia, Keys Botzum, Tom Alcott, Bill Hines

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

JMX in WebSphere Application Server

In WAS V5, all runtime components are instrumented as MBeans, which correspond to the instrumentation layer in the JMX architecture. WAS V5 implements a JMX MBean server in each WAS process, corresponding to the JMX agent layer. At the distributed services layer, WAS V5 supports two types of connectors—RMI/IIOP and SOAP/HTTP(S)—which provide administrative client access to server resources.

WAS management function is achieved using JMX. The administrative clients that you are familiar with (wsadmin and the admin console) are simply clients of the WAS JMX infrastructure. In essence, WAS management, under the covers, boils down to using JMX MBeans. WAS V5.x implements over 70 MBeans.[2] The documentation for ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required