Open source middleware life cycle management platform system and method

Abstract

The invention relates to an open source middleware life cycle management platform system and method. The platform system comprises a system service module used for realizing account management, parameter management, role management, authority management, monitoring task distribution and collector monitoring functions; the middleware management service module is used for realizing middleware application, middleware query, acquisition task configuration and baseline version management functions; the monitoring alarm service module is used for realizing monitoring data processing and middleware alarm functions; the monitoring acquisition service module is used for realizing a monitoring data acquisition function; the report service module is used for realizing report query and report downloading functions; the interface service module is used for achieving the functions of middleware starting, middleware stopping, middleware installing, middleware unloading, service account number creating, environment variable configuring, CMDB synchronizing and user message pushing. Compared with the prior art, full-life-cycle management of various open source middleware can be achieved, the operation and maintenance management efficiency is improved, and standardized configuration is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of middleware operation and maintenance management, and in particular to an open source middleware lifecycle management platform system and method. Background Art

[0002] With the development of enterprise business and the increase in the construction of new systems, the types of middleware products and the number of nodes used are increasing. The main problems at present are: first, it is difficult to standardize the use of versions. There are many types of open source middleware, and there are many versions in use. In the daily operation and maintenance process, there is a certain difficulty in controlling the middleware version; second, it is difficult to unify the configuration standards. There are many types of open source middleware, and the baseline configuration (security baseline and configuration baseline) standards and specifications have not been solidified through the platform, making it difficult to manage and strictly unify; third, there is no service display view. There are many types of open source middleware applications, and there is no unified service information display window that can display the operating status and information of all middleware in real time, which is not convenient for global monitoring and statistics of middleware nodes; fourth, there is no complete application view. For each application system, there is no complete middleware view to display the middleware nodes under this application system.

[0003] Currently, the management of open source middleware mainly relies on manual maintenance by operation and maintenance personnel, who manually complete the installation, deployment, management, configuration and delivery processes. As the scale of middleware reaches thousands of sets, the manual operation of technicians has problems such as low efficiency and inability to perform batch operations, and is dependent on the technical level of manual operation. In addition, manual installation, deployment and configuration management cannot unify and solidify baseline standards, resulting in inconsistent configuration. Summary of the invention

[0004] The purpose of the present invention is to overcome the defects of the above-mentioned prior art and to provide an open source middleware lifecycle management platform system and method, which can realize the full lifecycle management of various open source middleware, improve the operation and maintenance management efficiency and realize standardized configuration.

[0005] The purpose of the present invention can be achieved through the following technical solutions: an open source middleware lifecycle management platform system, including a system service module, a middleware management service module, a monitoring alarm service module, a monitoring collection service module, a report service module and an interface service module, wherein the system service module is used to implement account management, parameter management, role management, authority management, monitoring task dispatching, and collector monitoring functions;

[0006] The middleware management service module is used to implement middleware application, middleware query, collection task configuration, and baseline version management functions;

[0007] The monitoring alarm service module is used to realize monitoring data processing and middleware alarm functions;

[0008] The monitoring and collection service module is used to realize the monitoring data collection function;

[0009] The report service module is used to realize report query and report download functions;

[0010] The interface service module is used to implement middleware startup, middleware stop, middleware installation, middleware uninstallation, service account creation, environment variable configuration, CMDB (Configuration Management Database) synchronization, and user message push functions.

[0011] Furthermore, the open source middleware lifecycle management platform system is interconnected with the technical center, CMDB system, and automated operation platform system respectively to perform corresponding data transmission and interaction.

[0012] Furthermore, the open source middleware lifecycle management platform system is specifically developed based on the spring-boot and spring-cloud frameworks.

[0013] A method for managing the life cycle of open source middleware includes a middleware application and installation process, a middleware offline process, a middleware startup process, a middleware stop process, a middleware parameter management process, a middleware log management process and a middleware backup management process.

[0014] Furthermore, the middleware application and installation process is: obtaining the middleware application information submitted by the user, pushing the middleware application approval message, obtaining the approval instruction, performing the installation environment verification, generating the middleware installation work order, and calling the middleware installation work order to install the middleware.

[0015] Furthermore, the middleware application information includes: the business system to which the middleware belongs, the server to which the middleware belongs, the associated CMDB host name, IP address, application system name, operation and maintenance person in charge information, and middleware version information.

[0016] Further, the process of calling the middleware installation work order to install the middleware includes: executing an automated operation to complete the standardized installation of the middleware;

[0017] Manage middleware user privileges and scan and write middleware information into CMDB for management;

[0018] Notify the management platform that the system is installed and then push relevant messages to notify users;

[0019] Obtain the user's online confirmation instruction, and then complete the monitoring installation and configuration.

