KR20050003501A - The converting system for abstracting snmp operation into xml operation and the method therefor, and computer program product using the same - Google Patents

Abstract

PURPOSE: A relay system abstracting an SNMP(Simple Network Management Protocol) operation to an XML(eXtensible Markup Language) operation for supporting communication among network management functions, a relaying method, and a computer program product using the same are provided to define diverse access elements with a single access method through a web service. CONSTITUTION: An input device(21) receives an SOAP(Simple Object Access Protocol) request message including the XML from a client. An SOAP processor(22) processes the received SOAP request message and an SOAP reply message including the XML matched with the SOAP request message. A WSDL(Web Services Description Language) file(25) defines a data type, an operation, and a service of the SOAP message. A CPU(23) includes a request/reply processor(231) for outputting the SOAP reply message by operating the data received from a management network server depending on each mode of the received SOAP request message. A memory(24) stores the data processed in the CPU. A network server connector(27) transmits the data of the network management server to the CPU as the SNMP.

Description

A relay system that abstracts the SNP operation into a WML operation, and a relay method thereof, and a computer program product using the same, and the method of using the same, and a computer program product using the same, {THE CONVERTING SYSTEM FOR ABSTRACTING SNMP OPERATION INTO XML Operation>

The present invention relates to a relay system for abstracting an SNMP operation into an XML operation, a relay method thereof, and a computer program product using the same. More specifically, the present invention abstracts an SNMP-based network management operation for data exchange between network devices supporting the SNMP protocol. The present invention relates to a relay system that supports communication between other web service programs, objects, databases, and comprehensive network management functions by relaying web services and XML-based network management operations, and a relay method thereof, and a computer program product using the same.

The Internet, which began to explode with the development of the world wide web in the late 1980s, formed various computer networks created by vendors (computer makers). The importance of management has also increased. In these computer networks, various devices such as hubs, routers, servers, clients, switches, and bridges exist, and they are interconnected to exchange data. have. As such, various devices connected to the network should be able to perform functions without interruption, be set to maximize efficiency, be able to cope with failures, and be able to add new users freely. This is called network management.

The server that performs network management is called a network management server, and is a network system including a network management server and a network component managed by the network management server, and controls a complex network in order to maximize network efficiency and productivity. This system is called a network management system. The network management server collects, in real time, data related to the current operating state of the network component, such as fault data, configuration data, and statistical data, from the network element. Accordingly, the network management server analyzes the current network based on the collected data, or analyzes the current network based on the collected data, such as analyzing the collected data by the set logic, or promptly notifying the network administrator of an abnormal condition of the network component. It provides the basic data for developing the network operation plan.

In order for a network management server to be compatible with various network components and management methods in such a network management system, an object to be managed, that is, a managed object, must be defined to be compatible with each other. Simple network management protocol (SNMP) is typical as a protocol for this. SNMP is a simple protocol that monitors and oversees network management and network devices and their operations. It allows management information about computing and network components to be logically inspected or changed by remote users, in particular MIB. manages the Internet based on transmission control protocol / internet protocol (TCP / IP) such as related standards describing management information base (SMI) and structure of management information (SMI) To provide a simple and operable structure and system for this purpose. SNMP is designed to manage the Internet efficiently and easily. In the early days, it was a transitional standard that was started for the purpose of short-term use. However, it is still widely used in most Internet administrations because of its easy implementation and compatibility.

However, since SNMP has disadvantages in terms of scalability and efficiency, there are limitations in managing an ever-growing huge network using an SNMP-based network management system. Therefore, researches are attempting to use XML (extensible markup language) for the network as a way to efficiently process and manage a large number of management data derived from a large network by supplementing the disadvantage of the SNMP-based network management system.

XML is a standardized text format designed to transmit structured documents on the Internet web. It is a solution to overcome the limitations of the hypertext markup language (HTML) used in the Internet and to solve the complexity of standard generalized markup language (SGML). In HTML, we added the ability for users to define new tags.

XML not only improves homepage building and search functions, but also facilitates complex data processing of client server systems and allows users to freely manipulate structured databases. XML is a subset of the practical features of SGML, and is expected to be widely used not only on the Internet, but also in the areas of electronic publishing, medicine, business, law, sales automation, digital libraries, and e-commerce. do.

In the above studies, XML is used as a method of data transfer, processing, and storage in a web-based network management system. In other words, standardized XML processing method is used to express management information as XML document, deliver XML document using HTTP communication, store in database or process data with user application.

Web services using these standard XML-formatted interfaces can be used on the Web, accessed from a network of the Internet, intranets, and extranets. In a distributed environment, application servers, CORBA (common object request broker architecture), .NET servers, Abstracted over software systems such as messaging and packaged applications, you can connect any operating system, hardware platform or programming language just like the web. Such a web service is made up of a set of standards. It is a related specification for implementing a web service. It introduces XML, a technology used to describe information, and an interface exposed as a web service. Web services description language (WSDL), which maps to the network, a simple object access protocol (SOAP) that allows Web services interfaces to provide intercommunication functions over the Internet and other networks, as a protocol for remotely executing web services, and It consists of universal decription, discovery, and integration (UDDI), which provides a registry and registry repository services to store and read the web services interface to find the services that are available.

The XML-based network management system has an advantage in scalability, but there is a problem in that the utility is not sufficient when it cannot provide a method for accommodating a device equipped with an existing SNMP agent. In other words, Internet network management is mostly developed based on SNMP. Since most Internet devices are equipped with an SNMP agent and manage the network, the existing SNMP agent can be integrated while taking advantage of XML-based network management. There is a need for management.

In order to solve this problem, in order to integrate and manage the SNMP agent without change with the embedded web server-based agent in the XML-based network management system, the management information of the SNMP agent expressed as the SNMP MIB is changed to XML. In order to actually transmit data, a method of coding a gateway for changing mutual data representation between an SNMP message and an XML document has been proposed.

As an example of such a method, Korean Utility Model Publication No. 20-0299180 discloses an XML conversion device of an element management system (EMS). In this case, in order to convert the SNMP MIB used in EMS to XML document format, the configuration includes the EMS converter and XML receiving equipment that converts the SNMP MIB information of EMS and EMS to XML documents that individually manage the equipment constituting the network. This enables efficient and stable definition and use of information between different types of equipment, easily validates data through DTD (document type definition), and is suitable for applying to structures such as CIM (commoninformation model). Provides XML converter.

However, in this method, it is necessary to check the information by extracting the data of the SNMP MIB. The SNMP MIB, which is the management information of the SNMP agent, is constantly changing according to the information change of the network. Therefore, there is a limit in reflecting the current operating state, there is a problem that can cause data inconsistency between the equipment.

When converting and maintaining the SNMP MIB used by the EMS into an XML document, the maintenance process can load XML into memory and maintain SNMP results in a database or document object model (DOM). Features such as searching and filtering can be made easier than the SNMP protocol. This is usually because searching and filtering are provided by an XML-enabled application program interface (API). In the process of converting SNMP MIB to XML, 1: 1 conversion of SNMP MIB to XML or recommendation model such as CIM can be expressed in XML and SNMP MIB can be mapped. There is a problem in EMS that is not useful and general purpose. Using CIM has the advantage of providing a single interface to the client, but there is a maintenance problem that must be mapped from device to device to support all existing SNMP devices.

Maintaining the SNMP MIB in XML is only useful when the SNMP MIB is deterministic, such as EMS. In addition, since it exists between the client and the device, the SNMP data of the device must be collected and reflected continuously or periodically, and there is a problem in that the system burden or data inconsistency is high.

Therefore, in order to solve this problem, the SNMP MIB information of the management network server is imported into the SNMP protocol and converted into XML only when the client requests. You can consider services.

The present invention is to solve this problem, it is expressed by the XML representation of the operation for the equipment that supports SNMP, and provides this as a web service, depending on the machine, operating system, development language, etc. of the existing SNMP management system in a distributed environment It is possible to define various access elements in a single approach, and to easily connect business functions from various program, object, database and network management perspectives.

In addition, through the present invention, the data exchange between the SNMP devices to simulate the XML, and abstracts the SNMP protocol to be easily and quickly applied to network management systems and service systems that have already been developed or developed around SNMP.

1 is a conceptual diagram showing the operating principle of the entire system of the present invention.

2 is an internal configuration diagram of the relay system of the present invention.

3 is a flowchart showing the overall processing of the present invention.

4 is a flowchart showing a processing procedure in a synchronous mode.

5 is a flowchart showing a process in asynchronous / cycle mode.

<Explanation of symbols for the main parts of the drawings>

11. Relay system 12, 13. Client

14. Management network server 21. Input device

22. SOAP handlers 23. CPU

24. Memory 25. WSDL Files

26. Output Device 27. Network Server Connection

The present invention for achieving the above object relates to a relay system for abstracting an SNMP operation to an XML operation, an input device for receiving a SOAP request message including XML from a client, a SOAP request message and a SOAP request message received from the input device SOAP handler for processing SOAP response messages containing XML corresponding to the WSDL file connected to the SOAP handler to define the data type, operation and service of the SOAP message, and management network according to each mode of the SOAP request message received from the SOAP handler. A CPU including a request / response processor that outputs a SOAP response message by calculating data received from the server, a memory connected to the CPU to store the processed data, and a management network server and a CPU connected to the management network server. Network server connection to send data to the CPU via SNMP It should.

In the relay system of the present invention, the CPU may further include an SNMP processor configured to receive and compute data of the management network server through SNMP in any one of synchronous, asynchronous, and periodic modes.

In addition, in the relay system of the present invention, the CPU may further include a thread processor that performs thread generation, registration, and operation based on data transmitted from the management network server to SNMP in the asynchronous or periodic mode.

The CPU may further include a trap processor configured to receive and calculate data from the management network server through SNMP when the mode is a trap setting.

According to the present invention, a relay method for abstracting an SNMP operation into an XML operation may include receiving SOAP request operation data of a SOAP request message including XML from a client, analyzing the SOAP request operation data, and analyzing the SOAP request operation data. Acquiring data about the server in the management network through SNMP operation from the management network, calculating data for the management network server according to each mode of the analyzed SOAP request operation data, and converting the calculated data into XML including XML Sending the response message to the client.

In the relay method of the present invention, the step of calculating data for the management network server in the synchronous mode may include opening an SNMP session of the analyzed SOAP request operation data, setting a parameter related to the SNMP operation, and managing network. It is preferred to include sending an SNMP request to the server, waiting for a response to the SNMP request, and closing the SNMP session.

In the relay method of the present invention, the step of computing data for the management network server in the asynchronous mode includes the steps of generating a thread by operating the data from the management network server with SNMP and driving the thread. It is preferable.

In the relay method of the present invention, in the periodic mode, calculating data for the management network server may include generating a thread by calculating data from the management network server with SNMP, registering a thread with a thread pool, It is preferable to include the step of repeatedly driving the thread according to a predetermined operating time, and the step of calculating data for the management network server according to the repeated operation of the thread.

In the relay method of the present invention, in the trap setting mode, calculating data for the management network server includes: setting a client-side URL to transmit data according to trap generation, and calculating data of the management network server when the trap occurs. And sending the SOAP response message to a URL.

The computer program product of the present invention may include a series of instructions for performing the above-described relay method, and may further include a library for providing instructions included in the series of instructions.

Embodiments of the present invention will be described below with reference to the drawings.

1 is a diagram schematically showing a network configuration of an overall system of the present invention. As shown in FIG. 1, the relay system 11 of the present invention for abstracting an SNMP operation into an XML operation is connected to a plurality of clients 12 and 13 and a plurality of management network servers 14. Multiple clients 12 may send a SOAP request message including XML to the relay system, which relay system 11 receives the SOAP request message and then sends the received SNMP message from the management network server 14 accordingly. The data can be computed and sent back to the original client 12 or another client 13 with a SOAP response message. Thus, the client 12 and the client 13 may be the same object or different objects.

A plurality of clients 12 and 13 connected via the web transmit and receive data about the management network server using SNMP from the relay system 11 through the SOAP message in the form of XML. Simple object access protocol (SOAP) is a text-based protocol for smoothly supporting remote applications. It is used to exchange structured and typed information using XML in a distributed environment. Provides access to the server and service. Removing all messages of the form <SOAP-XXX> from the SOAP message results in a normal XML document.

As shown in FIG. 1, when the client 12 transmits a SOAP request message to the relay system 11, the relay system 11 maps it through the internal WSDL, and accordingly, the desired information is received by the internal SNMP processor. Get and process it and send it to the client 13 as a SOAP response message.

WSDL is a structure consisting of data type definition, abstract operation, and service binding. It describes the data type and structure of web service and describes the data type and structure in the exchanged message. It contains information on how to map and link messages to underlying implementation techniques.

The details of the coding of the WSDL are illustrated in Listing 1 below. Listing 1 below is for illustrating the WSDL of the present invention, but the present invention is not limited thereto.

List 1

As described in Listing 1, lines 1 to 219 are XML schemas, coded as <types> to define data types, and lines 220 to 283 are coding instructions for abstraction operations. , Lines 283-318 code for service binding.

Looking at some of these more specifically, the data types for synchronization mode (sync), asynchronous mode (period) and period mode (period) are defined in lines 55-60, and requests in lines 84-92. In the body elements for lines) and lines 94 to 104, data types such as body elements for a reply are defined. Lines 145 to 157 also include IP address (line 146), community (line 147), retry (line 148), timeout (line 149), version (line 150), which are basic information of the client computer sending the SOAP request message. Port (line 151), targetcode (line 152), mode (line 153), uri (line 154), interval (line 155) and waittime (line 156) are described.

