Server and method for integrated middleware management

Abstract

A method for integrated middleware management of a server is disclosed. A middleware integrated management method according to one embodiment of the present invention comprises: (a) collecting middleware engine data at predetermined time intervals or upon the occurrence of a preset event by a data collection process operating on each of a plurality of middleware servers, and then receiving said middleware engine data or data processed therefrom through a message queue; (b) mapping said received data to corresponding management identification information and storing it in a storage; and (c) verifying said stored data to support checking whether the middleware is operating normally on the plurality of middleware servers.

Description

Technology Field

[0001] The present invention relates to a middleware integrated management server and method, which enables integrated and efficient management of whether each middleware server is operating normally in an environment where multiple middleware servers are operated. Background Technology

[0002] Today, as financial companies become increasingly reliant on computer systems, the management complexity of their IT systems is growing. Specifically, they simultaneously operate heterogeneous server operating systems such as AIX, SunOS, HP-UX, and Linux, and require the operation of extensive middleware to connect various services including payment, risk management, authentication, and mobile channels.

[0003] However, due to the complexity of this system architecture, a problem arises where responding to service failures requires significant time, cost, and manpower. In particular, since seamless and stable real-time customer service is critical for financial services, a solution is needed to manage middleware engines in an integrated and efficient manner.

[0004] However, until now, there has been a lack of automated solutions to collect and manage middleware engines in an integrated and efficient manner.

[0005] Accordingly, the inventor developed a technology capable of integratedly and efficiently managing whether each middleware server is operating normally in an environment where multiple middleware servers are running. The problem to be solved

[0006] The objective of the present invention is to provide a middleware integrated management server and a method capable of comprehensively and efficiently managing whether each middleware server is operating normally in an environment where multiple middleware servers are operated. means of solving the problem

[0007] A middleware integrated management method according to an embodiment of the present invention for achieving the above-mentioned purpose comprises: (a) a step of receiving middleware engine data or data processed therefrom through a message queue after middleware engine data is collected at predetermined time intervals or upon the occurrence of a preset event by a data collection process operating on each of a plurality of middleware servers; a step of storing the received data in a storage by mapping it to corresponding management identification information; and a step of supporting verification of whether the middleware operates normally on the plurality of middleware servers by verifying the stored data.

[0008] At this time, in step (a) above, System Configuration data items are collected by a data collection process operating at each of the plurality of middleware servers at predetermined time intervals and specialized according to a predefined format, and based thereon, when a transmission file is generated which is the middleware engine data or data processed therefrom, transmission to the message queue can be performed by the data transmission pipeline.

[0009] In addition, the above data specialization can be performed according to a predefined format at the level of business logic that may affect the performance of the middleware engine.

[0010] Additionally, the above step (b) may include (b1) a step of performing an integrity verification based on the number of System Configuration data items included in the transmission file, and (b1) a step of parsing the received transmission file and mapping it to management identification information and storing it in a storage when the integrity verification is completed.

[0011] In addition, the above management identification information may be information including a middleware management host, a business code, a business logic code, and a port number.

[0012] In addition, in step (a) above, when a preset event occurs, middleware configuration data is collected as middleware engine data by a data collection process operating on each of the plurality of middleware servers, and when it is determined that there is a change in data as a result of comparing it with previously recorded configuration data, new configuration data—referred to as a 'transmission file'—can be transmitted to the message queue as the middleware engine data or data processed therefrom by a data transmission pipeline.

[0013] Additionally, the above step (b) may include: (b3) a step of setting the name and storage path of a new file based on the middleware management host and middleware engine names included in the header of the transmission file; and (b4) a step of generating data of the new file based on the content of the transmission file, and restoring the transmission file to the new file by aligning the data lines within the new file using the line numbers of the content.

[0014] Additionally, the above step (a) includes receiving the middleware engine data or data processed therefrom through a different message queue corresponding to the type of the collected middleware engine data, and the type of the middleware engine data may be classified based on at least some of System Configuration data, configuration data, the function of each middleware, the workload of each middleware server, whether a failure has occurred in each middleware, and the performance of each middleware server.

[0015] Additionally, the above step (c) includes (c1) a step of determining the status of the middleware server based on whether at least some of the values ​​of the stored data exceed a predetermined standard, and (c2) a step of providing the determination result to a user to support checking whether the middleware is operating normally in the middleware server, and the above step (c1) can determine the middleware server to be normal even if the predetermined standard is exceeded, provided that an exception flag is processed.

