Middleware deployment method and device, computer equipment and storage medium

Abstract

The invention relates to a middleware deployment method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a self-defined configuration parameter, and analyzing the configuration parameter to obtain an analyzed configuration parameter; dynamically generating an installation script according to the analyzed configuration parameters; generating a configuration file according to the self-defined configuration parameters; performing first verification on the configuration file to obtain a verified configuration file; performing second verification on the configuration parameters to correct the installation script to obtain a corrected installation script; and deploying the middleware to the target deployment node according to the verified configuration file and the corrected installation script. By adopting the method, the middleware can be automatically deployed, and the installation script and the configuration file in the middleware deployment process are verified, so that the middleware deployment efficiency is enhanced, and the operation and maintenance cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of operation and maintenance technology, and in particular to a middleware deployment method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] In the early days of software development, many companies adopted the traditional monolithic application architecture, packaging all functional modules into a separate application service for deployment. However, with the continuous development and expansion of the enterprise business system, the disadvantages of this architecture gradually emerged. In order to overcome the defects of the monolithic application architecture, the microservice architecture came into being. The microservice architecture splits a single application into multiple independent and autonomous small services, each of which is responsible for a specific business function and communicates through network protocols. In the widespread application of microservice architecture and cloud-native applications, service registration, configuration management, and service discovery become particularly important, that is, microservices and applications need a powerful tool to manage and maintain service registration, configuration, and service discovery. To solve this problem, middleware such as the Naming and Configuration Orchestration Service (Nacos) came into being. As a feature-rich dynamic service discovery, configuration management, and service management platform, Nacos middleware provides a convenient management and configuration method for service registration, configuration, and service discovery. Therefore, the deployment of middleware such as Nacos on deployment nodes is particularly important.

[0003] In traditional technologies, the deployment of middleware relies on manual configuration and manual operation. Administrators need to prepare the operating system environment of the target server, download and decompress the middleware installation package, and then manually edit multiple configuration files to set service parameters such as ports and network settings to complete the deployment of the middleware on the deployment node.

[0004] However, as the deployment environment of Nacos becomes more and more complex, the configuration requirements gradually increase, and the traditional manual configuration and deployment methods can no longer meet the needs of modern applications. The traditional middleware deployment method mainly relies on command lines and scripts to perform a large number of configuration modifications and deployments. The entire installation and deployment process is completed manually, the steps are cumbersome and repetitive, the middleware deployment workload is huge, and configuration errors are prone to occur, which not only reduces the efficiency of middleware deployment, but also increases operation and maintenance costs. Summary of the invention

[0005] Based on this, it is necessary to provide a middleware deployment method, device, computer equipment, computer-readable storage medium and computer program product that can automatically deploy middleware and verify the installation scripts and configuration files of the middleware deployment process, thereby enhancing the efficiency of middleware deployment and reducing operation and maintenance costs.

[0006] In a first aspect, the present application provides a middleware deployment method, comprising:

[0007] Get the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters;

[0008] Dynamically generate installation scripts based on parsed configuration parameters; and generate configuration files based on custom configuration parameters;

[0009] Performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0010] Deploy the middleware to the target deployment node based on the verified configuration files and the corrected installation scripts.

[0011] In one embodiment, performing a second verification on the configuration parameters includes:

[0012] When it is determined that the installation directory of the target deployment node exists, determine whether the environment version meets the middleware operation requirements;

[0013] When it is determined that the environment version meets the middleware operation requirements, the database of the target deployment node is traversed to determine whether the configuration parameters exist in the database of the target deployment node;

[0014] When the configuration parameters exist in the database of the target deployment node, the second verification of the configuration parameters is completed.

[0015] In one embodiment, deploying the middleware according to the verified configuration file and the corrected installation script includes:

[0016] Transfer the verified configuration files and the corrected installation scripts to the target deployment node;

[0017] Run the corrected installation script through the preset task execution interface;

[0018] During the process of running the corrected installation script, the environment settings and parameter adjustments of the middleware are performed according to the verified configuration files to complete the deployment of the middleware on the target deployment node.

[0019] In one embodiment, performing a first verification on the configuration file to obtain a verified configuration file includes:

[0020] Verify whether there are conflicts between configuration parameters in the configuration file through the preset deployment logic mechanism;

[0021] When it is determined that there is no conflict between the configuration parameters of the configuration file, whether the configuration file complies with the standard specification is determined through the preset configuration syntax and structure verification mechanism;

[0022] When it is determined that the configuration file complies with the standard specification, a verified configuration file is obtained.

[0023] In one embodiment, after deploying the middleware to the target deployment node, the method further includes:

[0024] The middleware is cluster-deployed on the cluster nodes, and the running status of the cluster nodes is monitored for abnormalities according to the preset time period to obtain abnormal information;

[0025] When it is determined that there is an abnormality in the cluster node, locate the faulty node based on the abnormal information;

[0026] Automatically restart the failed node or redeploy the middleware on the failed node.

[0027] In one embodiment, an installation script is dynamically generated according to the parsed configuration parameters; and a configuration file is generated according to the customized configuration parameters, including:

[0028] Dynamically generate installation scripts based on parsed configuration parameters and pre-set script templates;

[0029] A predefined configuration file template is used to generate an initial configuration file adapted to the environment, and the customized configuration parameters are used to replace the default values ​​in the initial configuration file to generate a configuration file.