In addition, abstraction operations (lines 220 to 283) are coded for SDMMediatorSoap, SDMMeidatorHttpGet, SDMMeidatorHttpPost, and the like. In the service binding, the URL of the server where the product is installed (line 297) is coded.

The SOAP request message and the SOAP response message under the WSDL list are coded in XML, and the internal envelope has a knowledge element of a header and a body. The header is optional and may be omitted, but the body part must be described. The SOAP request message of the present invention has information to be processed in the body part and may request a remote function call. Correspondingly, the SOAP response message of the present invention is capable of responding to a remote function call.

The body part of the SOAP message of the present invention may be a message, and may contain a valid and well defined XML document without having a namespace and without a DTD reference or processing instruction.

2 is a diagram illustrating an internal structure of the relay system of the present invention, and is a diagram showing in detail the internal structure of the relay system of the present invention in more detail.

As shown in FIG. 2, the relay system of the present invention includes an input device 21, a SOAP processor 22, a central processing unit (CPU) 23, a memory 24, a WSDL file 25, And an output device 26 and a network server connection 27. The CPU 23 includes a request / response processor 231, a thread processor 232, a trap processor 233, and an SNMP processor 234. Such an internal structure of the relay system of the present invention is merely to illustrate the present invention, the present invention is not limited to this, and may be replaced by other components having the same function.