[0020] Furthermore, the middleware offline process includes: obtaining the middleware offline information submitted by the user, pushing the middleware offline approval message, obtaining the approval instruction, generating the middleware offline work order, and calling the middleware offline work order to perform the middleware offline processing;

[0021] The middleware offline processing process includes: monitoring offline review and middleware monitoring deletion;

[0022] Cancel the management of middleware user privileges and update of middleware information CMDB management status;

[0023] The notification management platform system is offline and then pushes relevant messages to notify users.

[0024] Furthermore, the middleware startup process includes: obtaining the middleware startup information and the service order number submitted by the user, verifying the service order number format, and calling an automated job to start the middleware;

[0025] Get the callback of the execution result of the automated job. If it is displayed that the process management is not started, call the automated job to start the process management. After the process management is successfully started, call the automated job again to start the middleware, get the callback result and modify the middleware display status.

[0026] Furthermore, the middleware stopping process includes: obtaining the middleware stopping information and the service order number submitted by the user, verifying the service order number format, and calling an automated job to stop the middleware;

[0027] Get the callback of the execution result of the automated job. If it is displayed that the process management is not started, call the automated job to start the process management. After the process management is successfully started, call the automated job again to stop the middleware, get the callback result and modify the middleware display status.

[0028] Furthermore, the middleware parameter management process includes: obtaining user configuration modification information, middleware parameter corresponding field modification information and change order number, calling the corresponding automated job to modify the parameters, obtaining the execution result, and if the execution is successful, modifying the platform display information, otherwise ending the current process.

[0029] Compared with the prior art, the present invention has the following advantages:

[0030] The invention designs an open source middleware lifecycle management platform system, which includes a system service module, a middleware management service module, a monitoring and alarming service module, a monitoring and collecting service module, a report service module and an interface service module. The system service module is used to realize account management, parameter management, role management, authority management, monitoring task dispatching and collector monitoring functions; the middleware management service module is used to realize middleware application, middleware query, collecting task configuration and baseline version management functions; the monitoring and alarming service module is used to realize monitoring data processing and middleware alarm functions; the monitoring and collecting service module is used to realize monitoring data collection functions; the report service module is used to realize report query and report download functions; the interface service module is used to realize middleware startup, middleware stop, middleware installation, middleware uninstallation, service account creation, environment variable configuration, CMDB synchronization and user message push functions. Thus, a unified open source middleware management platform is established, which can realize the full lifecycle management of multiple open source middleware, realize standardized configuration, version management, centralized service information display window, improve middleware lifecycle control and realize complete link tracking.

[0031] The present invention connects the open source middleware lifecycle management platform system with the technical middle platform, CMDB system, and automated operation platform system respectively to perform corresponding data transmission interaction, and designs an open source middleware lifecycle management method including middleware application and installation process, middleware offline process, middleware startup process, middleware stop process, middleware parameter management process, middleware log management process, and middleware backup management process, which can better manage middleware version information, monitor middleware running status, standardize middleware online and offline processes, decouple business from basic system services, greatly improve middleware operation and maintenance management efficiency, and reduce management costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a schematic diagram of the system structure of the present invention;

[0033] Figure 2 A schematic diagram of the system architecture constructed in the embodiment;

[0034] Figure 3 This is a schematic diagram of the middleware application and installation process in the embodiment;

[0035] Figure 4 This is a schematic diagram of the middleware offline process in the embodiment;

[0036] Figure 5 This is a schematic diagram of the middleware startup process in the embodiment;

[0037] Figure 6 This is a schematic diagram of the middleware stopping process in the embodiment;

[0038] Figure 7This is a schematic diagram of the middleware parameter management process in the embodiment;

[0039] Explanation of the marks in the figure: 101. System service module, 102. Middleware management service module, 103. Monitoring and alarm service module, 104. Monitoring and collection service module, 105. Report service module, 106. Interface service module, 2. Technical middle platform, 3. CMDB system, 4. Automated operation platform system. DETAILED DESCRIPTION

[0040] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0041] Example

[0042] like Figure 1 As shown, an open source middleware lifecycle management platform system includes a system service module 101, a middleware management service module 102, a monitoring alarm service module 103, a monitoring collection service module 104, a report service module 105 and an interface service module 106. The system service module 101 is used to implement account management, parameter management, role management, authority management, monitoring task dispatching, and collector monitoring functions;

[0043] The middleware management service module 102 is used to implement middleware application, middleware query, collection task configuration, and baseline version management functions;

[0044] The monitoring and alarm service module 103 is used to implement monitoring data processing and middleware alarm functions;

[0045] The monitoring and collection service module 104 is used to realize the monitoring data collection function;

[0046] The report service module 105 is used to implement report query and report download functions;

[0047] The interface service module 106 is used to implement middleware startup, middleware stop, middleware installation, middleware uninstallation, service account creation, environment variable configuration, CMDB synchronization, and user message push functions.