[0030] In a second aspect, the present application also provides a middleware deployment device, including:

[0031] The acquisition module is used to obtain the custom configuration parameters and parse the configuration parameters to obtain the parsed configuration parameters;

[0032] The generation module is used to dynamically generate the installation script according to the parsed configuration parameters; and generate the configuration file according to the customized configuration parameters;

[0033] The verification module is used to perform a first verification on the configuration file to obtain a verified configuration file; and to perform a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0034] The deployment module is used to deploy the middleware to the target deployment node according to the verified configuration file and the corrected installation script.

[0035] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0036] Get the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters;

[0037] Dynamically generate installation scripts based on parsed configuration parameters; and generate configuration files based on custom configuration parameters;

[0038] Performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0039] Deploy the middleware to the target deployment node based on the verified configuration files and the corrected installation scripts.

[0040] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0041] Get the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters;

[0042] Dynamically generate installation scripts based on parsed configuration parameters; and generate configuration files based on custom configuration parameters;

[0043] Performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0044] Deploy the middleware to the target deployment node based on the verified configuration files and the corrected installation scripts.

[0045] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0046] Get the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters;

[0047] Dynamically generate installation scripts based on parsed configuration parameters; and generate configuration files based on custom configuration parameters;

[0048] Performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0049] Deploy the middleware to the target deployment node based on the verified configuration files and the corrected installation scripts.

[0050] The above-mentioned middleware deployment method, device, computer equipment, storage medium and computer program product obtain custom configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters; dynamically generate an installation script according to the parsed configuration parameters; and generate a configuration file according to the custom configuration parameters; perform a first verification on the configuration file to obtain a verified configuration file; and perform a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script; and deploy the middleware to the target deployment node according to the verified configuration file and the corrected installation script. The method can be used to automatically deploy the middleware, and verify the installation script and configuration file of the middleware deployment process, thereby enhancing the middleware deployment efficiency and reducing the operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0052] Figure 1 An application environment diagram of a middleware deployment method in an embodiment;

[0053] Figure 2 A schematic diagram of a flow chart of a middleware deployment method in an embodiment;

[0054] Figure 3 A schematic diagram of a process for deploying middleware in an embodiment;

[0055] Figure 4 It is a structural block diagram of a middleware deployment device in one embodiment;

[0056] Figure 5 A schematic diagram of the working process of an error detection module in one embodiment;

[0057] Figure 6 A schematic diagram of the working process of a self-healing module in one embodiment;

[0058] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0060] The middleware deployment method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The terminal 102 sends a middleware deployment request to the server 104, and the server 104 receives the middleware deployment request, obtains the custom configuration parameters, and parses the configuration parameters to obtain the parsed configuration parameters; according to the parsed configuration parameters, dynamically generates an installation script; and generates a configuration file according to the custom configuration parameters; performs a first verification on the configuration file to obtain a verified configuration file; and performs a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script; according to the verified configuration file and the corrected installation script, the middleware is deployed to the target deployment node. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0061] As the deployment environment of Nacos middleware becomes more and more complex, the configuration requirements become more and more cumbersome, and frequent manual resource configuration has become a time-consuming and error-prone daily operation and maintenance change method. When clustering middleware, that is, deploying middleware on multiple deployment nodes, the traditional middleware deployment method is to perform a large number of configuration modifications and deployments through commands and scripts, and the installation and deployment process needs to be implemented manually, the steps are cumbersome, and multiple servers need to be deployed into a cluster. Each deployment requires repeated manual work, which consumes working time and easily leads to the problem of normalization errors in the configuration information of the middleware deployment, which in turn leads to poor performance of the deployed middleware and difficulty in maintenance. In addition, the traditional middleware deployment method does not have a unified management interface to uniformly manage the cluster nodes of the deployed middleware and change and adjust the configuration information, and its transparency and maintainability are limited. At the same time, the traditional middleware deployment method requires users to manually edit a large number of configuration files. When there are many cluster nodes in the cluster deployment, it is inconvenient to view and modify the configuration. This application proposes a middleware deployment method that can automatically deploy middleware, avoiding tedious manual operations; it can automatically generate installation scripts and configuration files, and verify and correct the installation scripts and configuration files, which can ensure the standardization and accuracy of the middleware deployment process, thereby reducing maintenance costs, while improving management efficiency and user experience. In addition, the middleware deployment method of this application supports multi-environment deployment and dynamic adjustment, and can flexibly adapt according to different deployment requirements, enhancing the consistency and reliability of the middleware in different environments.

[0062] In an exemplary embodiment, Figure 2 As shown, a middleware deployment method is provided, which is applied to Figure 1 The server in the example is used to illustrate, including the following steps 202 to 208. Among them:

[0063] Step 202: Obtain the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters.

[0064] Customized configuration parameters refer to the customized configuration parameters manually input by users according to business requirements in middleware deployment. Configuration parameters may include middleware deployment version information, target deployment environment identifier, deployment node identifier, connection configuration information of related databases, middleware performance tuning parameters, etc. Parsing configuration parameters means deeply analyzing configuration parameters, extracting relevant information, and performing syntax and logic verification to obtain parsed configuration parameters.

