Method, device, storage medium and electronic equipment for configuring middleware

Abstract

The application provides a middleware configuration method and device, a storage medium and an electronic device. The method comprises: obtaining historical middleware and configuration information of the historical middleware, wherein the configuration information at least comprises version information of the historical middleware; determining a plurality of middleware categories according to the configuration information, and determining a configuration parameter threshold of each middleware category, wherein the configuration parameter threshold is determined according to a maximum value and a minimum value of a configuration parameter of the historical middleware in each middleware category, and the configuration parameter at least comprises a memory size; obtaining a target middleware, determining a target middleware category of the target middleware, and configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories. Through the application, the problem that the configuration of the middleware is inaccurate due to manual configuration according to experience in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of middleware configuration, and in particular, to a middleware configuration method, configuration device, storage medium and electronic device. Background Art

[0002] The use of middleware can reduce the difficulty of project code development, thereby improving developer productivity. However, when using middleware, its configuration parameters are often independently configured based on personal experience, lacking a unified configuration template. This results in significant subjective influence during the initial project code build. Middleware and its alerts are often inseparable. Middleware configuration affects the frequency and content of intermediate alerts. Furthermore, changes to middleware configuration may also trigger alerts. Existing technical solutions for alert information management include the following: 1) Classify alerts by severity and formulate corresponding response strategies based on their severity. For example, Level P1 indicates that continuous occurrence requires immediate action, Level P2 indicates alerts requiring ongoing attention, and Level P3 indicates that alerts can be ignored. 2) Alert information is clustered using text clustering, and alerts with the same attributes are assigned different severity levels and frequencies, thereby reducing alert noise and prioritizing urgent issues. 3) Machine learning algorithms are used to cluster alerts of the same type, deduplicate alerts, and reduce the number of alerts. If a newly triggered alarm has been previously triggered for the same type of alarm with similar content, the alarm frequency can be reduced accordingly based on the alarm level, allowing operations and maintenance developers to prioritize other high-level alarms.

[0003] However, the above-mentioned technical solutions also present the following technical issues: The disadvantage of the middleware configuration solution and alarm management technology is that they are managed too independently, failing to consider that the triggering of alarms may be related to the middleware configuration. Furthermore, middleware configuration currently relies on the developer's experience and manual operation, and its accuracy cannot be guaranteed. Regarding alarm management, existing technologies do not consider governance at the source, namely, the middleware configuration, and fail to integrate configuration information with alarm information or standardize configuration operations.

[0004] Therefore, a method for intelligent management of middleware is needed to solve the above technical problems. Summary of the Invention

[0005] The main purpose of the present application is to provide a middleware configuration method, configuration device, storage medium and electronic device, so as to at least solve the problem in the prior art that middleware configuration is performed manually based on experience, resulting in inaccurate configuration.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a middleware configuration method is provided, comprising: obtaining historical middleware and obtaining configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware; determining multiple middleware categories based on the configuration information, and determining a configuration parameter threshold for each of the middleware categories, wherein the configuration parameter threshold is determined based on the maximum and minimum values ​​of the configuration parameters of the historical middleware in each of the middleware categories, and the configuration parameters at least include memory size; obtaining target middleware, determining a target middleware category of the target middleware, and configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0007] Optionally, obtaining historical middleware and obtaining configuration information of the historical middleware includes: obtaining a historical project code, wherein the historical project code is a code representing a historical project, and the historical middleware is applied to the historical project; searching for a data packet corresponding to the historical project code through a command line to obtain a historical data packet, performing keyword filtering on the historical data packet to obtain the name of the historical middleware; obtaining a configuration file of the historical middleware according to the name of the historical middleware, and obtaining information in the configuration file to obtain the configuration information.

[0008] Optionally, determining multiple middleware categories based on the configuration information includes: performing feature extraction on the configuration information to obtain multiple feature data, wherein the feature data at least includes the version information of the historical middleware; performing numerical processing on the multiple feature data to obtain the feature data after numerical processing, and performing cluster analysis on the feature data after numerical processing to obtain multiple middleware categories.

[0009] Optionally, determining the target middleware category of the target middleware includes: obtaining the name of the target middleware, and obtaining target configuration information of the target middleware according to the name of the target middleware; classifying the target configuration information through a classification algorithm to obtain the target middleware category corresponding to the target middleware.

[0010] Optionally, after configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, the method further includes: obtaining historical alarm information, wherein the historical alarm information is generated when the middleware fails and includes at least the historical alarm time; determining alarm-related characteristics based on the historical alarm information, wherein the alarm-related characteristics are characteristics corresponding to historical characteristic values ​​that cause the middleware to fail and generate the historical alarm information; determining the configuration parameter threshold of the middleware corresponding to the alarm-related characteristics, and obtaining the actual configuration parameter value of the middleware, and determining whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold.

[0011] Optionally, determining alarm-related features based on the historical alarm information includes: obtaining historical configuration information corresponding to the historical alarm time, establishing historical feature values ​​based on the historical configuration information, wherein the historical feature values ​​at least include middleware attribute values ​​and middleware attribute change values; performing correlation analysis on the historical feature values ​​to obtain a correlation coefficient corresponding to each of the historical feature values, and determining the features corresponding to a predetermined number of the historical feature values ​​with the largest correlation coefficient as the alarm-related features.

[0012] Optionally, determining whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold includes: calculating the discreteness of the actual configuration parameter, and when the discreteness exceeds the configuration parameter threshold, issuing the alarm message to warn the middleware of a failure; when the discreteness does not exceed the configuration parameter threshold, not issuing the alarm message.

[0013] According to another aspect of the present application, a middleware configuration device is provided, comprising: a first acquisition unit, configured to acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware; a first determination unit, configured to determine multiple middleware categories based on the configuration information, and determine a configuration parameter threshold for each of the middleware categories, wherein the configuration parameter threshold is determined based on the maximum and minimum values ​​of the configuration parameters of the historical middleware in each of the middleware categories, and the configuration parameters at least include memory size; a configuration unit, configured to acquire target middleware, determine a target middleware category of the target middleware, and configure the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0014] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the configuration methods.