[0048] The above-mentioned open source middleware lifecycle management platform system is respectively interconnected with the technical center 2, CMDB system 3, and automated operation platform system 7 to perform corresponding data transmission and interaction.

[0049] The above platform system is applied to implement an open source middleware lifecycle management method, including the middleware application and installation process, the middleware offline process, the middleware startup process, the middleware stop process, the middleware parameter management process, the middleware log management process and the middleware backup management process.

[0050] In this embodiment, the open source middleware lifecycle management platform system is specifically developed based on the spring-boot and spring-cloud frameworks. Figure 2 As shown, the main functions of the platform are decoupled according to microservices, and at the same time rely on the technical middle platform to implement service governance, link tracking, and centralized configuration management. Users can perform corresponding operations on the developed software interaction page and obtain the management status information of the middleware in a timely manner.

[0051] In actual applications, the above open source middleware management platform can realize the full life cycle management of various open source middleware such as Tomcat, JDK, Nginx, RabbitMQ, Zookeeper, Kafka, Filebeat, ElasticSearch, etc. This embodiment takes Tomcat middleware as an example to explain the platform management process in detail from the user operation perspective:

[0052] 1. Middleware Application and Installation

[0053] like Figure 3 As shown, the user clicks the middleware application button on the middleware management page, selects the business system and server to which he is responsible, automatically fills in the CMDB host name, IP address, application system abbreviation, first person in charge of operation and maintenance, second person in charge information, selects JDK version, Tomcat version, if multiple middlewares need to be applied, clicks Continue to add, fills in correctly, and clicks Submit. Enter the subsequent middleware approval link.

[0054] After the middleware is approved, the system automatically calls the middleware installation work order corresponding to the process engine to install the middleware. The specific process of the work order is: automated operation (standardized installation of middleware) - middleware user privilege management - user information CMDB management - automated operation (middleware information scanning) - notification of middleware platform installation completion - email notification to users - online confirmation - monitoring addition review - adding monitoring. After receiving the work order completion notification, the platform obtains the latest node information and manages it.

[0055] 2. Middleware offline

[0056] like Figure 4 As shown, the middleware approval administrator receives an email notification and logs into the system to view pending tasks. The platform displays pending approvals. Click Display to display specific middleware application information. Click the Approve button to fill in the information. You can also check the checkbox for batch approval.

[0057] 3. Middleware startup

[0058] like Figure 5As shown in the figure, after the middleware is managed, the user can see the newly added node on the corresponding type of middleware management page. According to the node health status obtained from the monitoring platform, if the middleware process is started, the status is green, if the process is stopped, the status is red, and if the status cannot be obtained, it is gray. If the status is red or gray, the start button is displayed. After the user clicks the start button, he needs to enter the service order number. The platform verifies the service order number format and calls the automated job: middleware start.

[0059] The platform obtains the callback of the execution result of the automated job. If it shows that the Supervisor (process management) is not started, the automated job: Supervisor start is called. After the startup is successful, the automated job: middleware start is called again to obtain the callback result and modify the middleware display status. The batch startup function is supported.

[0060] 4. Middleware Stop

[0061] like Figure 6 As shown, if the intermediate status is displayed in green or gray, a stop button is displayed. After the user clicks the stop button, he needs to enter the service order number. The platform verifies the service order number format and calls the automated job: middleware stop. The platform obtains the callback of the automated job execution result. If it shows that Supervisor is not started, the automated job: Supervisor start is called. After the startup is successful, the automated job: middleware stop is called again to obtain the callback result and modify the middleware display status. The batch selection stop function is supported.

[0062] 5. Middleware parameter management

[0063] like Figure 7 As shown, the user clicks the middleware button on the management page, and the specific configuration parameter information of the node pops up. Click Modify Configuration to modify the various fields under JVM parameters and Tomcat parameters. After saving, call the corresponding automated job to modify the parameters. If the execution is successful, modify the platform display information. You can also check multiple middlewares and click the button to batch modify the parameters.

[0064] 6. Middleware log management

[0065] The user clicks the middleware node configuration button on the page, a configuration page pops up, clicks log management related functions, calls automated jobs, and views middleware related logs (access logs, crash logs).

[0066] 7. Middleware backup management

[0067] The user clicks the middleware node configuration button on the page, a configuration page pops up, clicks backup and enters backup information, calls the automated job to perform the middleware backup, and can click the rollback button to roll back the version or delete the backup.