The relay system of the present invention receives the SOAP request message from the client through the input device 21. The relay system forwards the SOAP request message received from the client to the SOAP handler 22. The SOAP handler 22 is processed by the WSDL file 25 of the relay system of the present invention and provides the function of receiving a SOAP message from the outside or sending a SOAP message to the outside. In the present invention, the SOAP handler 22 is implemented using SUN Microsystems' JAXM (Java API for XML Messaging) and Apache Tomcat. The result of the various operations through the CPU 23 is transmitted by the SOAP processor 22 to the client in the SOAP response message via the output device 26 again. That is, the SOAP handler 22 is responsible for receiving the SOAP request message and transmitting the SOAP response message. In particular, in the case of a synchronous mode request, the SOAP processor 22 is responsible for receiving and sending at the same time, and in the case of an asynchronous / cycle mode request, the SOAP processor 22 is separately responsible for receiving and sending.

The request / reply handler 231 in the CPU 23 extracts the SOAP body from the SOAP request message received by the SOAP handler 22. The request / response processor 231 identifies the body components that are delivered according to the interface described in the WSDL, and processes them by dividing them into synchronous mode, asynchronous mode, periodic mode, and trap settings.

The SNMP processor 234 is a library for SNMP itself developed by JAVA. The SNMP processor 234 is connected to an SNMP device, configures and transmits a protocol data unit (PDU) for GET, GETNEXT, SET, and BULK, and sends the resulting SNMP PDU from the device. It is responsible for receiving and reporting SNMP results and PDU results to the upper system.