[0015] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for executing any one of the configuration methods.

[0016] By applying the technical solution of the present application, historical middleware is obtained, and configuration information of the historical middleware is obtained. Based on the configuration information, multiple middleware categories are determined, and the configuration parameter thresholds of each middleware category are determined. Then, the target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured according to the configuration parameter thresholds corresponding to the target middleware category. In this way, configuration can be performed according to the category of the target middleware. Compared with the problem in the prior art where manual configuration based on experience leads to inaccurate configuration, the present application configures the target middleware based on the configuration parameter thresholds corresponding to the target middleware category, and intelligently configures the target middleware. Therefore, it can solve the problem in the prior art where manual configuration based on experience leads to inaccurate configuration of the middleware, and improve the accuracy of the middleware configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings that constitute part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0018] Figure 1 A hardware structure block diagram of a mobile terminal for executing a middleware configuration method provided in an embodiment of the present application is shown;

[0019] Figure 2 A schematic diagram showing a flow chart of a method for configuring middleware provided in an embodiment of the present application is shown;

[0020] Figure 3 A schematic diagram showing a flow chart of a specific middleware configuration method provided in an embodiment of the present application is shown;

[0021] Figure 4 A schematic diagram showing a flow chart of a method for configuring target middleware provided in an embodiment of the present application is shown;

[0022] Figure 5 A schematic diagram of a middleware alarm process provided by an embodiment of the present application is shown;

[0023] Figure 6 The figure shows a structural block diagram of a middleware configuration device provided in an embodiment of the present application.

[0024] The above drawings include the following reference numerals:

[0025] 102. Processor; 104. Memory; 106. Transmission device; 108. Input / output device. DETAILED DESCRIPTION

[0026] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0027] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] For ease of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0030] Code repository: A code repository, also known as a repository, resource library, or version library, refers to a data structure on disk in a version control system, containing files, directories, and metadata. A code repository is a public or private location where a large amount of source code is stored. A code repository also typically includes configuration files and property files, as these files are essential for building code.

[0031] Middleware: Middleware is a type of software that enables collaboration, resource sharing, and service provisioning between applications. Common types of middleware include transactional middleware, procedural middleware, message-oriented middleware, object-oriented middleware, and web application server middleware.

[0032] Maven: A project object model that manages project builds through a short description. It is also a software project management tool for reporting and documentation. Maven can be used to manage project dependencies and project builds.

[0033] As introduced in the background technology, in the prior art, manual configuration of middleware based on experience leads to inaccurate configuration. In order to solve the problem of inaccurate configuration caused by manual configuration of middleware based on experience, the embodiments of the present application provide a middleware configuration method, configuration device, storage medium and electronic device.

[0034] The technical solutions in the embodiments of the present invention will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention.

[0035] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 FIG. 1 is a hardware structure diagram of a mobile terminal of a middleware configuration method according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0036] The memory 104 can be used to store computer programs, such as software programs of application software and modules, such as a computer program corresponding to the configuration method of the middleware in the embodiments of the present application. The processor 102 can execute various functional applications and data processing, i.e., implement the above method, by running the computer programs stored in the memory 104. The memory 104 can include a high-speed random access memory, and can further include a nonvolatile memory, such as one or more magnetic storage devices, flash memories, or other nonvolatile solid-state memories. In some examples, the memory 104 can further include memories disposed remotely with respect to the processor 102, which can be connected to the mobile terminal through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The transmission device 106 is used to receive or send data via a network. The specific examples of the above network can include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.

[0037] In the embodiments, a configuration method of middleware running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0038] Figure 2 is a flowchart of the configuration method of the middleware according to the embodiments of the present application. As shown in Figure 2 , the method includes the following steps:

[0039] In step S201, a historical middleware is acquired, and configuration information of the historical middleware is acquired, wherein the configuration information at least includes version information of the historical middleware.

[0040] Specifically, in order to establish a configuration template of the middleware, a configuration template is established according to the historical middleware and the configuration information of the historical middleware. The configuration information is information contained in a configuration file, and at least includes version information of the historical middleware. The historical middleware is a plurality of middlewares used in the past.

[0041] Step S202: determining multiple middleware categories based on the configuration information, and determining a configuration parameter threshold for each middleware category, wherein the configuration parameter threshold is determined based on the maximum and minimum values ​​of the historical configuration parameters of the middleware in each middleware category, the configuration parameters including at least memory size;

[0042] Specifically, classification is performed based on the above configuration information, that is, multiple middleware are divided into multiple categories, namely middleware categories, according to the configuration information. After classification, the configuration parameters of the middleware in each category are counted, so that the maximum and minimum values ​​of the configuration parameters of the middleware in each category are obtained, thereby determining the configuration parameter threshold. The above configuration parameter threshold is a numerical range, for example, it can be a range from the minimum value to the maximum value of each parameter.

[0043] Step S203 , acquiring target middleware, determining a target middleware category of the target middleware, and configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0044] Specifically, after determining the configuration parameter thresholds for each category based on historical middleware and its configuration information, the target middleware can be configured. First, determine which of the above middleware categories the target middleware belongs to, and then configure the target middleware according to the configuration parameter thresholds corresponding to the corresponding middleware category.

[0045] Through this embodiment, historical middleware is obtained, and configuration information of the historical middleware is obtained. Based on the configuration information, multiple middleware categories are determined, and configuration parameter thresholds for each middleware category are determined. Then, target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured based on the configuration parameter thresholds corresponding to the target middleware category. This allows configuration based on the target middleware category. Compared to the prior art, where manual configuration based on experience can lead to inaccurate configuration, the present application configures the target middleware based on the configuration parameter thresholds corresponding to the target middleware category, performing intelligent configuration of the target middleware. Therefore, the prior art problem of manual configuration based on experience leading to inaccurate configuration of middleware is solved, and the accuracy of middleware configuration is improved.