[0065] Optionally, the server initializes the configuration parameter input unit through a preset graphical user interface, and at the same time receives a series of key configuration parameters that are customized and input by the user according to the current business needs through the preset graphical user interface. These configuration parameters include, but are not limited to, middleware deployment version information, target deployment environment identifier, deployment node identifier, connection configuration information of related databases, middleware performance tuning parameters, etc. At the same time, the server can verify the validity of the configuration parameters customized by the user in real time to ensure the integrity and compliance of the configuration parameters. Among them, the middleware deployment version information determines the middleware version that needs to be deployed, the target deployment environment identifier refers to the identifier of the environment (such as development environment, test environment, production environment) in which the middleware is deployed, the deployment node identifier refers to the identifier of the node in which the middleware is deployed, and the connection configuration information of the related database includes the database address, port, user name, password, etc., which is used to ensure that the middleware can connect to and operate the required database, and the middleware performance tuning parameters are used to adjust the performance of the middleware, such as memory size, number of threads, etc.

[0066] Step 204, dynamically generate an installation script according to the parsed configuration parameters; and generate a configuration file according to the customized configuration parameters.

[0067] The installation script refers to the script used to perform operations such as middleware installation, configuration, and dependency installation in automated deployment. The installation script can include middleware installation commands, dependency libraries and environment configuration, directory structure and file settings, system environment configuration, etc. The configuration file is a file that stores the parameters and configuration information required for the middleware to run, usually in plain text format (such as .properties, .yaml, .json). The middleware can determine how to connect to other services, how to configure the network, how to optimize performance, etc. by reading the configuration file.

[0068] Exemplarily, the user provides a series of customized configuration parameters through a graphical user interface according to business needs and deployment environment. For example, the user may specify the target environment (such as development environment, production environment), the middleware version to be deployed, database connection information, etc. These configuration parameters will be collected by the server and verified and standardized through the parsing process to ensure that all input parameters are correct and consistent. Based on the parsed configuration parameters, the server dynamically generates an installation script adapted to the target environment. The installation script automatically performs tasks such as installation, configuration, and dependency processing according to different operating systems and middleware versions. At the same time, the server also generates a configuration file based on the customized configuration parameters. The configuration file may include database connection, performance tuning, environment-specific parameters, etc. The configuration file will be read and applied when the middleware is started to ensure that the middleware runs correctly on each deployment node.

[0069] Step 206, performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script.

[0070] Among them, the first verification of the configuration file is used to verify the correctness and consistency of the configuration file and ensure that there is no conflict between the configuration parameters of the configuration file. The second verification of the configuration parameters refers to judging the correctness of the middleware deployment and making necessary adjustments based on the input configuration parameters. During the second verification of the configuration parameters, the validity of the configuration parameters will be checked, such as confirming whether the selected installation path, Java Development Kit (Java DevelopmentKit, JDK) version, and database connection information are correct. If a configuration error or missing is found during the second verification of the configuration parameters, the server will automatically adjust or correct it, such as creating a missing installation directory, downloading the JDK version required for installation, or creating a database table. These adjustment or correction operations will directly affect the installation script, which can ensure that the installation script is executed as expected, thereby avoiding deployment failures or redundant operations caused by incorrect parameter configuration.

[0071] Step 208: deploy the middleware to the target deployment node according to the verified configuration file and the corrected installation script.

[0072] Optionally, the verified configuration file may include the middleware's operating parameters, deployment environment information, database connection configuration and other information, and the corrected installation script ensures that the middleware can be correctly installed according to the current deployment environment and hardware configuration. The server uses a secure transmission interface to transmit the verified configuration file and the corrected installation script to the target deployment node, and uses a preset task execution interface to gradually implement the middleware deployment task. The middleware deployment task may include the installation, configuration and necessary environment adjustments of the middleware, thereby ensuring that the middleware can run smoothly on the target deployment node and meet the predetermined performance standards. Through this automated process, the middleware deployment process can be completed quickly and accurately, reducing manual intervention and improving the consistency and efficiency of middleware deployment.

[0073] In the above middleware deployment method, custom configuration parameters are obtained so that the deployment process can be flexibly adjusted according to user needs; and the configuration parameters are parsed to obtain the parsed configuration parameters, which can ensure that the custom configuration parameters meet the expected format and standards, thereby avoiding middleware operation problems caused by configuration parameter errors. According to the parsed configuration parameters, the installation script is dynamically generated; and the configuration file is generated according to the custom configuration parameters, which can reduce the complexity of manual configuration and script writing, thereby improving the consistency and maintainability of middleware deployment. The configuration file is first verified to obtain the verified configuration file, which can ensure that the various configuration parameters in the configuration file meet the predetermined rules; and the configuration parameters are secondly verified to correct the installation script to obtain the corrected installation script, ensuring that all parameters used in the installation script are valid and consistent, thereby ensuring that the middleware is correctly configured and efficiently operated on the target deployment node, reducing maintenance costs, while improving management efficiency and user experience. The middleware is deployed to the target deployment node according to the verified configuration file and the corrected installation script, which can automatically deploy the middleware, avoid tedious manual operations, and reduce configuration errors or inconsistencies introduced by manual operations. At the same time, through the middleware deployment process of this embodiment, the administrator can uniformly deploy the middleware on multiple deployment nodes (cluster nodes) without having to manually configure each deployment node one by one, thereby simplifying the operation and maintenance work.