If there is a synchronous mode request for SNMP, since the processing must be performed in real time, after receiving the data of the management network server through SNMP through the network server connection unit 27, the SNMP processor 234 processes and waits. Next, after passing through the request / response processor 231, the SOAP processor 22 transmits the SOAP response message through the output device 26 in the form of a SOAP response message. In this case, since it is a synchronous mode request, the clients connected to the pressure device 21 and the output device 26 are the same object.

In the case of an asynchronous mode request or a periodic mode request, a thread is created, registered, and started through the thread processor 232 based on the information obtained from the SNMP processor 234. The response processed through the process is a request / After passing through the response processor 231, the SOAP processor 22 transmits the result to the output device 26 in the form of a SOAP response message. In the periodic mode, the thread runs continuously at predetermined times.

If a trap is set and a corresponding situation occurs, after receiving data of the management network server through SNMP through the network server connection unit 27, the trap / reprocessor 233 processes the data to the request / response processor 231. After passing through the SOAP processor 22, the SOAP response message including the XML is transmitted to the output device 26. In particular, the trap processor 233 may be divided into a trap transmitter and a trap receiver.

As described above, according to the relay system of the present invention, it is possible to minimize the development burden of the network management system because it is divided into the synchronous mode, asynchronous / cycle mode, and trap settings according to the SOAP body.