[0046] In the specific implementation process, the above step S201 obtains the historical middleware and obtains the configuration information of the above historical middleware, which can be achieved by the following steps: obtaining the historical project code, wherein the above historical project code is a code representing the historical project, and the above historical middleware is applied to the above historical project; searching the data packet corresponding to the above historical project code through the command line to obtain the historical data packet, filtering the above historical data packet by keywords to obtain the name of the above historical middleware; obtaining the configuration file of the above historical middleware according to the name of the above historical middleware, and obtaining the information in the above configuration file to obtain the above configuration information. This method searches and obtains the configuration information of the historical middleware according to the above method, so that the configuration information of the historical middleware can be accurately obtained.

[0047] Specifically, first read all historical project codes from the code repository, then scan the various historical data packages that the historical project codes depend on through the Maven command line "mvn dependency:tree", and then extract the name of the historical middleware that the project depends on through keyword filtering, and obtain the corresponding configuration information from its configuration file.

[0048] To accurately classify middleware, step S202 determines multiple middleware categories based on the configuration information. This can be accomplished by: performing feature extraction on the configuration information to obtain multiple feature data, wherein the feature data includes at least the version information of the historical middleware; performing numerical processing on the multiple feature data to obtain the numerically processed feature data; and performing cluster analysis on the numerically processed feature data to obtain multiple middleware categories. This method first extracts features from the configuration information and then performs cluster analysis, which can make the data processing process more standardized and the classification more accurate.

[0049] During the specific implementation, feature data is created based on the configuration information described above. This means that features are extracted from the configuration information. Feature data may include the number of middleware, middleware version, whether it is a direct dependency, and the project's business category. Project business categories include deposits and withdrawals. Each feature data is digitized and classified using the kmeans clustering algorithm.

[0050] In some optional embodiments, step S203 of determining the target middleware category of the target middleware can be achieved by: obtaining the name of the target middleware, obtaining target configuration information for the target middleware based on the name of the target middleware; and classifying the target configuration information using a classification algorithm to obtain the target middleware category corresponding to the target middleware. This method uses a classification algorithm to determine the category of the target middleware, thereby accurately determining the category and facilitating configuration based on the threshold.

[0051] Specifically, after determining the configuration parameter thresholds for each middleware category, if a new project is available, the project code and business type are obtained. The Maven command line "mvn dependency:tree" is then used to scan the various data packages that the new project code depends on. Keyword filtering is then used to extract the names of the target middleware that the project depends on, and the corresponding target configuration information is retrieved from its configuration file. The target configuration information is then classified using the Support Vector Machine (SVM) algorithm to determine the target middleware category corresponding to the target middleware.

[0052] In order to promptly handle middleware failures, after configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category in step S203, the method further includes the following steps: step S301: obtaining historical alarm information, wherein the historical alarm information is generated when the middleware fails and includes at least the historical alarm time; step S302: determining alarm-related features based on the historical alarm information, wherein the alarm-related features are features corresponding to historical feature values ​​that caused the middleware to fail and generate the historical alarm information; step S303: determining the configuration parameter threshold of the middleware corresponding to the alarm-related features, and obtaining the actual configuration parameter value of the middleware, and determining whether to issue an alarm based on the actual configuration parameter value and the configuration parameter threshold. The method warns of a middleware failure through the above steps, thereby enabling timely warning of the failure information and processing.

[0053] In the implementation process, in order to alarm from the perspective of the configuration information of the middleware, first, the log information is scanned to obtain historical middleware alarm events and corresponding solutions. According to the obtained historical alarm time, the historical middleware configuration files in the same period and the front and back intermediate attribute change records (if any) are obtained from the code repository, and the historical alarm information is stored in the configuration file. Then, the alarm-related features are determined, including the middleware name, whether it directly depends on the middleware, the middleware attribute value, the attribute change difference, the alarm category, the project category, etc., and the threshold of the middleware configuration is determined. A comparator is established to monitor the middleware configuration information of each project in real time, and compared with the configuration parameter threshold. If the threshold is exceeded, an alarm warning is given. That is, first, the feature parameters related to the alarm are obtained through the analysis of the historical alarm information, and these feature parameters are monitored, and an alarm is given when the threshold is exceeded.

[0054] In some optional embodiments, the step S302 of determining the alarm-related features according to the historical alarm information can be implemented by the following steps: obtaining the historical configuration information corresponding to the historical alarm time, establishing historical feature values according to the historical configuration information, wherein the historical feature values at least include the middleware attribute value and the middleware attribute change value; performing correlation analysis on the historical feature values to obtain the correlation coefficients corresponding to each historical feature value, and determining the features corresponding to the predetermined number of historical feature values with the largest correlation coefficients as the alarm-related features. This method determines the alarm-related features by calculating the correlation, which can accurately determine the alarm-related features for monitoring.

[0055] Specifically, after determining the alarm-related features, including the middleware name, whether it directly depends on the middleware, the middleware attribute value, the attribute change difference, the alarm category, the project category, etc., the correlation coefficients are calculated, and the features corresponding to the first predetermined number of historical feature values with larger correlation coefficients are determined as the alarm-related features. For example, the first three features can be determined as the alarm-related features by arranging the correlation coefficients from large to small.

[0056] In order to accurately determine whether to issue an alarm information, the step S303 can be implemented by the following steps: calculating the dispersion of the actual configuration parameters, and issuing the alarm information to warn that the middleware has failed when the dispersion exceeds the configuration parameter threshold; and not issuing the alarm information when the dispersion does not exceed the configuration parameter threshold. This method determines whether to issue an alarm information by the size of the dispersion, which can accurately determine whether to issue an alarm information.

[0057] In the specific implementation process, the dispersion indicates the degree of dispersion of the actual configuration parameters. A large dispersion, even exceeding the configuration parameter threshold, indicates that the actual configuration parameters are relatively dispersed and exceed the configuration parameter threshold. In this case, it indicates that the middleware may fail, so an alarm message is issued. On the contrary, if the dispersion does not exceed the configuration parameter threshold, no alarm message is issued.