[0074] In an exemplary embodiment, an installation script is dynamically generated based on the parsed configuration parameters; and a configuration file is generated based on the customized configuration parameters, including: dynamically generating an installation script based on the parsed configuration parameters and a pre-set script template; using a predefined configuration file template to generate an initial configuration file adapted to the environment, and replacing the default values ​​in the initial configuration file with the customized configuration parameters to generate a configuration file.

[0075] The environment refers to the deployment environment of the middleware.

[0076] After deeply analyzing the configuration parameters, extracting relevant information, and performing syntax and logic verification, the parsed configuration parameters are obtained, which can ensure that there are no syntax errors in the configuration parameters and no conflicts or inconsistencies in logic. After obtaining the parsed configuration parameters, the appropriate script template is determined according to the characteristics of different deployment environments, middleware version iterations, and target devices (devices for which the target deployment node corresponds). Then, based on the script template, an installation script that meets specific requirements is dynamically generated to achieve adaptation for specific environments. For example, for devices with different operating systems, the generated installation script will automatically adapt to the corresponding commands and configuration methods to ensure the correct execution of the middleware deployment process.

[0077] Generate an initial configuration file that is adapted to the current deployment environment based on the predefined configuration file template. This initial configuration file will automatically load appropriate default values ​​in the predefined configuration file template based on the current deployment environment. Automatically replace the default values ​​in the initial configuration file with the customized configuration parameters. For example, if the user specifies the database connection address, port or other configuration items in the customized configuration parameters, these information will replace the corresponding placeholders in the initial configuration file, thereby generating a configuration file that meets the user's needs.

[0078] In this implementation, the installation script is dynamically generated based on the parsed configuration parameters and the pre-set script template. It can be flexibly adapted according to different deployment environments, version requirements and target device (device for the target deployment node) characteristics, and automatically generate installation scripts that adapt to specific environments, which enhances the flexibility and adaptability of middleware deployment. At the same time, it can avoid the tedious steps of manual script writing, greatly reduce human errors, and thus accelerate the deployment process of middleware. Automatically replacing the default values ​​in the initial configuration file with user-defined configuration parameters can improve the efficiency and accuracy of configuration file generation, avoid the tedious and error-prone problems of manual editing of configuration files, and facilitate large-scale deployment and management of middleware.

[0079] In an exemplary embodiment, a first verification is performed on the configuration file to obtain a verified configuration file, including: verifying whether there is a conflict between configuration parameters of the configuration file through a preset deployment logic mechanism; when it is determined that there is no conflict between the configuration parameters of the configuration file, judging whether the configuration file complies with standard specifications through a preset configuration syntax and structure verification mechanism; when it is determined that the configuration file complies with the standard specifications, obtaining the verified configuration file.

[0080] Among them, the preset deployment logic mechanism refers to the middleware deployment logic reasoning mechanism, which refers to the process of reasoning, judging and verifying configuration parameters according to predefined logic rules and algorithms during the middleware deployment process. These rules and algorithms analyze the parameters in the configuration file to ensure that there will be no conflicts, duplications or inconsistencies during the deployment process. For example, if a configuration parameter requires the specification of a database port number, the system will use the reasoning mechanism to determine whether the port is occupied and whether it conflicts with other configuration items. The preset syntax and structure verification mechanism refers to the syntax and structure checks of the generated configuration files through preset rules or standards to ensure that the configuration files comply with standard formats and conventions, and avoid the failure of middleware deployment due to file format errors or syntax errors.

[0081] Exemplarily, the configuration parameters of the configuration file are verified one by one through the middleware deployment logic reasoning mechanism to ensure that there is no conflict between the configuration parameters of the configuration file. For example, if two configuration parameters set the same port or resource, the system will prompt the conflict and require the user to adjust it. The configuration file is also verified for security standards to ensure that the configuration file complies with the security standards specified by the organization or industry to prevent security vulnerabilities in the middleware deployment. For example, some configuration parameters of the configuration file may require data encryption or access control to be enabled, and these security parameters are evaluated and verified to ensure that the configuration file meets the requirements. The configuration file is checked for compliance with the predetermined format and structure standards through the syntax and structure verification mechanism. The syntax and structure verification mechanism is used to verify whether the syntax of the configuration file is correct, such as whether there are any missing required items or illegal characters, to ensure that the configuration file can be read successfully.

[0082] In this embodiment, through the preset deployment logic mechanism and the preset configuration syntax and structure verification mechanism, it is ensured that the configuration files in the deployment process comply with standard specifications, reducing potential configuration errors, conflicts and security vulnerabilities, and can effectively improve the success rate, stability and security of middleware deployment.

[0083] In an exemplary embodiment, a second verification is performed on the configuration parameters, including: when it is determined that the installation directory of the target deployment node exists, determining whether the environment version meets the middleware operation requirements; when it is determined that the environment version meets the middleware operation requirements, traversing the database of the target deployment node to determine whether the configuration parameters exist in the database of the target deployment node; when the configuration parameters exist in the database of the target deployment node, the second verification of the configuration parameters is completed.

[0084] The installation directory refers to the folder on the target deployment node that stores middleware programs, configuration files, and other related resources. The environment version refers to the JDK version corresponding to the middleware.

[0085] Optionally, the target deployment node is automatically checked through a preset deployment node check interface, which detects whether the installation directory of the target deployment node exists. If the installation directory of the target deployment node does not exist, the installation directory of the target deployment node is created to ensure that the middleware can be successfully installed and run under the specified path.