3 is a flowchart showing the overall processing of the relay system of the present invention. As shown in FIG. 3, the relay system of the present invention receives a SOAP request message including XML, extracts a SOAP body, processes it with an SNMP processor, and transmits the result as a SOAP response message including XML. . Hereinafter, the operation of the relay system of the present invention will be described in more detail.

When the process starts according to the relay system of the present invention, first, in step S31, the relay system of the present invention receives a SOAP request message including XML from a client. In step S32, the SOAP body part is extracted from the received SOAP request message. In step S33, an XML tag regarding the request of the BODY component is extracted, and then the request modes are compared. At this stage, processing is divided into real-time mode, asynchronous / cycle mode, and trap settings according to the BODY component comparison. The following describes the processing for each mode in detail by exemplifying List 2 relating to the synchronization mode. Listing 2 is merely to illustrate the synchronization mode of the present invention, but the present invention is not limited thereto.

List 2

Depending on the mode (line 7), it can be defined as synchronous, asynchronous or periodic mode. Listing 2 illustrates the sync mode. The type (line 8) defines the type of operator, and the pdu (line 9) only needs to define the objectid attribute on request, and in the case of a set operation, the objectid and syntax attributes and their values. On request one session component (line 7) can have multiple operation elements (line 8) and one request component (line 6) can be connected to multiple devices There can be multiple session components. With the above configuration, when a specific operation such as set or get is instructed to the management network server through the PDU, a response according to the PDU can be obtained.

In the case of the above-mentioned list 2 regarding the synchronous mode, the same applies to the periodic mode in the present invention. In the case of the periodic mode, the same result as in the above-described list 2 can be obtained, except that the result is continuously repeated according to a predetermined time, which is different from the synchronous mode.