[0016] Additionally, the above step (c) may include: (c3) a step of supporting the provision of a UX interface that illustrates at least one middleware server and an architecture block of a server associated therewith on an administrator terminal; and (c4) a step of supporting the display of normal operation on the architecture block through the UX interface and enabling an administrator to click a specific area to perform exception flag processing for a specific system.

[0017] In addition, in step (a) above, the data collection process operates based on a task script written with abstracted common commands, and the task script distributed to the plurality of middleware servers is converted and executed on individual middleware servers to suit a specific system environment, and when the task script is executed, the data collection command can be executed under predefined common conditions according to standardized script metadata.

[0018] A middleware integrated management server according to one embodiment of the present invention includes a communication unit that receives middleware engine data or data processed therefrom through a message queue after middleware engine data is collected at predetermined time intervals or upon the occurrence of a preset event by a data collection process operating at each of a plurality of middleware servers, and a processor that maps the received data to corresponding management identification information and stores it in a storage, and verifies the stored data to support checking whether the middleware operates normally at the plurality of middleware servers. Effects of the invention

[0019] The present invention enables integrated and efficient management of whether each middleware server is operating normally in an environment where multiple middleware servers are operated. Brief explanation of the drawing

[0020] FIG. 1 is a schematic diagram showing the operation concept of a middleware integrated management system (1000) according to one embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of a middleware integrated management server (100) according to one embodiment of the present invention. FIG. 3 is a schematic diagram showing the middleware management process of a middleware server (200-1, 200-2, ...) according to one embodiment of the present invention. FIG. 4 is a schematic diagram showing the transmission process of a data transmission pipeline according to one embodiment of the present invention. FIG. 5 is a schematic diagram showing the data refinement process of a middleware integrated management server (100) according to one embodiment of the present invention. FIG. 6 is a schematic diagram showing the middleware management process of a middleware server (200-1, 200-2, ...) according to one embodiment of the present invention. FIG. 7 is a schematic diagram showing the data refinement process of a middleware integrated management server (100) according to one embodiment of the present invention. FIG. 8 is a schematic diagram showing the data refinement process of a middleware integrated management server (100) according to one embodiment of the present invention. FIG. 9 is a flowchart illustrating a middleware integration management method according to one embodiment of the present invention. Specific details for implementing the invention

[0021] Hereinafter, various embodiments according to the present invention will be described with reference to the attached drawings.

[0022] In this process, the thickness of lines or the size of components depicted in the drawings may be exaggerated for the sake of clarity and convenience of explanation. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intent or convention of the user or operator. Therefore, the definitions of these terms should be based on the content throughout this specification.

[0023] Embodiments of the present invention are described below with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0024] Throughout the specification, when a part is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0025] Terms and words used in this specification and claims should not be interpreted as being limited to their ordinary or dictionary meanings, but should be interpreted in a meaning and concept consistent with the technical spirit of the invention, based on the principle that the inventor can appropriately define the concept of the terms to best describe his invention.

[0026] Therefore, it should be understood that the embodiments described in this specification and the configurations illustrated in the drawings are merely some of the most preferred embodiments of the invention and do not represent all of the technical spirit of the invention, and that various equivalents and modifications that may replace them may exist at the time of filing this application. Furthermore, as used in this specification, "comprise", "include" and / or "comprising", "including" specify the presence of the mentioned features, numbers, steps, actions, parts, elements, and / or groups thereof, and do not exclude the presence or addition of one or more other features, numbers, actions, parts, elements, and / or groups. Additionally, when describing embodiments of the invention, "may" or "may be" may include "one or more embodiments of the invention."

[0027] Additionally, to aid in understanding the invention, the attached drawings are not drawn to actual scale, and the dimensions of some components may be exaggerated. Furthermore, the same reference numerals may be assigned to identical components in different embodiments.

[0028] The statement that two subjects of comparison are 'identical' means that they are 'substantially identical.' Therefore, substantial identity may include deviations considered low in the industry, for example, deviations within 5%. Additionally, the statement that a parameter is uniform in a given area may mean that it is uniform from an average perspective.

[0029] Although terms such as "first," "second," etc., are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are used merely to distinguish one component from another, and unless specifically stated otherwise, the first component may also be the second component.