[0086] If the installation directory of the target deployment node exists, determine whether the environment version (JDK version) meets the middleware running requirements, that is, determine whether the JDK version corresponding to the middleware is installed on the target deployment node. If the required JDK version is not installed on the target deployment node, automatically download and install the correct JDK version according to the middleware deployment version information to ensure that the middleware can run correctly. If the required JDK version has been installed on the target deployment node (that is, the environment version meets the middleware running requirements), it is prohibited to repeatedly install the corresponding JDK version to avoid redundant operations and save resources.

[0087] When the required JDK version has been installed on the target deployment node (that is, the environment version meets the middleware running requirements), the database of the target deployment node is traversed to determine whether the required database and table (configuration parameters) exist. For example, some middleware requires a database named "middleware_db" and multiple tables for storing configuration information. If the required database and table (configuration parameters) do not exist in the database of the target deployment node, the required database and table are automatically created to ensure that the middleware can access the required data resources. This ensures that all necessary resources are ready during the middleware deployment process, avoiding the failure of middleware deployment due to missing databases or tables. When the required database and table (configuration parameters) exist in the database of the target deployment node, the second verification of the configuration parameters is completed.

[0088] In this embodiment, the installation directory of the target deployment node is judged to ensure that the required installation directory always exists, thereby improving the efficiency and consistency of the middleware deployment process. By judging whether the environment version meets the middleware operation requirements, the problem of mismatch between the middleware deployment version information and the JDK version can be avoided, thereby ensuring that the middleware can run in the correct environment. By judging whether the configuration parameters exist in the database of the target deployment node, it can be ensured that the deployed middleware can smoothly connect to and operate the correct database and table, thereby ensuring the reliability and consistency of data storage. This embodiment can effectively avoid human errors, improve the efficiency of the deployment process, reduce redundant operations, and ensure the consistency and integrity of the middleware deployment environment.

[0089] In an exemplary embodiment, Figure 3 As shown, deploying the middleware according to the verified configuration file and the corrected installation script includes steps 302 to 306. Among them:

[0090] Step 302: Transmit the verified configuration file and the corrected installation script to the target deployment node.

[0091] Step 304: Run the corrected installation script through a preset task execution interface.

[0092] Step 306, during the execution of the corrected installation script, the environment settings and parameter adjustments are performed on the middleware according to the verified configuration file to complete the deployment of the middleware on the target deployment node.

[0093] Optionally, the verified configuration files and corrected installation scripts are transferred in batches to the target deployment node using a preset secure transmission interface. The secure transmission interface uses an encryption algorithm to encrypt data using the SSL / TLS protocol to ensure that the verified configuration files and corrected installation scripts maintain integrity and security during transmission, and prevent data from being stolen or tampered with on the network. The secure transmission interface is an encrypted data transmission mechanism that is used to ensure that sensitive information is not leaked during data transmission.

[0094] Based on the transmitted verified configuration files and the corrected installation scripts, according to factors such as diversified deployment environments, middleware version iterations, and identification information of target devices (devices corresponding to target deployment nodes), the preset task execution interface is used to gradually implement installation and configuration tasks on the target deployment nodes. That is, through the preset task execution interface, the corrected installation script is run to implement installation and configuration tasks on the target deployment nodes, which can ensure that each target deployment node can accurately and efficiently deploy middleware.

[0095] When running the corrected installation script through the preset task execution interface to implement the installation and configuration tasks on the target deployment node, the environment settings and parameter adjustments of the middleware are performed according to the verified configuration file. The verified configuration file contains customized settings for specific environments, such as database connection information, JDK version, memory limit and other parameters. These settings ensure that the middleware can run smoothly on the target deployment node and interact correctly with other services, thereby achieving an efficient and secure middleware deployment process.

[0096] In this embodiment, during the process of running the corrected installation script, the necessary environment settings and parameter adjustments can be made to the middleware according to the verified configuration file, so that the deployed middleware can be adaptively configured according to the environmental characteristics of the target deployment node to ensure the best performance. Through the automated deployment of the middleware, the interference of human factors is reduced, the deployment errors of the middleware are reduced, and the stability and maintainability of the middleware after deployment are improved.

[0097] In an exemplary embodiment, after the middleware is deployed to the target deployment node, it also includes: clustering the middleware on the cluster nodes, and performing abnormal monitoring on the operating status of the cluster nodes according to a preset time period to obtain abnormal information; when it is determined that there is an abnormality in the cluster node, locating the faulty node according to the abnormal information; performing an automatic restart operation on the faulty node, or redeploying the middleware on the faulty node.

[0098] When the middleware is deployed in a cluster, that is, when the middleware is deployed in multiple deployment nodes, the middleware deployment method of the present application is used to implement cluster deployment of the middleware in multiple deployment nodes (cluster nodes). After the middleware is clustered in the cluster nodes, the running status of the cluster nodes is continuously monitored according to a preset time period. The monitoring content includes the health status of the nodes, resource usage (such as memory, disk space, etc.), network connection status, and the running status of the application. If any operational abnormality of any deployment node is detected during the monitoring process (such as no response from the node, excessive load, or failure), the abnormal information is collected immediately, and the specific faulty node is determined by locating the abnormal problem.