In case of asynchronous mode, it responds with SOAP message informing the requester that it is processing normally. After SNMP processing is completed, the result is sent as a SOAP response message to the designated URL. In the process, data is passed to the thread handler, which creates and manages the thread to support the operation in its asynchronous and periodic modes. The periodic mode is suitable when the data needs to be collected periodically, such as the performance data of SNMP. The thread is repeatedly run at a given time interval, and the processing result is continuously sent to the client as a SOAP response message.

Listing 3 below illustrates asynchronous mode. Listing 3 is merely illustrative of the asynchronous mode of the present invention, but the present invention is not limited thereto.

List 3

Keys in asynchronous mode are generated on request and passed to the asynckey attribute (line 21), and the asynckey attribute (line 33) provided asynchronously can be seen as the result of the request.

The trap processing will be described with reference to the following Listing 4. The following trap processing in Listing 4 is merely illustrative of the present invention and the present invention is not limited thereto.

List 4

The processing request can also specify the destination to which the trap is to be delivered from the equipment. In this process, the trap handler continuously receives and delivers traps from the equipment. This process uses message queues. In Listing 4, the manager component (line 5) sets the URL to pass information to when trapping. When a trap occurs (line 25 or below), a SOAP response message is sent to the specified URL.

Referring back to FIG. 3, in the present invention, when the request mode is a real-time synchronous mode, the process proceeds to step S34 and requests processing from the SNMP processor, and then waits for completion until a result is received from the SNMP processor in step S35. . In the case of asynchronous / cycle mode, the process of thread creation and registration is performed in step S36. In this case, the process proceeds to the next step without waiting for a result. In the case of trap setting, a process is requested to the trap processor in step S37. The result of each mode generated through such a process is terminated by the process of transmitting to the client as a SOAP message in step S38.

According to the relay method of the present invention as described above, since the relay system of the present invention imports necessary data from the management network server only when a request is made from the client to SNMP, there is no need to convert and manage the SNMP MIB into XML. You only need to map the parent request with the SNMP request. In other words, redefine SNMP to XML and show it as XML to client, and XML has a form simulating SNMP.

4 and 5 are diagrams illustrating in detail each mode in the relay system of the present invention, Figure 4 shows the process according to whether the synchronous mode, Figure 5 shows the creation, registration and It shows the driving process.

The synchronization mode process of the present invention will be described in detail with reference to FIG. 4. In step S41 of FIG. 4, an SNMP session for SNMP communication with a management network server is opened. Next, in step S42, an SNMP operation such as GET, SET, GETNEXT is performed and parameters such as a PDU value are set, and then in step S43, it is checked whether or not it is in synchronous mode. In the synchronous mode, the process proceeds to step S44 to send an SNMP request from the management network server, and waits for an SNMP response in step S45 and closes the SNMP session in step S48 without proceeding any further. In step S43, if it is not in synchronous mode, a CALLBACK class is generated to receive a response in asynchronous mode in step S46 for reconfirmation, and accordingly, in step S47, SNMP is performed in step S472 with simultaneous progress. After receiving the asynchronous response at the same time as request (S471), and then closes the SNMP session in step S48. Through this process, all processes of the synchronous mode are completed.

5 is a diagram illustrating a process of creating and registering a thread in the asynchronous / period mode in the relay system of the present invention. After the XML tag is extracted from the request of the body component of the SOAP body extracted from the received SOAP request message, the request modes are compared, and in the case of one-cycle asynchronous mode or N-cycle periodic mode, thread creation and registration are started. First, in step S51, a thread is created. In step S52, the next process is performed depending on whether the asynchronous / periodic mode is used.

In the case of the periodic mode, the process proceeds to step S53 to register the target thread of the cycle mode to the thread pool. In step S54, the thread is registered in step S55 according to the operation time, that is, the cycle interval and whether the drive is performed. S54) and step S55 are repeated continuously. In the asynchronous mode, the thread is driven in step S56. This process is completed by sending the result generated by this process to the output device as a SOAP response message including XML.