[0030] Throughout the specification, unless specifically stated otherwise, each component may be singular or plural.

[0031] The fact that any configuration is placed on the "upper (or lower)" of a component or on the "upper (or lower)" of a component may mean not only that any configuration is placed in contact with the upper (or lower) surface of said component, but also that another configuration may be interposed between said component and any configuration placed on (or below) said component.

[0032] Furthermore, where it is stated that one component is "connected," "coupled," or "connected" to another component, it should be understood that while said components may be directly connected or connected to each other, another component may be "interposed" between each component, or that each component may be "connected," "coupled," or "connected" through another component. Additionally, when it is stated that a part is electrically coupled with another part, this includes not only cases where they are directly connected but also cases where they are connected with another component in between.

[0033] Throughout the specification, "A and / or B" means A, B, or A and B unless specifically stated otherwise. That is, "and / or" includes any combination or any combination of the enumerated items. "C to D" means C or more and D or less, unless specifically stated otherwise.

[0034] In the specification, the expression "supports XX" means that one device provides data, transmits control commands, performs authentication, provides a UI, performs operations, or performs other actions to enable another device to perform certain actions.

[0035] FIG. 1 is a schematic diagram showing the operation concept of a middleware integrated management system (1000) according to one embodiment of the present invention.

[0036] Referring to FIG. 1, a middleware integrated management system (1000) according to one embodiment of the present invention includes a middleware integrated management server (100), a plurality of middleware servers (200-1, 200-2, ..., 200-n), a storage (300), a plurality of linked servers / DBs (400-1, 400-2, ..., 400-m), and an administrator terminal (500) (n, m are natural numbers).

[0037] The middleware integrated management server (100) is a device for managing whether each of the multiple middleware servers (200-1, 200-2, ..., 200-n) is operating normally in an integrated and efficient manner. The middleware integrated management server (100) receives middleware engine data or data processed therefrom from the multiple middleware servers (200-1, 200-2, ..., 200-n), maps it to corresponding management identification information, and stores it in a storage (300). Then, it supports verifying whether the middleware is operating normally in the multiple middleware servers (200-1, 200-2, ..., 200-n) by verifying the stored data.

[0038] Middleware engine data is information indicating the operation and status of the middleware engine, and may include at least some of System Configuration data and middleware configuration data.

[0039] The middleware integrated management server (100) does not, in principle, manage the operation and status of the linked server / DB (400-1, 400-2, ..., 400-m) that operates in conjunction with multiple middleware servers (200-1, 200-2, ..., 200-n), but can receive and store information about the linked system included in the middleware engine data or the data processed therefrom. The middleware integrated management server (100) can refine, analyze, and inspect the data before or after storing the received data in the storage (300). In addition, it can support verifying whether the middleware operates normally when multiple middleware servers (200-1, 200-2, ..., 200-n) are involved in the operation of the linked server / DB (400-1, 400-2, ..., 400-m).

[0040] Additionally, the middleware integrated management server (100) can identify the middleware server (200-1, 200-2, ..., 200-n) by using user information stored in a linked server / DB such as an account management system, and store it in a storage (300) to notify the system administrator when an event occurs.

[0041] Multiple middleware servers (200-1, 200-2, ..., 200-n) are devices that operate a middleware engine so that work can be properly performed in the linked server / DB providing the service. That is, they are servers that execute middleware, which is intermediate layer software responsible for communication, data exchange, transaction processing, resource management, etc. between an operating system (OS) and an application.

[0042] For example, at least some of the following can be executed: web server middleware that handles HTTP requests and provides static / dynamic pages (Apache, Nginx, IIS, etc.); application server middleware that executes business logic and manages transactions (Tomcat, JBoss, WebLogic, etc.); message-oriented middleware that performs communication based on asynchronous message queues (MOM: RabbitMQ, Kafka, ActiveMQ, etc.); DB middleware that mediates database access and manages connections (MyBatis, Hibernate, etc.); transaction processing monitors responsible for distributed transaction management (TPM: Tuxedo, CICS, etc.); API gateway / integration middleware responsible for inter-system API integration, authentication, and logging (EAI: Kong, WSO2, Mule ESB, etc.); and container middleware responsible for managing communication between microservices (Istio, Envoy, Linkerd, etc.).