[0058] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the middleware configuration method of the present application will be described in detail below in conjunction with specific embodiments.

[0059] This embodiment relates to a specific method for configuring middleware, such as Figure 3 As shown, the following steps are included:

[0060] Step S1: Start;

[0061] Step S2: Obtain the code repository project code (historical project code);

[0062] Step S3: Obtain project dependencies and middleware configuration information (historical middleware configuration information);

[0063] Step S4: Establish characteristic values ​​(characteristic data): number of middleware, version name (version information), direct dependency;

[0064] Step S5: performing Kmeans clustering (cluster analysis);

[0065] Step S6: Collect statistics on various types of middleware configuration information, calculate configuration parameter thresholds, and establish a reference template;

[0066] Step S7: End.

[0067] After determining the above configuration parameter thresholds, configure the target middleware of the new project, such as Figure 4 As shown, the following steps are included:

[0068] Step S8: Start;

[0069] Step S9: Obtain the code repository project code;

[0070] Step S10: Obtain project dependencies and middleware configuration information (target configuration information of target middleware);

[0071] Step S11: Determine the category (target middleware category) based on the SVM algorithm;

[0072] Step S12: recommending configuration parameters of corresponding middleware (configuration parameter thresholds corresponding to the target middleware category);

[0073] Step S13: End.

[0074] Figure 5 A schematic diagram of an alarm process provided by this application is shown in FIG. Figure 5 As shown, the following steps are included:

[0075] Step S14: Start;

[0076] Step S15: Scan the log information to obtain historical alarms and solutions;

[0077] Step S16: Obtain the middleware configuration of the same period, as well as the attribute change records before and after;

[0078] Step S17: constructing feature values, performing correlation analysis, and obtaining the most important features that trigger the alarm;

[0079] Step S18: Is it related to the attribute value change? If yes, go to step S19; if not, go to step S23;

[0080] Step S19: Determine the threshold value of the middleware configuration;

[0081] Step S20: monitoring the project middleware configuration information in real time and calculating the dispersion of the configuration information;

[0082] Step S21: Determine whether the threshold is exceeded. If yes, go to step S22; if no, go to step S23.

[0083] Step S22: pre-alarm;

[0084] Step S23: End.

[0085] The embodiments of the present application also provide a configuration device for a middleware. It should be noted that the configuration device for the middleware of the embodiments of the present application can be used to execute the configuration method for the middleware provided in the embodiments of the present application. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions thereof will not be repeated here. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0086] The following introduces the configuration device of the middleware provided in the embodiment of the present application.

[0087] Figure 6 Schematic diagram of a configuration device for middleware according to an embodiment of the present application. Figure 6 As shown, the device includes:

[0088] A first acquiring unit 10 is configured to acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware;

[0089] Specifically, to establish a configuration template for a middleware, a configuration template is established based on historical middleware and its configuration information, where the configuration information is information contained in a configuration file, including at least version information of the historical middleware.

[0090] a first determining unit 20 configured to determine a plurality of middleware categories based on the configuration information, and determine a configuration parameter threshold for each of the middleware categories, wherein the configuration parameter threshold is determined based on a maximum value and a minimum value of a configuration parameter of the historical middleware in each of the middleware categories, the configuration parameter including at least a memory size;

[0091] Specifically, classification is performed based on the above configuration information, that is, multiple middleware are divided into multiple categories, namely middleware categories, according to the configuration information. After classification, the configuration parameters of the middleware in each category are counted, so that the maximum and minimum values ​​of the configuration parameters of the middleware in each category are obtained, thereby determining the configuration parameter threshold. The above configuration parameter threshold is a numerical range, for example, it can be a range from the minimum value to the maximum value of each parameter.

[0092] The configuration unit 30 is configured to obtain target middleware, determine a target middleware category of the target middleware, and configure the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0093] Specifically, after determining the configuration parameter thresholds for each category based on historical middleware and its configuration information, the target middleware can be configured. First, determine which of the above middleware categories the target middleware belongs to, and then configure the target middleware according to the configuration parameter thresholds corresponding to the corresponding middleware category.

[0094] Through this embodiment, historical middleware is obtained, and configuration information of the historical middleware is obtained. Based on the configuration information, multiple middleware categories are determined, and configuration parameter thresholds for each middleware category are determined. Then, target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured based on the configuration parameter thresholds corresponding to the target middleware category. This allows configuration based on the target middleware category. Compared to the prior art, where manual configuration based on experience can lead to inaccurate configuration, the present application configures the target middleware based on the configuration parameter thresholds corresponding to the target middleware category, performing intelligent configuration of the target middleware. Therefore, the prior art problem of manual configuration based on experience leading to inaccurate configuration of middleware is solved, and the accuracy of middleware configuration is improved.

[0095] In a specific implementation process, the first acquisition unit includes a first acquisition module, a filtering module, and a second acquisition module. The first acquisition module is used to obtain a historical project code, wherein the historical project code is a code representing a historical project, and the historical middleware is applied to the historical project; the filtering module is used to search for a data packet corresponding to the historical project code through a command line to obtain a historical data packet, perform keyword filtering on the historical data packet, and obtain the name of the historical middleware; the second acquisition module is used to obtain a configuration file of the historical middleware according to the name of the historical middleware, and obtain information in the configuration file to obtain the configuration information. The device searches and obtains the configuration information of the historical middleware according to the above device, so that the configuration information of the historical middleware can be accurately obtained.

[0096] Specifically, first read all historical project codes from the code repository, then scan the various historical data packages that the historical project codes depend on through the Maven command line "mvn dependency:tree", and then extract the name of the historical middleware that the project depends on through the keyword filtering device, and obtain the corresponding configuration information from its configuration file.

[0097] To accurately classify middleware, the first determination unit includes an extraction module and an analysis module. The extraction module is configured to extract features from the configuration information to obtain multiple feature data, wherein the feature data includes at least the version information of the historical middleware. The analysis module is configured to digitize the multiple feature data to obtain the digitized feature data, and then perform cluster analysis on the digitized feature data to obtain multiple middleware categories. This device first extracts features from the configuration information and then performs cluster analysis, which can make the data processing process more standardized and the classification more accurate.