As described above, according to the present invention, it is possible to support an XML-based web service with minimal environmental constraints by supporting only a single XML interface. In addition, the SNMP protocol can be redefined and abstracted to XML for all devices that support SNMP, supported as a web service, shared in a distributed environment, and applied to existing SNMP developed products.

In addition, the present invention is applied to a client / server environment, and by supporting N clients irrelevant to the environment at the same time, it is possible to reduce development costs depending on the development environment. The present invention can easily and quickly apply system development by supporting XML API that abstracts the SNMP protocol, and can minimize the development burden of network management system by supporting synchronous mode, asynchronous mode, periodic mode and trap setting.

In the present invention, as a result of separating the content and the document form, which is a characteristic of XML, there is an advantage that the XML can be easily converted into a required form or a database through XSL (extended stylesheet language).

As a result, the present invention supports the SNMP protocol as an XML-based web service and can be shared in a distributed environment, and exchanges data using an XML document that is established as a document standard for data exchange between network devices supporting the existing SNMP protocol. Provide in a structure that can be done.

Although the present invention has been described above, it will be readily understood by those skilled in the art that various modifications and variations are possible without departing from the spirit and scope of the claims set out below.

Claims (11)

A relay system that abstracts simple network management protocol (SNMP) operations into extensible markup language (XML) operations. An input device that receives a simple object access protocol (SOAP) request message containing XML from a client, A SOAP handler for processing a SOAP request message received from the input device and a SOAP response message including XML corresponding to the SOAP request message; A web services description language (WSDL) file connected to the SOAP handler to define data types, operations, and services of a SOAP message, A central processing unit (CPU) including a request / response processor for outputting the SOAP response message by calculating data received from a management network server according to each mode of the SOAP request message received by the SOAP processor; A memory connected to the CPU to store data processed by the CPU; and A network server connection unit connected to the management network server and the CPU to transmit data of the management network server to the CPU by SNMP; Relay system comprising a. In claim 1, The CPU, And an SNMP processor configured to receive and operate data of the management network server through SNMP in real time when the mode is any one of synchronous, asynchronous and periodic modes. The method of claim 1 or 2, The CPU, And a thread handler configured to create, register, and run a thread based on data transmitted from the management network server to SNMP when the mode is asynchronous or periodic. The method of claim 1 or 2, The CPU, And a trap processor configured to receive data from the management network server via SNMP when the mode is a trap setting. As a relay method to abstract SNMP operations to XML operations, Receiving SOAP request operation data of a SOAP request message including XML from a client, Analyzing the SOAP request operation data, Obtaining data for a server in a management network through an SNMP operation from a management network according to the analyzed SOAP request operation data; Calculating data for the management network server according to each mode of the analyzed SOAP request operation data, and Transmitting the calculated data to a client in a SOAP response message including XML. Relay method comprising a. In claim 5, Computing data for the management network server when the mode is a synchronous mode, Opening an SNMP session of the analyzed SOAP request operation data, Setting parameters related to SNMP operations, Sending an SNMP request to the management network server, Waiting for a response to the SNMP request, and Closing the SNMP session Relay method comprising a. In claim 5, Computing data for the management network server when the mode is asynchronous mode, Generating a thread by computing data from the management network server with SNMP; and Driving the thread Relay method comprising a. In claim 5, Computing data for the management network server when the mode is a periodic mode, Generating a thread by calculating data from the management network server with SNMP; Registering the thread with a thread pool, Repeatedly driving the thread according to a preset operation time, and Calculating data for the management network server according to the repetitive driving of the thread; Relay method comprising a. In claim 5, Computing data for the management network server when the mode is a trap setting, Setting a client-side URL to which data in response to trap generation is to be transmitted, and Setting the data of the management network server to transmit a SOAP response message to the URL when a trap occurs; Relay method comprising a. A computer program product comprising a series of instructions for performing a method according to claim 5. In claim 10, And a library for providing instructions included in the series of instructions.