[0043] Multiple middleware servers (200-1, 200-2, ..., 200-n) collect middleware engine data through a data collection process operating on each server. The multiple middleware servers (200-1, 200-2, ..., 200-n) generate a transmission file, which is middleware engine data or data processed from it. Transmission to the middleware integrated management server (100) is achieved by a data transmission pipeline transmitting the transmission file to a message queue.

[0044] The storage (300) is a space that stores middleware engine data received by the middleware integration management server (100) or data processed therefrom by mapping it to management identification information. It may be in the form of at least one of a database, a data store, a repository, a data lake, or a warehouse.

[0045] Multiple interconnected servers / DBs (400-1, 400-2, ..., 400-m) are devices that provide user services either interconnected with multiple middleware servers (200-1, 200-2, ..., 200-n) or independently.

[0046] The administrator terminal (500) is a device for managing at least one middleware server (200-1, 200-2, ..., 200-n). The administrator terminal (500) provides a UX interface that can intuitively manage at least one middleware server (200-1, 200-2, ..., 200-n). In particular, as described below, a UX interface illustrating an architecture block of at least one middleware server and a server associated therewith may be provided.

[0047] The administrator can check whether the architecture block is functioning normally through the UX interface of the administrator terminal (500), and can perform exception flag processing for a specific system by clicking on a specific area. In addition, the administrator can receive reports of errors in a specific middleware server.

[0048] The middleware integrated management server (100) can provide information as a web service to an administrator terminal (500). At this time, the middleware integrated management server (100) or a web server (not shown) linked thereto may be configured. The middleware integrated management server (100) or the web server linked thereto may include a Linux (Ubuntu, CentOS, etc.) or Windows Server operating system. Additionally, it may include Apache, Nginx, IIS, etc. as web server software. It plays the role of receiving and processing HTTP requests from clients. Additionally, an application server (not shown) may be included and configured. The middleware integrated management server (100) or the web server may forward dynamic requests to the application server without directly processing them. The application server processes business logic and dynamic data. That is, it can perform processing of dynamic pages created with PHP, Python Flask / Django, Node.js, Java Spring, etc. Additionally, it may include a database (DBMS) such as MySQL, PostgreSQL, MongoDB, etc., to store and manage the received and processed data. The middleware integrated management server (100) or web server may include a configuration for providing security software such as an SSL / TLS certificate (provided by HTTPS), a firewall, and access control functions. The middleware integrated management server (100) or web server may be a Web Application Server (WAS) in which the functions of a web server and an application server are integrated.

[0049] As such, the present invention enables integrated and efficient management of whether each middleware server is operating normally in an environment where multiple middleware servers are operated.

[0050] The embodiments of the present invention will be described in more detail below.

[0051] FIG. 2 is a block diagram showing the configuration of a middleware integrated management server (100) according to one embodiment of the present invention.

[0052] Referring to FIG. 2, a middleware integrated management server (100) according to one embodiment of the present invention includes a communication unit (110) and a processor (120). As previously explained, parts that are not directly related to the configuration for explaining the technical features of the present invention in the drawings have been omitted. A person skilled in the art can understand the technical features of the present invention, including the hardware and software configurations basically required for the server (100) to operate, through the contents of this specification.

[0053] The communication unit (110) communicates with a plurality of middleware servers (200-1, 200-2, ..., 200-n), a storage (300), a plurality of linked servers / DBs (400-1, 400-2, ..., 400-m), and an administrator terminal (500) to transmit and receive data. In particular, the communication unit (110) collects middleware engine data at predetermined time intervals or when a preset event occurs by a data collection process operating in each of the plurality of middleware servers (200-1, 200-2, ..., 200-n), and then receives the middleware engine data or data processed from it through a message queue.

[0054] The processor (120) can control the operation of the middleware integrated management server (100) and control or support the operation of other servers and devices connected to the middleware integrated management server (100).

[0055] In one embodiment of the present invention, the processor (120) maps data received from a plurality of middleware servers (200-1, 200-2, ..., 200-n) to corresponding management identification information and stores it in a storage (300), and verifies the stored data to support checking whether the middleware operates normally in the plurality of middleware servers (200-1, 200-2, ..., 200-n).

[0056] FIG. 3 is a schematic diagram showing the middleware management process of a middleware server (200-1, 200-2, ..., 200-n) according to one embodiment of the present invention.