[0099] When the faulty node is accurately located, appropriate repair measures are taken according to the abnormal information. First, the server will automatically try to restart the faulty node to restore the normal operation of the node. If the restart operation cannot solve the problem, the middleware on the faulty node will be redeployed. The redeployment of the middleware may include reinitializing the installation of the middleware, updating the configuration files, and necessary service recovery, so as to ensure that the middleware of the node can be restored to a normal operating state and be consistent with other nodes in the cluster.

[0100] In traditional middleware deployment, node failures often require manual intervention by operation and maintenance personnel to troubleshoot and recover, which is time-consuming and has a high error rate. In this embodiment, an automatic restart operation is performed on the faulty node, or the middleware is redeployed at the faulty node, so that the middleware deployment has an automated repair process, that is, the middleware deployment has self-healing capabilities, which can significantly improve the reliability of the middleware deployment. At the same time, through the automated repair process, many common faults can be automatically repaired without manual operation, greatly shortening the recovery time and improving service continuity.

[0101] In an exemplary embodiment, the deployment process of the middleware is monitored in real time to ensure that all tasks are executed correctly and to record the deployment log; if the execution process of the middleware during deployment deviates from the expected behavior, the server obtains error detection information and corrects the deviated execution process based on the error detection information.

[0102] For example, when an exception occurs during the deployment of the middleware, the server can quickly identify deviations from expected behavior, whether it is an error in the configuration file, an issue with the execution of the installation script, or incompatibility with the target deployment node environment, and can promptly trigger the preset error handling process to repair common errors in an automated manner. For example, when a conflict in configuration parameters is found or the installation script fails to execute, the server will automatically select and execute the preset automatic repair steps by analyzing the error log and checking the abnormal parameters, such as regenerating the configuration file, repairing the installation script, or even restarting the relevant services or nodes, and all processing processes will generate detailed error logs for subsequent review and analysis by the operation and maintenance personnel.

[0103] In the traditional middleware deployment process, once a parameter error is found, manual intervention is often required to correct it, which is time-consuming and inefficient. In this embodiment, it is possible to determine whether the execution process in the middleware deployment process deviates from the expected behavior, and then automatically correct the deviated execution process, so that the effectiveness of the middleware deployment process can be monitored in real time, and the preset error handling process is automatically triggered when an abnormality is found, thereby minimizing manual intervention.

[0104] In an exemplary embodiment, the middleware deployment process and middleware performance are monitored in real time to analyze the middleware performance and operating environment status; the middleware performance and operating environment status are adaptively learned to predict performance bottlenecks that may occur in the future and obtain prediction results; and the relevant configurations are pre-optimized based on the prediction results to obtain updated configuration files and optimization records.

[0105] Alternatively, a performance bottleneck may refer to the inability of certain resources (such as CPU, memory, disk, network bandwidth, etc.) to meet current or future demands at a specific moment or as the load increases, resulting in a degradation of system performance or an inability to effectively provide services.

[0106] Compared with the static configuration in the traditional middleware deployment process, this embodiment supports adaptive optimization of configuration, can adjust configuration parameters according to real-time data and historical data, improve the flexibility and adaptability of middleware deployment, and improve the intelligence level and efficiency of middleware deployment. In addition, in this embodiment, through real-time monitoring and adaptive methods, the performance and reliability of the middleware can be continuously improved throughout the life cycle of the middleware deployment, while reducing the burden on operation and maintenance personnel, so that the middleware can maintain the best operating state in different usage scenarios. At the same time, this adaptive optimization can improve the efficiency of the middleware deployment process and enhance the adaptability of the middleware to changes.

[0107] In another embodiment, a middleware deployment method is provided, the method comprising:

[0108] Get the customized configuration parameters, and parse the configuration parameters to obtain the parsed configuration parameters.

[0109] Dynamically generate an installation script based on the parsed configuration parameters and the pre-set script template; use the predefined configuration file template to generate an initial configuration file adapted to the environment, and replace the default values ​​in the initial configuration file with the customized configuration parameters to generate a configuration file.

[0110] Through the preset deployment logic mechanism, verify whether there is a conflict between the configuration parameters of the configuration file; when it is determined that there is no conflict between the configuration parameters of the configuration file, judge whether the configuration file complies with the standard specifications through the preset configuration syntax and structure verification mechanism; when it is determined that the configuration file complies with the standard specifications, obtain the verified configuration file.

[0111] When it is determined that the installation directory of the target deployment node exists, determine whether the environment version meets the middleware operation requirements; when it is determined that the environment version meets the middleware operation requirements, traverse the database of the target deployment node to determine whether the configuration parameters exist in the database of the target deployment node; when the configuration parameters exist in the database of the target deployment node, complete the second verification of the configuration parameters to correct the installation script and obtain the corrected installation script.

[0112] The verified configuration file and the corrected installation script are transferred to the target deployment node; the corrected installation script is run through the preset task execution interface; during the running of the corrected installation script, the environment setting and parameter adjustment of the middleware are performed according to the verified configuration file to complete the deployment of the middleware on the target deployment node.

[0113] The middleware is cluster-deployed on the cluster nodes, and the running status of the cluster nodes is monitored for abnormalities according to the preset time period to obtain abnormal information; when it is determined that there is an abnormality in the cluster node, the faulty node is located according to the abnormal information; the faulty node is automatically restarted, or the middleware is redeployed on the faulty node.