[0098] During the specific implementation, feature data is created based on the configuration information described above. This means that features are extracted from the configuration information. Feature data may include the number of middleware, middleware version, whether it is a direct dependency, and the project's business category. Project business categories include deposits and withdrawals. Each feature data is digitized and classified using the kmeans clustering algorithm.

[0099] In some optional embodiments, the configuration unit includes a third acquisition module and a classification module. The third acquisition module is configured to acquire the name of the target middleware and, based on the name of the target middleware, acquire target configuration information for the target middleware. The classification module is configured to classify the target configuration information using a classification algorithm to obtain the target middleware category corresponding to the target middleware. The device determines the category of the target middleware using the classification algorithm, thereby accurately determining the category to facilitate configuration based on the threshold.

[0100] Specifically, after determining the configuration parameter thresholds for each middleware category, if a new project is available, the project code and business type are obtained. The Maven command line "mvn dependency:tree" is then used to scan the various data packages that the new project code depends on. Keyword filtering is then used to extract the name of the target middleware that the project depends on, and the corresponding target configuration information is retrieved from its configuration file. The target configuration information is then classified using the Support Vector Machine (SVM) algorithm to determine the target middleware category corresponding to the target middleware.

[0101] In order to promptly handle the failure of the middleware, the above-mentioned device further includes a second acquisition unit, a second determination unit, and a third determination unit. The second acquisition unit is used to obtain historical alarm information, wherein the historical alarm information is generated when the above-mentioned middleware fails and includes at least the historical alarm time; the second determination unit is used to determine the alarm-related characteristics based on the above-mentioned historical alarm information, wherein the above-mentioned alarm-related characteristics are characteristics corresponding to the historical characteristic values ​​that caused the above-mentioned middleware to fail and generate the above-mentioned historical alarm information; the third determination unit is used to determine the above-mentioned configuration parameter threshold of the above-mentioned middleware corresponding to the above-mentioned alarm-related characteristics, and obtain the actual configuration parameter value of the above-mentioned middleware, and determine whether to issue an alarm information based on the above-mentioned actual configuration parameter value and the above-mentioned configuration parameter threshold. The device warns of the failure of the middleware through the above-mentioned steps, so that the fault information can be promptly warned and handled.

[0102] In the specific implementation process, in order to issue an alarm from the perspective of the middleware configuration information, the log information is first scanned to obtain historical middleware alarm events and corresponding solutions. According to the obtained historical alarm time, the historical middleware configuration files of the same period and the previous and subsequent intermediate attribute change records (if any) are obtained from the code repository. The configuration files store historical alarm information. Then, the alarm-related features are determined, including the middleware name, whether it is directly dependent on the middleware, the middleware attribute value, the attribute change difference, the alarm category, the project type, etc., and the threshold of the middleware configuration is determined. A comparator is established to monitor the middleware configuration information of each project in real time, and compare it with the configuration parameter threshold. If the threshold is exceeded, an alarm warning is issued. In other words, first, by analyzing the historical alarm information, the characteristic parameters related to the alarm are obtained, and these characteristic parameters are monitored, and an alarm is issued when the threshold is exceeded.

[0103] In some optional embodiments, the second determination unit includes an establishment module and a determination module. The establishment module is configured to obtain historical configuration information corresponding to the historical alarm time and establish historical feature values ​​based on the historical configuration information, wherein the historical feature values ​​include at least middleware attribute values ​​and middleware attribute change values. The determination module is configured to perform correlation analysis on the historical feature values ​​to obtain a correlation coefficient corresponding to each of the historical feature values, and determine the features corresponding to a predetermined number of the historical feature values ​​with the largest correlation coefficients as the alarm-related features. The device determines the alarm-related features by calculating the correlation, thereby accurately determining the alarm-related features for monitoring.

[0104] Specifically, after determining the alarm-related features, including the middleware name, whether it is directly dependent on the middleware, the middleware attribute value, the attribute change difference, the alarm category, the project type, etc., the correlation coefficient is calculated, and the features corresponding to the first predetermined number of historical feature values ​​with a larger correlation coefficient are used as alarm-related features. For example, if the correlation coefficients are arranged from large to small, the first three features can be used as alarm-related features.

[0105] To accurately determine whether to issue an alarm, the configuration unit includes an issuing module and a non-issuing module. The issuing module calculates the dispersion of the actual configuration parameters and issues the alarm to warn the middleware of a fault if the dispersion exceeds the configuration parameter threshold. The non-issuing module suppresses the alarm if the dispersion does not exceed the configuration parameter threshold. This device determines whether to issue an alarm based on the dispersion, thus accurately determining whether to issue an alarm.

[0106] In the specific implementation process, the dispersion indicates the degree of dispersion of the actual configuration parameters. A large dispersion, even exceeding the configuration parameter threshold, indicates that the actual configuration parameters are relatively dispersed and exceed the configuration parameter threshold. In this case, it indicates that the middleware may fail, so an alarm message is issued. On the contrary, if the dispersion does not exceed the configuration parameter threshold, no alarm message is issued.

[0107] The configuration device of the middleware includes a processor and a memory. The first acquisition unit, the first determination unit, the configuration unit, and the like are all stored as program units in the memory. The processor executes the program units stored in the memory to implement the corresponding functions. The modules are all located in the same processor; alternatively, the modules may be located in different processors in any combination.

[0108] The processor contains a kernel, which retrieves the corresponding program unit from the memory. There can be one or more kernels, and the middleware can be configured by adjusting the kernel parameters.

[0109] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0110] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program. When the program is executed, the device where the computer-readable storage medium is located is controlled to execute the middleware configuration method.

[0111] Specifically, the middleware configuration method includes:

[0112] Step S201: Acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware;

[0113] Specifically, to establish a configuration template for a middleware, a configuration template is established based on historical middleware and its configuration information, where the configuration information is information contained in a configuration file, including at least version information of the historical middleware.