[0057] Referring further to FIG. 3, the data collection process can be executed based on a task script written on each of the multiple middleware servers (200-1, 200-2, ..., 200-n). The task script can be created on the middleware integration management server (100) and distributed to each of the multiple middleware servers (200-1, 200-2, ..., 200-n). It can be distributed directly to each middleware server via SSH, FTP, or SCP, or automatically transmitted to Ansible, Jenkins, or CI / CD pipelines. Alternatively, it can be created individually on each of the multiple middleware servers (200-1, 200-2, ..., 200-n) according to standard protocols.

[0058] As illustrated in FIG. 3, each of the multiple middleware servers (200-1, 200-2, ..., 200-n) can execute a task script (also called a task automation script) at predetermined time intervals. By the task script (data collection process) operating at each of the multiple middleware servers (200-1, 200-2, ..., 200-n) at predetermined time intervals, System Configuration data items are collected and specialized according to a predefined format, and based on this, a transmission file, which is the middleware engine data or data processed therefrom, is generated and transmitted to a message queue by a data transmission pipeline.

[0059] Here, System Configuration refers to the overall environment configuration state of a system (server, application, network, OS, etc.), including hardware, software, network settings, and configuration values. In particular, System Configuration may include system information such as the OS, middleware configuration values, and linked system information.

[0060] The operation script (data collection process) creates a transfer file and saves it in a designated directory. Additionally, as shown in FIG. 3, it can check the status of the file transfer agent or pipeline process and perform an operation to restart it if abnormal. The operation script (data collection process) checks whether the transfer is complete.

[0061] At this time, the process of collecting System Configuration data items and specializing them according to a predefined format is performed according to a predefined format at the level of business logic that can affect the performance of the middleware engine.

[0062] FIG. 4 is a schematic diagram showing the transmission process of a data transmission pipeline according to one embodiment of the present invention.

[0063] Referring to FIG. 4, a data transmission pipeline according to one embodiment of the present invention operates continuously and immediately transmits a new transmission file to a message queue when it is detected. The filename of the transmission file that has been transmitted is changed and moved to a transmission completion directory.

[0064] FIG. 5 is a schematic diagram showing the data refinement process of a middleware integrated management server (100) according to one embodiment of the present invention.

[0065] Referring to FIG. 5, a processor (120) of a middleware integrated management server (100) according to an embodiment of the present invention can perform integrity verification based on the number of System Configuration data items included in a transmission file. The processor (120) can determine the number of System Configuration data items that have been transmitted by separating the System Configuration data items included in the transmission file with a delimiter. If the number of identified data items is less than a preset value, it can be determined that the data transmission was not properly performed because the data integrity is compromised.

[0066] Meanwhile, the number of System Configuration data items may be included as a separate item in the transmission file. The processor (120) can verify data integrity by comparing the number of items included in the System Configuration data items with the number of items obtained by subtracting 1 from the number of identified data items.

[0067] If the number of identified data items exceeds a preset value, there is a high probability of duplicate data existing, so a process to check for data duplication may be performed. If duplicates are confirmed, while it is unlikely that data integrity will be compromised, there may be a problem with the transmission system itself, so the person in charge of the transmission system may be notified.

[0068] However, integrity verification based on the number of data items may make it difficult to accurately determine data tampering, particularly partial omissions. Therefore, data omission verification can be performed as a supplement. Since verifying all data can increase system load and management costs, the data subject to verification can be specified. For example, version information, which poses a high risk of mismanagement if System Configuration data items are transmitted incorrectly, can be verified. Generally, version information consists of multiple single-digit numbers separated by periods; therefore, data omission verification can be performed based on the number of digits and periods constituting the version information.

[0069] When the integrity verification is complete, the processor (120) controls the received transmission file to be parsed as JSON and mapped to management identification information and stored in the storage (300). Here, the management identification information (key) may be information including a middleware management host, a business code, a business logic code, and a port number.

[0070] FIG. 6 is a schematic diagram showing the middleware management process of a middleware integrated management server (100) according to one embodiment of the present invention.

[0071] The data collection process can be executed based on job scripts written on each of the multiple middleware servers (200-1, 200-2, ..., 200-n). Job scripts can be created on the middleware integration management server (100) and distributed to each of the multiple middleware servers (200-1, 200-2, ..., 200-n). They can be distributed directly to each middleware server via SSH, FTP, or SCP, or automatically transmitted to Ansible, Jenkins, or CI / CD pipelines. Alternatively, they can be created individually on each of the multiple middleware servers (200-1, 200-2, ..., 200-n) according to standard protocols.

