CORBA (Mib Browser) Application Web Browser Client CORBA Adaptor Adaptor Adaptor Adaptor Adaptor JMX Agent Figure 12.12 Breakdown of JMX Agent by protocol. Protocols NMS API EMS based JMX Agent on NMS Notification Callback To be developed Network by customer Figure 12.13 Representation of calls between EMS, NMS is a generic scenario. Provides details such as EMS host name, total memory and free memory. These details are obtained by the NMS by querying the EMS through the JMX Agent. Provides access to the data stored in the database. Can upload or download files using TFTP. Can register a number of agents with itself as sub-agents. Enables configuration at runtime. The EMS responds to the queries of the NMS through the JMX Agent. The JMX agent can either perform the query on the NE and get the details or check the data- base of the particular NE and provide responses. The protocol involved in sending a response to the NMS through the JMX Agent is the same as the protocol of the query received. 12.10.3 JMX Specifications The JMX specifications define the architecture, design patterns, APIs and services for application and network management in Java. The major benefit of this specification is that it provides a way to use common instrumentation on the agent and support multiple protocols for management. Since JMX is independent of the management infrastructure, the developer of the agent is freed from the details of each manage- ment protocol. 12 Fault Management The JMX architecture is divided into the instrumentation level, agent level and distributed services level. The instrumentation level defines how to use resources in the Java programming language so that they can be managed. The resources developed are called Java Manageable Resources. MBeans follows the design patterns and interfaces defined in this part of the specification, ensuring that all MBeans provide the instrumenta- tion of managed resources in a standardised way. The JMX Agent uses Model MBeans, which are dynamic MBeans that are config- urable an