[0068] In summary, this solution can achieve the full life cycle management of multiple open source middleware such as Tomcat, JDK, Nginx, RabbitMQ, Zookeeper, Kafka, Filebeat, ElasticSearch, etc. by establishing a unified open source middleware management platform, realize standardized configuration, version management, centralized service information display window, improve middleware life cycle control, complete link tracking, and better support business development. On the one hand, it can improve efficiency, speed up resource delivery / recovery speed, reduce the delivery cycle of operations to minutes, improve operation and maintenance efficiency, and reduce the time unit to minutes for application, approval, installation and deployment, service start and stop platform and visualization; on the other hand, it can reduce costs, visualize the utilization rate of hardware resources, promote reasonable allocation of resources, reduce hardware costs, one-click, visualized, platform-based operation and maintenance operations, and reduce operation and maintenance management costs; in addition, it can also strengthen management, strengthen and unify middleware configuration standards and specifications, and solidify them through the platform.

Claims

1. An open source middleware lifecycle management platform system, characterized in that: It comprises a system service module (101), a middleware management service module (102), a monitoring alarm service module (103), a monitoring collection service module (104), a report service module (105) and an interface service module (106), wherein the system service module (101) is used to implement account management, parameter management, role management, authority management, monitoring task dispatching and collector monitoring functions; The middleware management service module (102) is used to implement middleware application, middleware query, collection task configuration, and baseline version management functions; The monitoring alarm service module (103) is used to realize monitoring data processing and middleware alarm functions; The monitoring and collection service module (104) is used to realize the monitoring data collection function; The report service module (105) is used to realize report query and report download functions; The interface service module (106) is used to implement middleware startup, middleware stop, middleware installation, middleware uninstallation, service account creation, environment variable configuration, CMDB synchronization, and user message push functions.

2. The open source middleware lifecycle management platform system according to claim 1, characterized in that: The open source middleware lifecycle management platform system is interconnected with the technical center (2), the CMDB system (3), and the automated operation platform system (4) respectively to perform corresponding data transmission interaction; The open source middleware lifecycle management platform system is specifically developed based on the spring-boot and spring-cloud frameworks.

3. An open source middleware lifecycle management method, applied to an open source middleware lifecycle management platform system as claimed in claim 1, characterized in that: It includes the middleware application and installation process, the middleware offline process, the middleware startup process, the middleware stop process, the middleware parameter management process, the middleware log management process and the middleware backup management process.

4. The open source middleware lifecycle management method according to claim 3, characterized in that: The middleware application and installation process is as follows: obtaining the middleware application information submitted by the user, pushing the middleware application approval message, obtaining the approval instruction, performing the installation environment verification, generating the middleware installation work order, and calling the middleware installation work order to install the middleware.

5. The open source middleware lifecycle management method according to claim 4, characterized in that: The middleware application information includes: the business system to which the middleware belongs, the server to which the middleware belongs, the associated CMDB host name, IP address, application system name, operation and maintenance person in charge information, and middleware version information.

6. The open source middleware lifecycle management method according to claim 4, characterized in that: The process of calling the middleware installation work order to install the middleware includes: executing an automated operation to complete the standardized installation of the middleware; Manage middleware user privileges and scan and write middleware information into CMDB for management; Notify the management platform that the system is installed and then push relevant messages to notify users; Obtain the user's online confirmation instruction, and then complete the monitoring installation and configuration.

7. The open source middleware lifecycle management method according to claim 3, characterized in that: The middleware offline process includes: obtaining the middleware offline information submitted by the user, pushing the middleware offline approval message, obtaining the approval instruction, generating the middleware offline work order, and calling the middleware offline work order to perform the middleware offline processing; The middleware offline processing process includes: monitoring offline review and middleware monitoring deletion; Cancel the management of middleware user privileges and update of middleware information CMDB management status; The notification management platform system is offline and then pushes relevant messages to notify users.

8. The open source middleware lifecycle management method according to claim 3, characterized in that: The middleware startup process includes: obtaining the middleware startup information and service order number submitted by the user, verifying the service order number format, and calling an automated job to start the middleware; Get the callback of the execution result of the automated job. If it is displayed that the process management is not started, call the automated job to start the process management. After the process management is successfully started, call the automated job again to start the middleware, get the callback result and modify the middleware display status.

9. The open source middleware lifecycle management method according to claim 3, characterized in that: The middleware stopping process includes: obtaining the middleware stopping information and the service order number submitted by the user, verifying the service order number format, and calling an automated operation to stop the middleware; Get the callback of the execution result of the automated job. If it is displayed that the process management is not started, call the automated job to start the process management. After the process management is successfully started, call the automated job again to stop the middleware, get the callback result and modify the middleware display status.

10. The open source middleware lifecycle management method according to claim 3, characterized in that: The middleware parameter management process includes: obtaining user configuration modification information, middleware parameter corresponding field modification information and change order number, calling the corresponding automated job to modify the parameters, obtaining the execution result, and if the execution is successful, modifying the platform display information, otherwise ending the current process.

Images