Operation and maintenance method and device for maintaining middleware License, equipment and storage medium
Through the automated middleware license operation and maintenance method, the complex license management challenges faced by middleware operation and maintenance personnel are solved, efficient license management and compliance inspection are achieved, and operation and maintenance costs are reduced.
Patent Information
- Application Number
- CN202510115187.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-24
- Publication Date
- 2025-05-27
AI Technical Summary
Middleware operation and maintenance personnel face complex license management challenges, including management of multiple licensing models, compliance inspection, license renewal and upgrade, resulting in inefficiency and increased costs.
It provides an automated middleware license operation and maintenance method. Through the license adapter and control center, it realizes tasks such as middleware license collection, detection, early warning, and update, reducing manual intervention and improving operation and maintenance efficiency.
It realizes automation of middleware license management, improves operation and maintenance efficiency and system performance, reduces operation and maintenance costs, and ensures compliance with middleware usage.
Smart Images

Figure CN120045207A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the operation and maintenance field of maintaining middleware License, and particularly to an operation and maintenance method, device, equipment and storage medium for maintaining middleware License. Background Art
[0002] Middleware is an important component in software development. When in use, the supplier needs to control the scope of software use to ensure that users use the software according to the purchased License quantity and usage rights. The License of middleware has the following characteristics:
[0003] 1. Diverse authorization methods: Middleware License supports multiple authorization methods, such as pre-authorization, temporary authorization, and formal authorization, etc. These authorization methods can meet the needs of different users, and at the same time provide flexible authorization management means for middleware suppliers. For middleware users or maintainers, they need to invest energy in maintaining the authorization methods of different middleware instances.
[0004] Pre-authorization: Usually used for trial versions. When the middleware medium leaves the factory, it carries the License authorization of software functions. Users can directly try it, but there are time and function limitations.
[0005] Temporary authorization: To facilitate users to try some software functions that require License authorization, users can obtain temporary authorization by contacting the supplier. There are also time and function limitations.
[0006] Formal authorization: Users need to purchase and install formal authorization to permanently use software functions.
[0007] 2. Cluster authorization: Some middleware products adopt the cluster quantity-based authorization method, that is, to control the number of cloud service clusters. In a cluster environment, middleware software needs to be able to work collaboratively on multiple nodes to provide features such as high availability and load balancing. The cluster quantity-based authorization method can ensure the legal use and effective management of middleware software in a cluster environment.
[0008] There are many types of middleware. In a large business system, multiple service instances of multiple middleware may be used to cooperate to provide services externally. The authorization modes and validity periods of different instances will also be different, which brings greater complexity to middleware operation and maintenance work.
[0009] The complex and diverse License licensing modes of middleware bring various problems and challenges to middleware operation and maintenance personnel. The following are some problems faced by middleware during operation and maintenance:
[0010] 1. Middleware may support multiple license modes, such as commercial licenses, open-source licenses (e.g., Apache, MIT, GPL, etc.), hybrid licenses, etc. Each license mode has its specific terms and restrictions, and operation and maintenance personnel need to deeply understand the content of these license agreements to ensure compliance.
[0011] 2. In large-scale systems, multiple middleware may be used simultaneously, and each middleware may adopt different license modes. Operation and maintenance personnel need to track and manage the license status of these middleware, including license purchase, renewal, upgrade, etc., to ensure the legal operation of the system.
[0012] 3. Operation and maintenance personnel need to ensure that the use of middleware complies with the terms of its license agreement. This includes compliance in aspects such as the number of users, concurrent connection numbers, and function usage restrictions. Violating the license agreement may lead to legal disputes and fines.
[0013] 4. Commercial middleware license agreements require regular license audits and the provision of detailed license usage reports. Operation and maintenance personnel need to prepare these reports and ensure their accuracy and completeness to meet audit requirements.
[0014] 5. As the middleware version is updated and iterated, its license mode may also change. Operation and maintenance personnel need to pay timely attention to these changes and handle license renewal and upgrade work to ensure that the system can continuously obtain technical support and updates.
[0015] 6. Middleware operation and maintenance personnel need to possess cross-domain knowledge and skills, including knowledge in license management, compliance requirements, system architecture, etc. These knowledge and skills help operation and maintenance personnel better understand and solve complex problems in middleware operation and maintenance.
[0016] 7. Operation and maintenance personnel need to closely collaborate with the procurement department to jointly handle tasks such as middleware license purchase and renewal.
[0017] In summary, with the rapid development of enterprise business, the scale and complexity of IT systems are also increasing continuously. There are a wide variety of middleware types and versions used, which pose great challenges to operation and maintenance personnel in manually maintaining middleware licenses. Summary of the Invention
[0018] To better operate and maintain middleware licenses, the present invention provides an operation and maintenance method, device, equipment, and storage medium for maintaining middleware licenses, which can automatically complete tasks such as middleware license collection, detection, warning, and update, can efficiently and accurately complete license management work, reduce the need for manual intervention, thereby accelerating the operation and maintenance speed and improving work efficiency.
[0019] In a first aspect, an operation and maintenance method for maintaining middleware License adopts the following technical solution:
[0020] An operation and maintenance method for maintaining middleware License includes the following steps:
[0021] S1. Collect middleware License and store it;
[0022] S11. The License adapter maintains a timing task to enable the control center to regularly obtain the middleware types managed in the platform, and send the License collection program corresponding to the middleware type to the middleware Agent in each Kubernetes cluster;
[0023] S12. The middleware Agent executes the License collection program to collect the License information of the middleware instance. The License information includes commercial License and open-source License;
[0024] S13. The middleware Agent reports the collected License information of the middleware instance to the control center, and the control center stores the License information in the database;
[0025] S2. Analyze the License information of the middleware instance;
[0026] S21. The License adapter obtains the middleware instance and the corresponding License information in batches from the database through the control center according to the middleware type;
[0027] S22. The License adapter executes the corresponding License parsing program according to the middleware instance type, identifies that the License information is commercial License or open-source License, and extracts the authorization code, time validity period, function authorization, quantity authorization, hardware compatibility information, software compatibility information, dynamic update characteristics, technical support and services from the License information;
[0028] S23. The License adapter analyzes the License information, identifies the items that have affected or will affect the operation of the middleware instance, generates an alarm message and sends it to the middleware maintenance personnel;
[0029] S24. The License adapter updates the analysis result of the License information to the database through the control center, records the error information that appears during the process of analyzing the License information, and generates an error report.
[0030] Preferably, it further includes the following steps:
[0031] S3. Batch update middleware License;
[0032] S31. Obtain the basic parameters required for the middleware to apply for a License within the License adapter;
[0033] S32. The License adapter distributes the corresponding information collection program to the Agent of the corresponding Kubernetes cluster according to the middleware instance type to be updated, and collects the basic information of the middleware instance;
[0034] S33. Batch download the basic information collected in S32 through the platform, apply for or purchase middleware License according to the requirements of the License, and batch upload the License to the control center through the middleware management platform;
[0035] S34. The control center distributes the License to the License adapter, and the License adapter parses the License and obtains the device serial number and MAC from the License to identify the mapping relationship between the License and the middleware instance;
[0036] S35. The License adapter distributes the License, middleware instance and License update program to the corresponding middleware Agent through the control center. The middleware Agent executes the License update program, completes the License update according to the License update program, and determines whether to restart the middleware instance according to the License update program.
[0037] Preferably, the basic information in S32 includes hardware serial number, MAC address, middleware instance version number, operating system information, authorized quantity, and authorized period.
[0038] Preferably, it further includes the following steps:
[0039] S4. Generate a License report;
[0040] S41. Send a request to generate a License report to the control center through the platform, and select one or more middleware types, weekly report, monthly report;
[0041] S42. The control center issues an instruction to generate a License report to the License adapter, and the License adapter generates a License report according to the middleware type and time period;
[0042] S43. Establish a link for downloading the License report.
[0043] Preferably, the License report in S42 includes: total number of Licenses, License type distribution, License status, organizational attribution information, unused Licenses, compliance check, Licenses expiring soon, abnormal Licenses, and parsing problem reports.
[0044] In a first aspect, an operation and maintenance device for maintaining middleware License provided by the present invention adopts the following technical solution:
[0045] An operation and maintenance device for maintaining middleware License includes the following modules:
[0046] The middleware License collection and storage module includes the following units:
[0047] The middleware License collection program distribution unit is used to maintain a timing task according to the License adapter, so that the control center regularly obtains the types of middleware managed in the platform, and distributes the License collection program corresponding to the middleware type to the middleware Agent in each Kubernetes cluster;
[0048] The middleware License collection unit is used to execute the License collection program through the middleware Agent to collect the License information of the middleware instance, and the License information includes commercial License and open source License;
[0049] The middleware License storage unit is used to report the collected License information of the middleware instance to the control center through the middleware Agent, and the control center stores the License information in the database;
[0050] The License information analysis module includes the following units:
[0051] The batch acquisition unit is used to enable the License adapter to batch acquire the middleware instance and the corresponding License information from the database according to the middleware type through the control center;
[0052] The License information identification and extraction unit is used to enable the License adapter to execute the corresponding License parsing program according to the middleware instance type, identify that the License information is a commercial License or an open source License, and extract the authorization code, time validity period, function authorization, quantity authorization, hardware compatibility information, software compatibility information, dynamic update characteristics, technical support and services from the License information;
[0053] License Information Analysis Unit, which is used to enable the License Adapter to identify the entries that have affected or will affect the operation of the middleware instance by analyzing the License information, generate warning messages and send them to the middleware maintenance personnel;
[0054] Result Update and Error Information Recording Unit, which is used to enable the License Adapter to update the analysis result of the License information to the database through the control center, record the error information that appears during the process of analyzing the License information, and generate an error report.
[0055] Preferably, it further includes the following modules:
[0056] Batch Update Module, including the following units:
[0057] Basic Parameter Acquisition Unit, which is used to acquire the basic parameters required for the middleware to apply for a License in the License Adapter;
[0058] Basic Information Collection Unit, which is used to enable the License Adapter to send the corresponding information collection program to the Agent of the corresponding Kubernetes cluster according to the type of middleware instance to be updated, and collect the basic information of the middleware instance;
[0059] Application or Purchase Unit, which is used to batch download the basic information collected in S32 through the platform, apply for or purchase the middleware License according to the requirements of the License, and batch upload the License to the control center through the middleware management platform;
[0060] License and Middleware Instance Mapping Relationship Identification Unit, which is used to enable the control center to send the License to the License Adapter, the License Adapter parses the License, obtains the device serial number and MAC from the License, and identifies the mapping relationship between the License and the middleware instance;
[0061] Update Unit, which is used to enable the License Adapter to send the License, the middleware instance and the License update program to the corresponding middleware Agent through the control center, and the middleware Agent executes the License update program to complete the License update according to the License update program;
[0062] Middleware Instance Reboot Judgment Unit, which is used to judge whether to reboot the middleware instance according to the License update program.
[0063] Preferably, it further includes the following modules:
[0064] License report generation module, including the following units:
[0065] License report request unit, used to send a license report generation request to the control center through the platform, and select one or more middleware types, weekly reports, and monthly reports;
[0066] License report generation unit, used to enable the control center to send an instruction to generate a license report to the license adapter, and the license adapter generates a license report according to the middleware type and time period;
[0067] License report link unit, used to establish a link for downloading the license report.
[0068] Thirdly, the present application provides an electronic device, adopting the following technical solution:
[0069] An electronic device, which includes:
[0070] One or more processors;
[0071] A memory;
[0072] One or more applications, where one or more applications are stored in the memory and configured to be executed by one or more processors, and one or more programs are configured to: execute an operation and maintenance method for maintaining middleware license shown in any possible implementation manner of the first aspect.
[0073] Fourthly, the present application provides a computer-readable storage medium, adopting the following technical solution:
[0074] A computer-readable storage medium, including: storing an operation and maintenance method for maintaining middleware license shown in any possible implementation manner of the first aspect that can be loaded and executed by a processor.
[0075] In summary, the present invention includes the following beneficial technical effects:
[0076] 1. The present invention can automatically complete tasks such as middleware license collection, detection, warning, and update, can efficiently and accurately complete license management work, reduces the need for manual intervention, thereby accelerating the operation and maintenance speed and improving work efficiency.
[0077] 2. The present invention provides rich interfaces, which can be easily integrated with continuous integration / continuous deployment (CI / CD) processes, project management tools, or code repositories, etc., to realize the automation and real-time nature of license detection, improve the overall performance and stability of the system, and further reduce the operation and maintenance costs.
[0078] 3. The middleware License adapter in the present invention can help users check whether the open-source components used in the project comply with the corresponding license requirements, ensuring the compliance of the project; for license types with potential legal risks or compliance issues, the tool can give early warnings and suggestions to help users take timely measures to avoid risks.
[0079] 4. The present invention can generate a detailed license detection report, including all license types, license texts, copyright information, etc. used in the project, helping users comprehensively understand the license status of the project.
[0080] 5. Through the unified management platform of the present application, the License management tasks of middleware can be automated, such as automatic renewal, automatic update, etc., reducing manual intervention and improving operation and maintenance efficiency.
[0081] 6. The present invention can centrally monitor the usage of middleware License through the unified management platform, including information such as remaining term, usage volume, etc., helping operation and maintenance personnel timely understand the License status and avoiding affecting business operation due to License expiration or insufficiency.
[0082] 7. The present invention can avoid duplicate management and maintenance of middleware License between different departments or teams, reducing unnecessary resource waste.
[0083] 8. The present invention helps to ensure that the enterprise's behavior of using middleware complies with the terms and conditions of its license agreement by uniformly managing middleware License, avoiding legal disputes and fines caused by violating the license agreement. And the unified management platform can provide detailed License usage reports and audit logs to support internal or external audits of the enterprise to ensure compliance. At the same time, the unified management platform can support the disaster recovery backup and recovery strategy of middleware License to ensure that middleware services can be quickly restored in case of disasters and guarantee business continuity.
[0084] 9. When there are problems or faults with middleware License, the unified management platform can quickly locate the cause of the problem and take corresponding solutions to reduce the business interruption time. BRIEF DESCRIPTION OF THE DRAWINGS
[0085] Figure 1 is the architecture diagram of the management platform in the embodiment of the present invention.
[0086] Figure 2 is the flowchart of the operation and maintenance method for maintaining middleware License in the embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0087] The present invention will be further described in detail below with reference to the accompanying drawings.
[0088] An embodiment of the present invention discloses an operation and maintenance method for maintaining middleware License.
[0089] The operation and maintenance method for maintaining middleware License in this embodiment realizes the automated operation and maintenance of middleware based on the middleware management platform. Referring to Figure 1 , the core parts involved include a control center, a storage module, one or more Kubernetes clusters, a License adapter, a License report generation service, etc., such as external services or middleware manufacturers.
[0090] Specifically, referring to Figure 2 , the operation and maintenance method for maintaining middleware License includes the following steps:
[0091] S1. Collect middleware License and store it.
[0092] S11. The License adapter maintains a timing task to enable the control center to regularly obtain the middleware types managed in the platform and send the License collection program corresponding to the middleware types to the middleware Agent in each Kubernetes cluster.
[0093] S12. The middleware Agent executes the License collection program to collect the License information of the middleware instance. The License information includes commercial License and open source License.
[0094] S13. The middleware Agent reports the collected License information of the middleware instance to the control center, and the control center stores the License information in the database.
[0095] S2. The License adapter analyzes the collected License information of the middleware instance.
[0096] S21. The License adapter obtains the middleware instances and the corresponding License information in batches from the database according to the middleware types through the control center.
[0097] S22. The License adapter executes the corresponding License parsing program according to the middleware instance type, identifies that the License information is a commercial License or an open source License, and extracts information such as authorization code, time validity period, function authorization, quantity authorization, hardware compatibility information, software compatibility information, dynamic update characteristics, technical support and services, etc. from the License information.
[0098] S23. The License adapter analyzes the License information, identifies the entries that have affected or will affect the operation of the middleware instance, generates warning messages and sends them to the middleware maintenance personnel;
[0099] If some middleware instances update the License, the previously generated warning messages may be eliminated;
[0100] S24. The License adapter updates the analysis results of the License information to the database through the control center, records the error messages that occur during the process of analyzing the License information, and generates an error report.
[0101] And some key information in the analysis results of the License information also needs to be recorded for subsequent auditing and troubleshooting.
[0102] S3. Batch update the middleware License;
[0103] S31. Obtain the basic parameters required for the middleware to apply for a License in the License adapter, and this request is transmitted to the License adapter through the control center.
[0104] S32. The License adapter distributes the corresponding information collection program to the Agent of the corresponding Kubernetes cluster according to the type of middleware instance to be updated, and collects the basic information of the middleware instance;
[0105] The basic information includes the hardware serial number, MAC address, middleware instance version number, operating system information, authorized quantity, authorized period and other information.
[0106] S33. Batch download the basic information collected in S32 through the platform, apply for or purchase the middleware License according to the requirements of the License, and batch upload the License to the control center through the middleware management platform;
[0107] S34. The control center distributes the License to the License adapter, and the License adapter parses the License, obtains the device serial number and MAC from the License, and identifies the mapping relationship between the License and the middleware instance;
[0108] S35. The License adapter distributes the License, the middleware instance and the License update program to the corresponding middleware Agent through the control center, and the middleware Agent executes the License update program, completes the License update according to the License update program, and determines whether to restart the middleware instance according to the License update program.
[0109] S4. Generate a License report;
[0110] S41. The user sends a request to generate a License report to the control center through the platform page, and selects one or more middleware types, weekly reports, and monthly reports;
[0111] S42. The control center sends an instruction to generate a License report to the License adapter. The License adapter generates a License report according to the middleware type and time period. The License report is mainly output based on the License collection, detection, and update records;
[0112] The License report includes: total number of Licenses, License type distribution, License status, organizational affiliation information, unused Licenses, compliance check, Licenses expiring soon, abnormal Licenses, and parsing problem reports.
[0113] S43. Establish a link for downloading the License report to facilitate user access and review.
[0114] The embodiment of the present application also discloses an operation and maintenance device for maintaining middleware Licenses, which includes the following modules:
[0115] Middleware License collection and storage module, including the following units:
[0116] Middleware License collection program distribution unit, used to maintain a timing task according to the License adapter, so that the control center regularly obtains the middleware types managed in the platform, and distributes the License collection program corresponding to the middleware type to the middleware Agent in each Kubernetes cluster;
[0117] Middleware License collection unit, used to execute the License collection program through the middleware Agent to collect the License information of middleware instances. The License information includes commercial Licenses and open source Licenses;
[0118] Middleware License storage unit, used to report the collected License information of middleware instances to the control center through the middleware Agent, and the control center stores the License information in the database;
[0119] License information analysis module, including the following units:
[0120] Batch acquisition unit, used to enable the License adapter to batch acquire middleware instances and corresponding License information from the database according to middleware types through the control center;
[0121] License information identification and extraction unit, used to enable the License adapter to execute corresponding License parsing programs according to middleware instance types, identify whether the License information is a commercial License or an open-source License, and extract authorization codes, time validity periods, function authorizations, quantity authorizations, hardware compatibility information, software compatibility information, dynamic update features, technical support and services from the License information;
[0122] License information analysis unit, used to enable the License adapter to identify items that have affected or will affect the operation of middleware instances by analyzing License information, generate warning messages and send them to middleware maintenance personnel;
[0123] Result update and error information recording unit, used to enable the License adapter to update the analysis results of License information to the database through the control center, record error information that occurs during the process of analyzing License information, and generate error reports.
[0124] Batch update module, including the following units:
[0125] Basic parameter acquisition unit, used to acquire basic parameters required for the middleware to apply for a License within the License adapter;
[0126] Basic information collection unit, used to enable the License adapter to send corresponding information collection programs to the Agents of the corresponding Kubernetes clusters according to the middleware instance types to be updated, and collect basic information of middleware instances;
[0127] The basic information includes hardware serial numbers, MAC addresses, middleware instance version numbers, operating system information, authorized quantities, and authorized periods.
[0128] Application or purchase unit, used to batch download the basic information collected in S32 through the platform, apply for or purchase middleware Licenses according to the requirements of the License, and batch upload the Licenses to the control center through the middleware management platform;
[0129] The License and middleware instance mapping relationship recognition unit is used to enable the control center to issue the License to the License adapter. The License adapter parses the License, obtains the device serial number and MAC from the License, and recognizes the mapping relationship between the License and the middleware instance;
[0130] The update unit is used to enable the License adapter to issue the License, middleware instance, and License update program to the corresponding middleware Agent through the control center. The middleware Agent executes the License update program and completes the License update according to the License update program;
[0131] The middleware instance restart judgment unit is used to judge whether to restart the middleware instance according to the License update program.
[0132] The License report generation module includes the following units:
[0133] The License report request unit is used to send a License report generation request to the control center through the platform and select one or more middleware types, weekly reports, and monthly reports;
[0134] The License report generation unit is used to enable the control center to issue an instruction to generate a License report to the License adapter. The License adapter generates a License report according to the middleware type and time period;
[0135] The License report includes: total number of Licenses, License type distribution, License status, organizational attribution information, unused Licenses, compliance check, Licenses about to expire, abnormal Licenses, parsing problem reports, etc.
[0136] The License report link unit is used to establish a link for downloading the License report to facilitate user access and viewing.
[0137] In the embodiments of the present application, an electronic device is provided. The electronic device includes: a processor and a memory. Among them, the processor and the memory are connected, such as through a bus. Optionally, the electronic device may further include a transceiver. It should be noted that in practical applications, the transceiver is not limited to one, and the structure of the electronic device does not constitute a limitation to the embodiments of the present application.
[0138] The processor can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0139] The bus can include a path for transmitting information between the above components. The bus can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc.
[0140] The memory can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or it can also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
[0141] The memory is used to store the application program code for executing the solution of this application and is controlled by the processor for execution. The processor is used to execute the application program code stored in the memory to implement the content shown in the foregoing embodiments of an operation and maintenance method for maintaining the middleware License.
[0142] Among them, the electronic devices include but are not limited to: mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. It can also be a server, etc.
[0143] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When it runs on a computer, it enables the computer to execute the corresponding content in the foregoing embodiment of the operation and maintenance method for maintaining the middleware License.
[0144] It should be understood that although each step in the flowchart of the accompanying drawings is shown sequentially according to the indication of the arrows, these steps are not necessarily executed sequentially according to the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limitation, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and their execution order is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.
[0145] The above are only some implementation manners of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.
Claims
1. A method for maintaining a middleware license, characterized in that: The following steps are involved: S1. Collect and store middleware licenses; S11. The License Adapter maintains a scheduled task, which enables the control center to regularly obtain the middleware types managed in the platform and send the license collection program corresponding to the middleware type to the middleware Agent in each Kubernetes cluster. S12, the middleware agent executes the license collection program to collect the license information of the middleware instance, the license information includes commercial license and open source license; S13, the middleware agent reports the collected license information of the middleware instance to the control center, and the control center stores the license information into the database; S2. Analyze the license information of the middleware instance; S21. The license adapter obtains the middleware instances and corresponding license information in batches from the database according to the middleware types through the control center; S22. The license adapter executes the corresponding license parsing program according to the middleware instance type, identifies whether the license information is a commercial license or an open source license, and extracts the authorization code, time validity period, function authorization, quantity authorization, hardware compatibility information, software compatibility information, dynamic update features, and technical support and services from the license information; S23, the license adapter identifies the items that have affected or will affect the operation of the middleware instance by analyzing the license information, generates an alarm message and sends it to the middleware maintenance personnel; S24. The license adapter updates the analysis result of the license information to the database through the control center, records the error information that occurs during the analysis of the license information, and generates an error report.
2. According to claim 1, a method for maintaining a middleware license is characterized in that: The following steps are also included: S3. Update middleware licenses in batches; S31. Obtain the basic parameters required by the middleware in the license adapter to apply for a license; S32. The license adapter sends the corresponding information collection program to the Agent of the corresponding Kubernetes cluster according to the middleware instance type that needs to be updated, and collects the basic information of the middleware instance; S33, batch download the basic information collected in S32 through the platform, apply for or purchase the middleware license according to the license requirements, and upload the license in batches to the control center through the middleware management platform; S34, the control center sends the license to the license adapter, the license adapter parses the license, obtains the device serial number and MAC from the license, and identifies the mapping relationship between the license and the middleware instance; S35. The license adapter sends the license, the middleware instance and the license update program to the corresponding middleware agent through the control center. The middleware agent executes the license update program, completes the license update according to the license update program, and determines whether to restart the middleware instance according to the license update program.
3. The method for maintaining a middleware license according to claim 2, characterized in that: The basic information in S32 includes hardware serial number, MAC address, middleware instance version number, operating system information, authorized quantity, and authorized period.
4. The method for maintaining a middleware license according to claim 1, characterized in that: The following steps are also included: S4. Generate a license report; S41. Send a request to generate a license report to the control center through the platform, and select one or more middleware types, weekly reports, and monthly reports; S42, the control center issues an instruction to the license adapter to generate a license report. The license adapter generates license reports based on the middleware type and time period; S43. Create a link for downloading the license report.
5. The method for maintaining a middleware license according to claim 4, characterized in that: The license report in S42 includes: total number of licenses, license type distribution, license status, organization affiliation information, unused licenses, compliance checks, licenses that are about to expire, abnormal licenses, and analysis problem reports.
6. An operation and maintenance device for maintaining a middleware license, characterized in that: Includes the following modules: The middleware license collection and storage module includes the following units: The middleware license collection program delivery unit is used to maintain the scheduled tasks according to the license adapter, so that the control center can regularly obtain the middleware types managed in the platform, and deliver the license collection program corresponding to the middleware type to the middleware agent in each Kubernetes cluster; The middleware license collection unit is used to execute the license collection program through the middleware agent to collect the license information of the middleware instance, and the license information includes commercial license and open source license; The middleware license storage unit is used to report the collected license information of the middleware instance to the control center through the middleware agent, and the control center stores the license information into the database; The license information analysis module includes the following units: The batch acquisition unit is used to enable the license adapter to obtain the middleware instances and corresponding license information in batches according to the middleware types from the database through the control center; The license information identification and extraction unit is used to enable the license adapter to execute the corresponding license parsing program according to the middleware instance type, identify whether the license information is a commercial license or an open source license, and extract the authorization code, time validity period, function authorization, quantity authorization, hardware compatibility information, software compatibility information, dynamic update characteristics, technical support and services from the license information; The license information analysis unit is used to enable the license adapter to identify the items that have affected or will affect the operation of the middleware instance by analyzing the license information, generate alarm information and send it to the middleware maintenance personnel; The result updating and error information recording unit is used to enable the License adapter to update the analysis results of the License information to the database through the control center, record the error information that occurs during the analysis of the License information, and generate an error report.
7. The operation and maintenance device for maintaining middleware license according to claim 6, characterized in that: Also includes the following modules: Batch update module, including the following units: The basic parameter acquisition unit is used to obtain the basic parameters required by the middleware in the license adapter when applying for a license; The basic information collection unit is used to enable the License adapter to send the corresponding information collection program to the Agent of the corresponding Kubernetes cluster according to the middleware instance type that needs to be updated, and collect the basic information of the middleware instance; The application or purchase unit is used to batch download the basic information collected in S32 through the platform, apply for or purchase the middleware license according to the license requirements, and upload the license in batches to the control center through the middleware management platform; The license and middleware instance mapping relationship identification unit is used to enable the control center to send the license to the license adapter, and the license adapter parses the license, obtains the device serial number and MAC from the license, and identifies the mapping relationship between the license and the middleware instance; The update unit is used to enable the license adapter to send the license, the middleware instance and the license update program to the corresponding middleware agent through the control center, and the middleware agent executes the license update program to complete the license update according to the license update program; The middleware instance restart determination unit is used to determine whether to restart the middleware instance according to the license update program.
8. The operation and maintenance device for maintaining middleware license according to claim 6, characterized in that: Also includes the following modules: The license report generation module includes the following units: The license report request unit is used to send a license report generation request to the control center through the platform, and select one or more middleware types, weekly reports, and monthly reports; A license report generating unit, used to enable the control center to issue a license report generating instruction to the license adapter, and the license adapter generates the license report according to the middleware type and time period; The license report link unit is used to establish a link for downloading the license report.
9. An electronic device, characterized in that: It includes: One or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to: execute an operation and maintenance method for maintaining a middleware license according to any one of claims 1 to 5.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, an operation and maintenance method for maintaining a middleware license as described in any one of claims 1 to 5 is implemented.