[0072] As illustrated in FIG. 6, each of the multiple middleware servers (200-1, 200-2, ..., 200-n) can execute a task script (also called a task automation script). When a preset event occurs, middleware configuration data is collected as middleware engine data by a data collection process operating in each of the multiple middleware servers (200-1, 200-2, ..., 200-n) and can be compared with previously recorded configuration data.

[0073] If the task script determines that there is a change in the data, it copies the collected configuration data to a temporary path (specified directory) for transmission and saves it, and may append the 'modify time' of the configuration file to the end of the filename. As shown in FIG. 6, it can perform an action to check the status of the file transfer agent or pipeline process and restart it if it is abnormal.

[0074] As described above, the data transmission pipeline according to one embodiment of the present invention operates continuously and immediately transmits a new transmission file (new configuration data) to a message queue when it is detected. The filename of the transmission file is changed to indicate that the transmission is complete.

[0075] FIGS. 7 and 8 are schematic diagrams illustrating the data refinement process of a middleware integrated management server (100) according to one embodiment of the present invention.

[0076] Referring to FIGS. 7 and 8, a processor (120) of a middleware integrated management server (100) according to one embodiment of the present invention can set the name and storage path of a new file based on the middleware management host and middleware engine names included in the header of a transmission file. The name of the new file can be a key for data identification and retrieval.

[0077] Additionally, the processor (120) can generate data for a new file based on the content of the transmitted file, and restore the newly restored files by sorting the order among them using the line numbers of the content.

[0078] Multiple configuration files from various middleware servers can be stored in a mixed state in the message queue. Before a file is sent, line numbers are attached to its content to determine the order among the files. This is because the state of each middleware server (200-1, 200-2, ..., 200-n) may differ depending on the order in which configuration data is changed, and multiple middleware servers (200-1, 200-2, ..., 200-n) may have dependencies on each other or on other linked servers / DBs.

[0079] Meanwhile, the message queue may vary depending on the type of collected middleware engine data. That is, the processor (120) can control receiving middleware engine data or data processed therefrom through a different message queue corresponding to the type of collected middleware engine data.

[0080] The types of middleware engine data can be classified based on at least some of the following: System Configuration data, configuration data, the function of each middleware, the workload of each middleware server, whether each middleware has failed, and the performance of each middleware server. For example, System Configuration data and configuration data may be transmitted through separate message queues. Additionally, if a middleware server has a high workload, experiences a failure, or has relatively low performance, load balancing may be performed using predefined message queues.

[0081] Meanwhile, the processor (120) can control the middleware server (200-1, 200-2, ..., 200-n) to determine the state based on whether at least some of the values ​​of the data stored as above exceed a predetermined standard.

[0082] Additionally, the processor (120) can determine whether the operation status of the middleware servers (200-1, 200-2, ..., 200-n) is normal by periodically checking whether data collection (engine, environment, etc.) is taking place.

[0083] However, the processor (120) may determine the middleware server to be normal even if it exceeds a predetermined standard, provided that an exception flag is processed. For example, if data collection is not performed because a specific system is in operation, or if the collected data is not within an appropriate range, the exception flag can be checked to determine whether it is normal or pending. In this case, it is also possible to determine if it is abnormal if the set exception period has ended.

[0084] Additionally, the processor (120) can provide the judgment result to the administrator terminal (10) to support verification of whether the middleware is operating normally on the middleware server. That is, the processor (120) can provide a user screen that allows viewing middleware engine information, configuration information, a list of managed systems, a list of middleware engine administrators, additional information, special notes, engine operation statistics, history, etc. At this time, a customized screen may be provided according to the user type. For example, a user screen for managing a specific service may provide information related to that service.

[0085] A processor (120) of a middleware integrated management server (100) according to one embodiment of the present invention can support the provision of a UX interface on an administrator terminal (10) that illustrates an architecture block of at least one middleware server and a server associated therewith.

[0086] At this time, the processor (120) can display whether normal operation is occurring on the architecture block through a UX interface and support an administrator in clicking on a specific area to handle exception flags for a specific system. Through this, the administrator can intuitively monitor the status of the middleware server.

