1 JDMK Overview JDMK (Java Dynamic Management Kit) is a Toolkin, which is published by the Sun, is used to implement network management and network services. Simplely said that Java Dynamic Management Kit is an application interface (Java API) and a development tool for Java API. JMX (Java Management Extensions) is a set of NMS solutions based on Java technology. JMX defines a set of architecture and design patterns for network management systems to implement various types of management operations, while JDMK is the first commercial product of JMX. It is an implementation of JMX (Java Management Extensions), which provides Java The application manages a framework for the Java object. JDMK provides a complete solution for the distributed management system. This Java technology-based solution can embed intelligent management into your Agent program, providing an abstract communication layer and can dynamically upgrade. Network management is usually done by large, centralized management applications. These management applications monitors and maintain their jurisdiction by tightly controlling their agents. These agents are used to manage their own network resources, forward commands, and the original data and status information of the network, which are located near the NEs they control, which means that these agents are basically limited. They usually have little intelligence, only basic network element management operations. From a broader vision, there are various protocols and technologies to implement existing network application management systems. To achieve a market goal, developers must choose a single management technology; in some cases, in order to obtain a wider potential market, developers must implement multiple management technologies. Due to the limitations of these two methods, suppliers have selores some management techniques. A Java dynamic management agent exposes its resources in a standard way, providing management services directly on the resource level. These services have intelligence, which allows agent applications to automatically complete administrative tasks. This allows management applications from daily tasks, such as turntable, and therefore also alleviate network loads. The resource interface is marked, which means that equipment vendors and application developers can reach the final agreement: they can use the technology they want! As long as the communication between them is done through the Java dynamic management agent, management applications can access any resources. The same such flexibility is applied to the management service configured in the agent because they can control resources through standard interface. In order to improve the competent agent capabilities, the available new services can be added to the agent through dynamic downloads. In the end, JDMK provides a model-independent model: management app rely on the API, and has nothing to do with the agreement. JDMK brings new solutions to the management field by following aspects: Ø Follow JMX (Java Management Extensions), which manages Java objects through Java applications developed by Java public administration process. Ø Single suite group provides unified expression for system, application, and network management, allowing access to resource uniform. Ø Flexible architecture - it can share network loads and add functions in real time to service-driven network management. Service-driven network management is a new network computing method, and network computing is concentrated on the service you want. This range from the low-level service of the management network service to the value-added services you provide to the user, which can meet the needs of networks and management. In addition, autonomous proxy can functionally make more extensive networks possible. Establish a Java dynamic management architecture, and the service is organically combined. The agent can complete the management task intelligently, which makes management logic to be distributed across the network. Using dynamically hot crafts, new services can be downloaded on the running web server. The service can not be implemented within the service, and can be downloaded on the network as the Java Applets via a simple Web page.
This dynamic, on-demand examples means that in future configuration, management, and monitoring or prior network configuration services (which are created, enhanced, and necessary) are no longer necessary. Since JDMK combines the current and future standards, this unique combination makes the application area more extensive. 2 JDMK work mechanism JDMK work mechanism as shown below:
The left virtual frame in the figure is an Agent end, which is mainly composed of two types of MBean Server and MBean. In the Agent end, all resources or services are manifestinal as MBean, and register with MBean Server, and Connector Server for communication with the management program is also registered as a MBean on the MBean Server. In the above figure, there are two resource MBeans registered on the MBean Server, and the Agent Service is registered as another MBean as a monitoring service. Agent contains a Connector Server, supports RMI, HTTP, HTTPS protocol, and Agent also contains a Protocol Adaptor, supports SNMP and HTML. The remote manager is a Java application running on the remote host, which contains Connector Client and Proxy MBean. Other application components can manage requests to the Agent when the Connector Client is connected to the Connector Server. A operation or configure Monitor Service Monitoring Resource 2 can be called on resource 1 by an Proxy object. HTML Adaptor allows us to view the Agent through the browser, each MBean is rendered as a stand-alone HTML page, and the user can set the attribute through the text field and call the operation by clicking the button. There is also an Administration page to create and delete MBean from MBean Server. 3 How to develop in JMX's Instrumentation layer in JMX how to rendering resources as Java objects; in the JMX Agent layer, how to describe how resources interact with Agent; JDMK expands Agent Services and defines distributed management features of remote access Agent . Solving distributed management depends on the three layers described above. 1 Define the resource as a resource that can be any entity, physical or virtual you want to control through the network. Physical resources can be network devices or printers; virtual resources such as programs running on the host, etc. The resource is seen through the management interface: This is a series of management programs to access properties, operations, and notifications. Defining a resource is to develop a Java object that presented the management interface of the resource. JMX specifically defines how to define a resource based on a certain mode, which is similar to the mode of JavaBean components: attributes include GET and SET; operations are presented by Java Method; send notifications through Java Event mode. Therefore, a MBean is a resource object defined according to JMX design mode. If the resource itself is a Java application, it is a MBean, otherwise, MBean is packaged in a local resource or device into a Java object. As long as you can accurately present the properties and operations of resources, the MBEAN of the resource can be remote from the managed object, and the MBean developer determines the available properties and operations of the MBean. For MBeans within the Agent, you can access each other through a general method or access to each other via MBeanServer. For information on Manager side management, only access to specific MBeans can be passed through these management interfaces. According to the JMX specification, any MBean must implement an interface that specifies the properties and methods for external access. Only when MBean is registered in MBeanServer, the MBean has exposed the properties and methods specified in the interface. For a specific attribute, if the read permissions are open, the MBean provides a GET method. If developed write permissions, MBean provides a SET method. Other methods that must be provided outside the interface also need to be defined in the interface.
2 Exposing your MBeans Java Dynamic Management Agent in Smart Agent Following Customer / Server Mode: Agent responds to the management request from any client you want to access resources, and centrally passes all requests to the target MBean, and returns response information . Processing communication details by agents include receiving and transmitting data, etc., and MBean does not have to care. The central component of the agent is MBean Server, registers the instance of MBean on the MBean Server. It exposes a universal interface, and the customer can request a request to this interface. If the customer may ask a MBean description to know that there is this MBean Those resources, managers programs can use this information to express their requests to MBean Server, such as acquiring or setting attributes, call operation, or registration notifications. The manager program can only access the MBean by requesting MBeanServer, and cannot reference the MBean object directly, and only one object name uniquely identifies MBean. MBean Server also provides a framework that allows Agent Services to interact with MBean. These services they are also reflected by MBean, complete various tasks through interactions with resource MBeans. For example, the manager program is to monitor some of the properties of some MBeans: instantiate a MBEAN of a monitoring service, set the threshold and register the received alarm. The manager program does not have to poll the Agent, and the manager will automatically notify the manager when the MBean property exceeds the threshold. 3 Remote Access Your Agent JDMK allows you to easily access the Agent and resources from a remote application, and the AGENT MBean Server also applies to remote managers, which transpares communication. The management program implements a request through the SET / GET property or with the object name call operation. The Proxy object provides a deeper abstraction through remote MBean to process all communication, and the manager program can be designed and developed like all resources. It is like locally. The management program developed by the Java program language makes communication transparent, and Connector supports RMI, HTTP / TCP, HTTP / SSL protocol. Adaptor provides a view for Agent, all Connector and Adaptor itself is also MBean, which can dynamically create, configure, and delete communication resources based on network conditions or available protocols. Of course, Agent also has a security mechanism to prevent illegal operations of communication MBeans. AdapTOR has established a bridge between JMX-based Agent and existing management systems, you can also create your own Connector and Adaptor to adapt to requirements. 4 JDMK's strengths, using JDMK, the following advantages: l Simplify the design and development of Agent and Manager. l Configuration flexible. l Dynamically expand and upgrade. 1 Simplify the design and development of JMX systems to standardize system components, three levels (INSTRUMENT, Agent, Manager) independently, communicate with the same API, so that modular development can be made, each layer can be independently designed and Implementation also makes the component reuse may be possible because the service developed on a JMX Agent can work on any JMX Agent. Instrumentation layers: l MBeans only need to define their management interface and map the resources of the resources into the properties and operations of the interface. l MBeans can be alive in any JMX Agent. l MBeans don't have to know the details of the outside world.