[0114] In this embodiment, according to the parsed configuration parameters and the pre-set script template, the installation script is dynamically generated, which can be flexibly adapted according to different deployment environments, version requirements and target devices (devices for the target deployment node), and the installation script adapted to the specific environment is automatically generated, which enhances the flexibility and adaptability of the middleware deployment, and can avoid the tedious steps of manually writing scripts, greatly reduce human errors, and thus accelerate the deployment process of the middleware. Through the preset deployment logic mechanism and the preset configuration syntax and structure verification mechanism, it is ensured that the configuration file in the deployment process complies with the standard specifications, reduces potential configuration errors, conflicts and security vulnerabilities, and can effectively improve the success rate, stability and security of the middleware deployment. The second verification of the configuration parameters can effectively avoid human errors, improve the efficiency of the deployment process, reduce redundant operations, and ensure the consistency and integrity of the middleware deployment environment. In the process of running the corrected installation script, the necessary environment settings and parameter adjustments can be made to the middleware according to the verified configuration file, so that the deployed middleware can be adaptively configured according to the environmental characteristics of the target deployment node to ensure the best performance. Through the automated deployment of middleware, the interference of human factors is reduced, the deployment errors of middleware are reduced, and the stability and maintainability of the middleware after deployment are improved.

[0115] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0116] Based on the same inventive concept, the embodiment of the present application also provides a middleware deployment device for implementing the middleware deployment method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more middleware deployment device embodiments provided below can refer to the limitations on the middleware deployment method above, and will not be repeated here.

[0117] In an exemplary embodiment, Figure 4 As shown, a middleware deployment device is provided, including: an acquisition module 402, a generation module 404, a verification module 406 and a deployment module 408, wherein:

[0118] The acquisition module 402 is used to acquire the customized configuration parameters and parse the configuration parameters to obtain the parsed configuration parameters;

[0119] The generation module 404 is used to dynamically generate an installation script according to the parsed configuration parameters; and generate a configuration file according to the customized configuration parameters;

[0120] Verification module 406, used to perform a first verification on the configuration file to obtain a verified configuration file; and perform a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script;

[0121] The deployment module 408 is used to deploy the middleware to the target deployment node according to the verified configuration file and the corrected installation script.

[0122] In an exemplary embodiment, during the system startup phase, the configuration acquisition module 402 is initialized through a preset graphical user interface. The user customizes and inputs a series of key configuration parameters according to current business needs. These parameters include but are not limited to the deployment version information of the middleware, the target deployment environment identifier, the unique identifier information of the deployment node, the connection configuration information of the relevant database, and the performance tuning parameters. The system verifies the input validity in real time to ensure data integrity and compliance.

[0123] In an exemplary embodiment, based on the information received from the acquisition module 402, the generation module 404 performs the following operations:

[0124] Analysis and parsing: Perform in-depth analysis of the configuration parameters entered by the user, extract relevant information, and perform syntax and logic verification.

[0125] Customized script generation: Dynamically generate customized installation scripts based on different deployment environments, version iterations, and target deployment node characteristics. This process relies on highly modularized script templates to achieve adaptation to specific environments.

[0126] Configuration file generation: Use predefined configuration file templates to generate an initial configuration file adapted to the environment, and automatically replace the default values ​​in the initial configuration file with the custom parameters entered by the user to generate a configuration file, which can ensure that the generated configuration file complies with standards and unified specifications.

[0127] In an exemplary embodiment, the verification module 406 is used to perform a first verification on the configuration file to obtain a verified configuration file, including: verifying whether there are conflicts or inconsistencies between configuration parameters through a middleware deployment logic reasoning mechanism. Ensuring that the generated configuration file complies with predefined security policies and performing security assessments. Ensuring that the generated configuration file complies with standard specifications through a syntax and structure verification mechanism.

[0128] In an exemplary embodiment, the verification module 406 performs a second verification on the configuration parameters to correct the installation script and obtain a corrected installation script, including: through the preset deployment node check interface, the system automatically checks whether the installation directory of the deployment node exists; if not, create the corresponding installation directory. Determine whether the JDK version corresponding to the middleware deployment version has been installed; if not, automatically download and install the corresponding JDK version based on the middleware deployment version; if the corresponding JDK version has been installed, prohibit repeated installation to avoid redundancy. Perform a traversal query on the database of the target deployment node to determine whether the required database and table exist; if not, automatically create the database and corresponding data table.

[0129] In an exemplary embodiment, the deployment module 408 uses a preset secure transmission interface to batch transmit the verified configuration files and the corrected installation scripts to the target deployment node. This process ensures that the data maintains integrity and security during transmission, and uses encrypted transmission technology to prevent data leakage.

[0130] In an exemplary embodiment, the deployment module 408 implements the installation and configuration tasks step by step through the preset node task execution interface (task execution interface) according to the verified configuration file and the corrected installation script, based on the diversified deployment environment, version iteration, identification information of the target deployment node, etc. This process ensures that the middleware is accurately and standardizedly deployed to the specified target deployment node, ensuring the high availability and stability of the system.