[0087] Meanwhile, the aforementioned data collection process can operate based on a task script written with abstracted common commands. In this case, the task script distributed to multiple middleware servers (200-1, 200-2, ..., 200-n) is converted and executed on each individual middleware server to suit a specific system environment. The overall administrator distributing the task script writes the task script using common commands in a standardized format, and since each of the multiple middleware servers (200-1, 200-2, ..., 200-n) automatically converts the script into a command format suitable for each middleware server environment through a conversion module, efficient management of the multiple middleware servers (200-1, 200-2, ..., 200-n) becomes possible.

[0088] In addition, when executing work scripts on each middleware server (200-1, 200-2, ..., 200-n), data collection commands can be executed under predefined common conditions according to standardized script metadata. That is, by defining a series of work sets and conditions by structured metadata for each work and executing data collection commands based on this, the management efficiency of multiple middleware servers (200-1, 200-2, ..., 200-n) can be maximized.

[0089] FIG. 9 is a flowchart illustrating a middleware integration management method according to one embodiment of the present invention.

[0090] Referring to FIG. 9, a middleware integrated management method according to one embodiment of the present invention comprises: (a) a step of receiving middleware engine data or data processed therefrom through a message queue after middleware engine data is collected at predetermined time intervals or when a preset event occurs by a data collection process operating on each of a plurality of middleware servers (S910); (b) a step of storing the received data in a storage by mapping it to corresponding management identification information (S920); and a step of verifying the stored data to support checking whether the middleware operates normally on the plurality of middleware servers (S930).

[0091] At this time, in step (a) above, System Configuration data items are collected by a data collection process operating at each of the plurality of middleware servers at predetermined time intervals and specialized according to a predefined format, and based thereon, when a transmission file is generated which is the middleware engine data or data processed therefrom, transmission to the message queue can be performed by the data transmission pipeline.

[0092] In addition, the above data specialization can be performed according to a predefined format at the level of business logic that may affect the performance of the middleware engine.

[0093] Additionally, the above step (b) may include (b1) a step of performing an integrity verification based on the number of System Configuration data items included in the transmission file, and (b1) a step of parsing the received transmission file and mapping it to management identification information and storing it in a storage when the integrity verification is completed.

[0094] In addition, the above management identification information may be information including a middleware management host, a business code, a business logic code, and a port number.

[0095] In addition, in step (a) above, when a preset event occurs, middleware configuration data is collected as middleware engine data by a data collection process operating on each of the plurality of middleware servers, and when it is determined that there is a change in data as a result of comparing it with previously recorded configuration data, new configuration data—referred to as a 'transmission file'—can be transmitted to the message queue as the middleware engine data or data processed therefrom by a data transmission pipeline.

[0096] Additionally, the above step (b) may include: (b3) a step of setting the name and storage path of a new file based on the middleware management host and middleware engine names included in the header of the transmission file; and (b4) a step of generating data of the new file based on the content of the transmission file, and restoring the transmission file to the new file by aligning the data lines within the new file using the line numbers of the content.

[0097] Additionally, the above step (a) includes receiving the middleware engine data or data processed therefrom through a different message queue corresponding to the type of the collected middleware engine data, and the type of the middleware engine data may be classified based on at least some of System Configuration data, configuration data, the function of each middleware, the workload of each middleware server, whether a failure has occurred in each middleware, and the performance of each middleware server.

[0098] Additionally, the above step (c) includes (c1) a step of determining the status of the middleware server based on whether at least some of the values ​​of the stored data exceed a predetermined standard, and (c2) a step of providing the determination result to a user to support checking whether the middleware is operating normally in the middleware server, and the above step (c1) can determine the middleware server to be normal even if the predetermined standard is exceeded, provided that an exception flag is processed.

[0099] Additionally, the above step (c) may include: (c3) a step of supporting the provision of a UX interface that illustrates at least one middleware server and an architecture block of a server associated therewith on an administrator terminal; and (c4) a step of supporting the display of normal operation on the architecture block through the UX interface and enabling an administrator to click a specific area to perform exception flag processing for a specific system.

[0100] In addition, in step (a) above, the data collection process operates based on a task script written with abstracted common commands, and the task script distributed to the plurality of middleware servers is converted and executed on individual middleware servers to suit a specific system environment, and when the task script is executed, the data collection command can be executed under predefined common conditions according to standardized script metadata.

[0101] Although the present invention has been described above by limited embodiments and drawings, the present invention is not limited thereto, and it is obvious that various modifications and variations are possible within the scope of the technical spirit of the present invention and the equivalent scope of the claims described below by those skilled in the art to which the present invention belongs. Explanation of the symbols