[0114] Step S202: determining multiple middleware categories based on the configuration information, and determining a configuration parameter threshold for each middleware category, wherein the configuration parameter threshold is determined based on the maximum and minimum values ​​of the historical configuration parameters of the middleware in each middleware category, the configuration parameters including at least memory size;

[0115] Specifically, based on the above configuration information, the plurality of middlewares are classified into a plurality of categories, i.e., the middleware categories, and after the classification, the configuration parameters of the middlewares in each category are counted, so that the maximum and minimum values of the configuration parameters of the middlewares in each category are obtained, thereby determining the configuration parameter threshold, which is a numerical range, for example, the range from the minimum value to the maximum value of each parameter.

[0116] In step S203, the target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured according to the configuration parameter threshold corresponding to the target middleware category. The target middleware category is one of the middleware categories.

[0117] Specifically, after the configuration parameter threshold of each category is determined according to the historical middlewares and their configuration information, the target middleware can be configured. First, it is determined which category the target middleware belongs to among the middleware categories, and then the target middleware is configured according to the configuration parameter threshold corresponding to the corresponding middleware category.

[0118] Optionally, the historical middlewares are obtained, and the configuration information of the historical middlewares is obtained, including: obtaining historical project code, wherein the historical project code is code representing a historical project, and the historical middlewares are applied to the historical project; searching for a data packet corresponding to the historical project code through a command line to obtain a historical data packet, and performing keyword filtering on the historical data packet to obtain the name of the historical middleware; obtaining a configuration file of the historical middleware according to the name of the historical middleware, and obtaining information in the configuration file to obtain the configuration information.

[0119] Optionally, a plurality of middleware categories are determined according to the configuration information, including: performing feature extraction on the configuration information to obtain a plurality of feature data, wherein the feature data at least includes the version information of the historical middleware; performing numerical value processing on the plurality of feature data to obtain the feature data after numerical value processing, and performing cluster analysis on the feature data after numerical value processing to obtain the plurality of middleware categories.

[0120] Optionally, the target middleware category of the target middleware is determined, including: obtaining the name of the target middleware, and obtaining the target configuration information of the target middleware according to the name of the target middleware; classifying the target configuration information through a classification algorithm to obtain the target middleware category corresponding to the target middleware.

[0121] Optionally, after configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, the method further includes: obtaining historical alarm information, wherein the historical alarm information is generated when the middleware fails and at least includes the historical alarm time; determining alarm-related characteristics based on the historical alarm information, wherein the alarm-related characteristics are characteristics corresponding to the historical characteristic values ​​that cause the middleware to fail and generate the historical alarm information; determining the configuration parameter threshold of the middleware corresponding to the alarm-related characteristics, and obtaining the actual configuration parameter value of the middleware, and determining whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold.

[0122] Optionally, determining alarm-related features based on the above-mentioned historical alarm information includes: obtaining historical configuration information corresponding to the above-mentioned historical alarm time, establishing historical feature values ​​based on the above-mentioned historical configuration information, wherein the above-mentioned historical feature values ​​at least include middleware attribute values ​​and middleware attribute change values; performing correlation analysis on the above-mentioned historical feature values ​​to obtain the correlation coefficient corresponding to each of the above-mentioned historical feature values, and determining the features corresponding to a predetermined number of the above-mentioned historical feature values ​​with the largest correlation coefficient as the above-mentioned alarm-related features.

[0123] Optionally, determining whether to issue an alarm message is based on the above-mentioned actual configuration parameter value and the above-mentioned configuration parameter threshold, including: calculating the discreteness of the above-mentioned actual configuration parameter, and when the above-mentioned discreteness exceeds the above-mentioned configuration parameter threshold, issuing the above-mentioned alarm message to warn that the above-mentioned middleware has a fault; when the above-mentioned discreteness does not exceed the above-mentioned configuration parameter threshold, not issuing the above-mentioned alarm message.

[0124] An embodiment of the present invention provides a device, comprising a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, at least the following steps are performed:

[0125] Step S201: Acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware;

[0126] Step S202: determining multiple middleware categories based on the configuration information, and determining a configuration parameter threshold for each middleware category, wherein the configuration parameter threshold is determined based on the maximum and minimum values ​​of the historical configuration parameters of the middleware in each middleware category, the configuration parameters including at least memory size;

[0127] Step S203 , acquiring target middleware, determining a target middleware category of the target middleware, and configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0128] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0129] Optionally, obtaining historical middleware and obtaining configuration information of the above historical middleware includes: obtaining a historical project code, wherein the above historical project code is a code representing a historical project, and the above historical middleware is applied to the above historical project; searching for a data packet corresponding to the above historical project code through a command line to obtain a historical data packet, performing keyword filtering on the above historical data packet to obtain the name of the above historical middleware; obtaining a configuration file of the above historical middleware according to the name of the above historical middleware, and obtaining information in the above configuration file to obtain the above configuration information.

[0130] Optionally, multiple middleware categories are determined based on the above-mentioned configuration information, including: performing feature extraction on the above-mentioned configuration information to obtain multiple feature data, wherein the above-mentioned feature data at least includes the above-mentioned version information of the above-mentioned historical middleware; performing numerical processing on the multiple feature data to obtain the above-mentioned feature data after numerical processing, and performing cluster analysis on the above-mentioned feature data after numerical processing to obtain multiple middleware categories.

[0131] Optionally, determining the target middleware category of the above-mentioned target middleware includes: obtaining the name of the above-mentioned target middleware, and obtaining the target configuration information of the above-mentioned target middleware according to the name of the above-mentioned target middleware; classifying the above-mentioned target configuration information through a classification algorithm to obtain the above-mentioned target middleware category corresponding to the above-mentioned target middleware.

