|
Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (e.g. printers) and service-oriented networks. Those resources are represented by objects called MBeans (for ''Managed Bean''). In the API, classes can be dynamically loaded and instantiated. Managing and monitoring applications can be designed and developed using the Java Dynamic Management Kit. JMX 1.0, 1.1 and 1.2 were defined by JSR 003〔(JSR 003: JavaTM Management Extensions (JMXTM) Specification )〕 of the Java Community Process. , JMX 2.0 is being developed under JSR 255 but the development has been halted.〔(JSR 255: JavaTM Management Extensions (JMXTM) Specification, version 2.0 )〕 The JMX Remote API 1.0 for remote management and monitoring is specified by JSR 160.〔(JSR 160: JavaTM Management Extensions (JMX) Remote API )〕 An extension of the JMX Remote API for Web Services is being developed under JSR 262.〔(JSR 262: Web Services Connector for Java Management Extensions (JMX) Agents )〕 Adopted early on by the J2EE community, JMX has been a part of J2SE since version 5.0. It is a trademark of Oracle Corporation. == Architecture == JMX uses a three-level architecture: # The ''Probe'' level - also called the ''Instrumentation'' level - contains the probes (called MBeans) instrumenting the resources # The ''Agent'' level, or MBeanServer - the core of JMX. It acts as an intermediary between the MBean and the applications. # The ''Remote Management'' level enables remote applications to access the MBeanServer through connectors and adaptors. A connector provides full remote access to the MBeanServer API using various communication (RMI, IIOP, JMS, WS- * …), while an adaptor adapts the API to another protocol (SNMP, …) or to Web-based GUI (HTML/HTTP, WML/HTTP, …). Applications can be generic consoles (such as JConsole〔(Using JConsole to Monitor Applications )〕 and MC4J〔(The MC4J project creates management software for J2EE application servers and other Java applications. )〕) or domain-specific (monitoring) applications. External applications can interact with the MBeans through the use of JMX connectors and protocol adapters. Connectors serve to connect an agent with a remote JMX-enabled management application. This form of communication involves a connector in the JMX agent and a connector client in the management application. Protocol adapters provide a management view of the JMX agent through a given protocol. Management applications that connect to a protocol adapter are usually specific to the given protocol. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Java Management Extensions」の詳細全文を読む スポンサード リンク
|