[0131] In an exemplary embodiment, the workflow of the error detection module is as follows: Figure 5As shown, the middleware deployment device also includes an error detection module; in any of the above modules, the error detection module is integrated. The error detection module integrates a multi-level detection mechanism to ensure that potential errors can be identified and handled in a timely manner during configuration management and middleware deployment. The module adopts a dynamic exception capture mechanism, which monitors the deviation between module results and expected behaviors in real time by performing abnormal monitoring and judgment at each module node. Once an abnormality is found, the system will automatically trigger the preset error handling process, perform preset optional automatic corrections for common errors, such as making necessary adjustments to configuration parameters, and generate a detailed error log. Secondly, the error detection module also introduces a rule-based verification system to conduct a comprehensive review of the generated configuration files and installation execution scripts, and perform logical reasoning on the relationship between configuration parameters to ensure that there are no conflicts or inconsistencies. The error detection module also provides an intuitive visual interface to display the system health status and historical error records in real time, helping operation and maintenance personnel to quickly locate the source of the problem.

[0132] In an exemplary embodiment, the middleware deployment device also includes an adaptive configuration optimization module, and the system can monitor the middleware deployment process and middleware performance in real time, obtain monitoring data, and automatically adjust configuration parameters according to the monitoring data. In the adaptive configuration optimization module, through adaptive learning, the system can predict and adapt to future changes and achieve dynamic optimization of configuration. This adaptive capability enables the system to automatically adjust the deployment strategy based on historical data and real-time monitoring, significantly improving the intelligence level and efficiency of deployment.

[0133] In an exemplary embodiment, the workflow of the self-healing module is as follows: Figure 6 As shown, the middleware deployment device also includes a self-healing module; when an abnormal state of cluster deployment occurs, the self-healing module can automatically restart the faulty node or redeploy the application according to the error information to minimize manual intervention and service interruption time. This method greatly improves the maintainability and flexibility of the system, and demonstrates excellent management efficiency and dynamic adaptability. That is, the self-healing module is designed to perform regular self-healing detection on the cluster nodes of the aforementioned deployed middleware. When the cluster nodes are in an abnormal state, the faulty nodes can be restarted or the applications can be redeployed according to common error information, which can significantly improve the maintainability and flexibility of the system and improve the dynamic adaptability of middleware management.

[0134] Each module in the above middleware deployment device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0135] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 7 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store configuration parameter data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a middleware deployment method is implemented.

[0136] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0137] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0138] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0139] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0140] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0141] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0142] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0143] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A middleware deployment method, characterized in that: The method comprises: Obtaining custom configuration parameters, and parsing the configuration parameters to obtain parsed configuration parameters; Dynamically generate an installation script based on the parsed configuration parameters; and generate a configuration file based on the customized configuration parameters; Performing a first verification on the configuration file to obtain a verified configuration file; and performing a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script; The middleware is deployed to a target deployment node according to the verified configuration file and the corrected installation script.

2. The method according to claim 1, characterized in that The performing a second verification on the configuration parameters includes: When it is determined that the installation directory of the target deployment node exists, determine whether the environment version meets the middleware operation requirements; When it is determined that the environment version meets the middleware operation requirements, traverse the database of the target deployment node to determine whether the configuration parameter exists in the database of the target deployment node; When the configuration parameters exist in the database of the target deployment node, the second verification of the configuration parameters is completed.

3. The method according to claim 1, characterized in that The deploying the middleware according to the verified configuration file and the corrected installation script includes: Transmitting the verified configuration file and the corrected installation script to a target deployment node; Run the corrected installation script through the preset task execution interface; During the process of running the corrected installation script, the environment settings and parameter adjustments are performed on the middleware according to the verified configuration file to complete the deployment of the middleware on the target deployment node.

4. The method according to claim 1, characterized in that The first verification of the configuration file to obtain a verified configuration file includes: Verify, through a preset deployment logic mechanism, whether there is a conflict between the configuration parameters of the configuration file; When it is determined that there is no conflict between the configuration parameters of the configuration file, judging whether the configuration file complies with standard specifications through a preset configuration syntax and structure verification mechanism; When it is determined that the configuration file complies with the standard specification, a verified configuration file is obtained.

5. The method according to claim 1, characterized in that After deploying the middleware to the target deployment node, the method further includes: The middleware is cluster-deployed on cluster nodes, and abnormality monitoring is performed on the running status of the cluster nodes according to a preset time period to obtain abnormality information; When it is determined that the cluster node is abnormal, locating the faulty node according to the abnormal information; An automatic restart operation is performed on the failed node, or the middleware is redeployed on the failed node.

6. The method according to claim 1, characterized in that dynamically generating an installation script according to the parsed configuration parameters; And generate a configuration file according to the customized configuration parameters, including: Dynamically generate an installation script according to the parsed configuration parameters and a pre-set script template; A predefined configuration file template is used to generate an initial configuration file adapted to the environment, and the customized configuration parameters are used to replace the default values ​​in the initial configuration file to generate a configuration file.

7. A middleware deployment device, characterized in that: The device comprises: An acquisition module is used to acquire custom configuration parameters and parse the configuration parameters to obtain the parsed configuration parameters; A generation module, used to dynamically generate an installation script according to the parsed configuration parameters; and to generate a configuration file according to the customized configuration parameters; A verification module, configured to perform a first verification on the configuration file to obtain a verified configuration file; and perform a second verification on the configuration parameters to correct the installation script to obtain a corrected installation script; A deployment module is used to deploy the middleware to a target deployment node according to the verified configuration file and the corrected installation script.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images