[0132] Optionally, after configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, the method further includes: obtaining historical alarm information, wherein the historical alarm information is generated when the middleware fails and at least includes the historical alarm time; determining alarm-related characteristics based on the historical alarm information, wherein the alarm-related characteristics are characteristics corresponding to the historical characteristic values ​​that cause the middleware to fail and generate the historical alarm information; determining the configuration parameter threshold of the middleware corresponding to the alarm-related characteristics, and obtaining the actual configuration parameter value of the middleware, and determining whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold.

[0133] Optionally, the alarm-related features are determined according to the historical alarm information, including: obtaining historical configuration information corresponding to the historical alarm time, establishing historical feature values according to the historical configuration information, wherein the historical feature values at least include middleware attribute values and middleware attribute change values; performing correlation analysis on the historical feature values to obtain correlation coefficients corresponding to each of the historical feature values, and determining features corresponding to a predetermined number of historical feature values with the largest correlation coefficients as the alarm-related features.

[0134] Optionally, whether to issue an alarm information is determined according to the actual configuration parameter value and the configuration parameter threshold, including: calculating a dispersion degree of the actual configuration parameter, and issuing the alarm information to warn that the middleware has failed in a case where the dispersion degree exceeds the configuration parameter threshold; and not issuing the alarm information in a case where the dispersion degree does not exceed the configuration parameter threshold.

[0135] The application also provides a computer program product adapted to execute the program of initializing at least the following method steps when executed on a data processing device:

[0136] Step S201, obtaining historical middleware and obtaining configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware;

[0137] Step S202, determining a plurality of middleware categories according to the configuration information, and determining a configuration parameter threshold of each of the middleware categories, wherein the configuration parameter threshold is determined according to a maximum value and a minimum value of a configuration parameter of the historical middleware in each of the middleware categories, and the configuration parameter at least includes a memory size;

[0138] Step S203, obtaining target middleware, determining a target middleware category of the target middleware, and configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories.

[0139] Optionally, obtaining historical middleware and obtaining configuration information of the historical middleware, including: obtaining historical project code, wherein the historical project code is code representing a historical project, and the historical middleware is applied to the historical project; searching a data packet corresponding to the historical project code through a command line to obtain a historical data packet, performing keyword filtering on the historical data packet to obtain a name of the historical middleware; obtaining a configuration file of the historical middleware according to the name of the historical middleware, and obtaining information in the configuration file to obtain the configuration information.

[0140] Optionally, the determining the plurality of middleware categories according to the configuration information comprises: performing feature extraction on the configuration information to obtain a plurality of feature data, wherein the feature data at least comprises the version information of the historical middleware; performing numerical value processing on the plurality of feature data to obtain the feature data after numerical value processing, and performing cluster analysis on the feature data after numerical value processing to obtain the plurality of middleware categories.

[0141] Optionally, the determining the target middleware category of the target middleware comprises: obtaining the name of the target middleware, and obtaining the target configuration information of the target middleware according to the name of the target middleware; and classifying the target configuration information by using a classification algorithm to obtain the target middleware category corresponding to the target middleware.

[0142] Optionally, after the target middleware is configured according to the configuration parameter threshold corresponding to the target middleware category, the method further comprises: obtaining historical alarm information, wherein the historical alarm information is generated in the case that the middleware fails and at least comprises a historical alarm time; determining alarm-related features according to the historical alarm information, wherein the alarm-related features are features corresponding to historical feature values of the middleware that fail and generate the historical alarm information; determining the configuration parameter threshold of the middleware corresponding to the alarm-related features, and obtaining an actual configuration parameter value of the middleware, and determining whether to issue an alarm information according to the actual configuration parameter value and the configuration parameter threshold.

[0143] Optionally, the determining the alarm-related features according to the historical alarm information comprises: obtaining historical configuration information corresponding to the historical alarm time, and establishing historical feature values according to the historical configuration information, wherein the historical feature values at least comprise middleware attribute values and middleware attribute change values; performing correlation analysis on the historical feature values to obtain a correlation coefficient corresponding to each historical feature value, and determining features corresponding to a predetermined number of historical feature values with the largest correlation coefficients as the alarm-related features.

[0144] Optionally, the determining whether to issue an alarm information according to the actual configuration parameter value and the configuration parameter threshold comprises: calculating a dispersion degree of the actual configuration parameter, and issuing the alarm information to warn that the middleware fails in the case that the dispersion degree exceeds the configuration parameter threshold; and not issuing the alarm information in the case that the dispersion degree does not exceed the configuration parameter threshold.

[0145] It should be apparent to those skilled in the art that the modules or steps of the application described above can be implemented with a general purpose computer, and can be centralized in a single computer or distributed among a network of computers, and can be implemented with program code executable by a computer, and thus can be stored in a storage device and executed by a computer, and in some cases, the steps shown or described can be executed in a different order than shown or described, or can be implemented as separate integrated circuit modules or as a single integrated circuit module, and thus the application is not limited to any particular combination of hardware and software.

[0146] Those skilled in the art will appreciate that embodiments of the application can be devised for a method, a system, or a computer program product. Accordingly, the application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the application can be in the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage media, etc.) embodying computer readable program code.

[0147] The present application is described in reference to the flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 The means for implementing each one or more flow or steps and / or blocks in the flowchart illustrations and / or block diagrams can be implemented by a machine such as a computer, a processor, or other programmable data processing apparatus in the form of a series of one or more computer readable program code means or steps embodied in the computer readable program code means. Figure 1 The means for implementing each one or more flow or steps and / or blocks in the flowchart illustrations and / or block diagrams can be implemented by a machine such as a computer, a processor, or other programmable data processing apparatus in the form of a series of one or more computer readable program code means or steps embodied in the computer readable program code means.

[0148] The computer readable program code means or steps can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 The means for implementing each one or more flow or steps and / or blocks in the flowchart illustrations and / or block diagrams can be implemented by a machine such as a computer, a processor, or other programmable data processing apparatus in the form of a series of one or more computer readable program code means or steps embodied in the computer readable program code means. Figure 1 The means for implementing each one or more flow or steps and / or blocks in the flowchart illustrations and / or block diagrams can be implemented by a machine such as a computer, a processor, or other programmable data processing apparatus in the form of a series of one or more computer readable program code means or steps embodied in the computer readable program code means.