[0102] 1000 : Middleware Integrated Management System 100 : Middleware Integration Management Server 200-1, 200-2, ..., 200-n : Middleware Servers 300 : Storage 400-1, 400-2, ..., 400-m : Linked Server / DB 500 : Administrator Terminal 10 : Administrator

Claims

Claim 1 A method for integrated middleware management of a server comprises: (a) collecting middleware engine data at predetermined time intervals or upon the occurrence of a preset event by a data collection process operating on each of a plurality of middleware servers, and receiving said middleware engine data or data processed therefrom through a message queue; (b) mapping said received data to corresponding management identification information and storing it in a storage; and (c) verifying said stored data to support checking whether the middleware is operating normally on the plurality of middleware servers, wherein in step (a), the data collection process operates based on a task script written with abstracted common commands, the task script distributed to the plurality of middleware servers is converted and executed on individual middleware servers to suit a specific system environment, and when the task script is executed, a data collection command is executed under preset common conditions according to standardized script metadata. Claim 2 A method according to claim 1, wherein in step (a), System Configuration data items are collected by a data collection process operating at each of the plurality of middleware servers at predetermined time intervals, specialized according to a predefined format, and a transmission file, which is the middleware engine data or data processed therefrom, is generated based thereon, and then transmitted to the message queue by a data transmission pipeline. Claim 3 In paragraph 2, the data specialization is performed according to a predefined format in business logic units that may affect the performance of the middleware engine. Claim 4 In paragraph 3, the above step (b) comprises: (b1) a step of performing an integrity verification based on the number of System Configuration data items included in the transmission file; and (b1) a step of parsing the received transmission file and mapping it to management identification information and storing it in a storage when the integrity verification is completed. Claim 5 In paragraph 4, the method wherein the management identification information is information including a middleware management host, a business code, a business logic code, and a port number. Claim 6 A method according to claim 1, wherein, in step (a), when a preset event occurs, middleware configuration data is collected as middleware engine data by a data collection process operating on each of the plurality of middleware servers and, as a result of comparing it with previously recorded configuration data, when it is determined that there is a change in data, new configuration data—referred to as a 'transmission file'—is transmitted to the message queue by a data transmission pipeline as the middleware engine data or data processed therefrom. Claim 7 In claim 6, the above step (b) comprises: (b3) setting the name and storage path of a new file based on the middleware management host and middleware engine names included in the header of the transmission file; and (b4) generating data of the new file based on the content of the transmission file, and restoring the newly restored files by sorting the order among them using the line numbers of the content. Claim 8 A method according to claim 1, wherein step (a) comprises receiving the middleware engine data or data processed therefrom through different message queues corresponding to the type of the collected middleware engine data, and the type of the middleware engine data is classified based on at least some of System Configuration data, configuration data, the function of each middleware, the workload of each middleware server, whether each middleware has failed, and the performance of each middleware server. Claim 9 In claim 1, the step (c) comprises: (c1) a step of determining the state of the middleware server based on whether at least some of the values ​​of the stored data exceed a predetermined standard; and (c2) a step of providing the determination result to a user to support checking whether the middleware is operating normally in the middleware server, wherein the step (c1) determines the middleware server to be normal even if the predetermined standard is exceeded, provided that an exception flag is processed. Claim 10 A method according to claim 1, wherein step (c) comprises: (c3) supporting the provision of a UX interface on an administrator terminal that illustrates an architecture block of at least one middleware server and a server associated therewith; and (c4) supporting the display of normal operation status on the architecture block through the UX interface and enabling an administrator to click a specific area to perform exception flag processing for a specific system. Claim 11 delete Claim 12 A middleware integrated management server comprising: a communication unit that receives middleware engine data or data processed therefrom through a message queue after middleware engine data is collected at predetermined time intervals or upon the occurrence of a preset event by a data collection process operating on each of a plurality of middleware servers; and a processor that maps the received data to corresponding management identification information and stores it in a storage, and verifies the stored data to support checking whether the middleware operates normally on the plurality of middleware servers, wherein the data collection process operates based on a task script written with abstracted common commands, the task script distributed to the plurality of middleware servers is converted and executed on individual middleware servers to suit a specific system environment, and when the task script is executed, a data collection command is executed under preset common conditions according to standardized script metadata.

Images