[0149] The computer readable program code means or steps can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0150] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0151] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0152] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0153] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0154] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0155] 1) In the middleware configuration method of the present application, historical middleware is obtained, and configuration information of the historical middleware is obtained. Based on the configuration information, multiple middleware categories are determined, and the configuration parameter threshold of each middleware category is determined. Then, the target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured according to the configuration parameter threshold corresponding to the target middleware category. In this way, the configuration can be performed according to the category of the target middleware. Compared with the problem in the prior art where manual configuration based on experience leads to inaccurate configuration, the present application configures the target middleware based on the configuration parameter threshold corresponding to the target middleware category, and intelligently configures the target middleware. Therefore, it can solve the problem in the prior art where manual configuration based on experience leads to inaccurate configuration, and improve the accuracy of the middleware configuration.

[0156] 2) In the middleware configuration device of the present application, historical middleware is obtained, and configuration information of the historical middleware is obtained. Based on the configuration information, multiple middleware categories are determined, and the configuration parameter threshold of each middleware category is determined. Then, the target middleware is obtained, the target middleware category of the target middleware is determined, and the target middleware is configured according to the configuration parameter threshold corresponding to the target middleware category. In this way, the configuration can be performed according to the category of the target middleware. Compared with the problem in the prior art where manual configuration based on experience leads to inaccurate configuration, the present application configures the target middleware based on the configuration parameter threshold corresponding to the target middleware category, and intelligently configures the target middleware. Therefore, it can solve the problem in the prior art where manual configuration based on experience leads to inaccurate configuration of the middleware, and improve the accuracy of the middleware configuration.

[0157] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for configuring middleware, characterized in that: include: Acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware; Determining multiple middleware categories based on the configuration information, and determining a configuration parameter threshold for each of the middleware categories, wherein the configuration parameter threshold is determined based on a maximum value and a minimum value of a configuration parameter of the historical middleware in each of the middleware categories, the configuration parameter including at least a memory size; Acquire target middleware, determine a target middleware category of the target middleware, and configure the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories; After configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, the configuration method further includes: Acquire historical alarm information, wherein the historical alarm information is generated when a middleware failure occurs and at least includes a historical alarm time; Determining an alarm-related feature based on the historical alarm information, wherein the alarm-related feature is a feature corresponding to a historical feature value that caused the middleware to fail and generate the historical alarm information; Determine the configuration parameter threshold of the middleware corresponding to the alarm-related feature, obtain the actual configuration parameter value of the middleware, and determine whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold.

2. The configuration method according to claim 1, characterized in that: Obtain the history middleware and its configuration information, including: Acquire a historical project code, wherein the historical project code is a code representing a historical project, and the historical middleware is applied to the historical project; Search the data packet corresponding to the historical project code through the command line to obtain the historical data packet, filter the historical data packet by keywords, and obtain the name of the historical middleware; The configuration file of the history middleware is obtained according to the name of the history middleware, and the information in the configuration file is obtained to obtain the configuration information.

3. The configuration method according to claim 1, wherein: Determine multiple middleware categories based on the configuration information, including: Performing feature extraction on the configuration information to obtain a plurality of feature data, wherein the feature data at least includes the version information of the historical middleware; Numerical processing is performed on the plurality of feature data to obtain the numerically processed feature data, and cluster analysis is performed on the numerically processed feature data to obtain the plurality of middleware categories.

4. The configuration method according to claim 1, wherein: Determining the target middleware category of the target middleware includes: Obtain the name of the target middleware, and obtain target configuration information of the target middleware according to the name of the target middleware; The target configuration information is classified by a classification algorithm to obtain the target middleware category corresponding to the target middleware.

5. The configuration method according to claim 1, wherein: Determining alarm-related features based on the historical alarm information includes: Acquire historical configuration information corresponding to the historical alarm time, and establish historical feature values ​​according to the historical configuration information, wherein the historical feature values ​​at least include a middleware attribute value and a middleware attribute change value; Perform correlation analysis on the historical feature values ​​to obtain a correlation coefficient corresponding to each of the historical feature values, and determine features corresponding to a predetermined number of the historical feature values ​​with the largest correlation coefficients as the alarm-related features.

6. The configuration method according to claim 1, characterized in that: Determining whether to issue an alarm message according to the actual configuration parameter value and the configuration parameter threshold includes: Calculating the dispersion of the actual configuration parameters, and issuing the alarm information when the dispersion exceeds the configuration parameter threshold to warn that the middleware has failed; If the dispersion does not exceed the configuration parameter threshold, the alarm information is not issued.

7. A middleware configuration device, characterized in that: include: A first acquiring unit, configured to acquire historical middleware and configuration information of the historical middleware, wherein the configuration information at least includes version information of the historical middleware; a first determining unit, configured to determine a plurality of middleware categories based on the configuration information, and determine a configuration parameter threshold for each of the middleware categories, wherein the configuration parameter threshold is determined based on a maximum value and a minimum value of a configuration parameter of the historical middleware in each of the middleware categories, the configuration parameter including at least a memory size; a configuration unit, configured to obtain a target middleware, determine a target middleware category of the target middleware, and configure the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the target middleware category is one of the middleware categories; The configuration device also includes: a second acquiring unit, configured to acquire historical alarm information after configuring the target middleware according to the configuration parameter threshold corresponding to the target middleware category, wherein the historical alarm information is generated when a middleware failure occurs and at least includes a historical alarm time; a second determining unit, configured to determine an alarm-related feature based on the historical alarm information, wherein the alarm-related feature is a feature corresponding to a historical feature value that caused the middleware to fail and generate the historical alarm information; The third determining unit is used to determine the configuration parameter threshold of the middleware corresponding to the alarm-related feature, obtain the actual configuration parameter value of the middleware, and determine whether to issue an alarm message based on the actual configuration parameter value and the configuration parameter threshold.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the configuration method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for executing the configuration method described in any one of claims 1 to 6.

Images