System upgrade early warning method and device, equipment and storage medium

Abstract

The application discloses a system upgrade early warning method and device, equipment and a storage medium. The method comprises the following steps: obtaining first product configuration information of a customized development product of a system to be upgraded, obtaining second product configuration information of a latest standard product, comparing the first product configuration information with the second product configuration information based on a preset comparison detection strategy, determining whether there is a configuration abnormal item in the customized development product compared with the latest standard product, detecting whether there is a configuration conflict between the customized development product and the latest standard product, and further detecting a system upgrade risk. If there is a configuration abnormal item in the customized development product compared with the latest standard product, an early warning prompt information is sent to inform a user to make a configuration correction, so that the system upgrade risk is effectively avoided, and the system upgrade is ensured to be successful. The embodiment of the application can be applied to enterprise management systems, such as enterprise resource planning systems and OA systems.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of system development, and particularly relates to a system upgrade early warning method and device, equipment and a storage medium. BACKGROUND

[0002] A standard product of an information management system such as an enterprise resource planning (ERP) will repair past bugs and add new functions when upgrading and iterating, that is, if the latest product needs to be experienced, the ERP must be upgraded. However, in actual situations, most of the ERP systems of enterprises have a large number of customized development products, and upgrading of the products may cause the customized development products or the standard products to be unavailable, thereby causing hidden dangers in system upgrading and bringing bad product experience to users. SUMMARY

[0003] The present application provides a system upgrade early warning method, device, equipment and storage medium to solve the technical problem of product unavailability risk in current system upgrading.

[0004] In order to solve the above technical problem, in a first aspect, the present application provides a system upgrade early warning method, comprising:

[0005] obtaining first product configuration information of a customized development product of a system to be upgraded, and obtaining second product configuration information of a latest standard product;

[0006] comparing the first product configuration information and the second product configuration information based on a preset comparison detection strategy, to determine whether there is a configuration abnormal item in the customized development product compared with the latest standard product;

[0007] if there is a configuration abnormal item in the customized development product compared with the latest standard product, issuing a warning prompt information.

[0008] In some implementation manners, the preset comparison detection strategy includes at least one of a business object detection strategy, a plug-in code detection strategy, a script detection strategy and a configuration file detection strategy.

[0009] In some implementation manners, the first product configuration information includes multi-layer business object extension layer information, the second product configuration information includes standard product business object information, and the comparison of the first product configuration information and the second product configuration information based on the preset comparison detection strategy includes:

[0010] If the preset comparison detection strategy is the business object detection strategy, for first-layer business object extension layer information, business control parameters between the first-layer business object extension layer information and the standard product business object information are compared to determine whether there is an abnormal configuration item in the business object extension layer information compared with the standard product business object information.

[0011] For N-layer business object extension layer information, the standard product business object information and the first to N-1-layer business object extension layer information are merged to obtain merged layer information, and business control parameters between the merged layer information and the N-layer business object extension layer information are compared, where N>1.

[0012] In some implementations, the comparison of the business control parameters between the first-layer business object extension layer information and the standard product business object information includes:

[0013] For the first-layer business object extension layer information, the business object extension layer information and the standard product business object information are deserialized to obtain a first metadata object;

[0014] Based on the first metadata object, first business control information in the business object extension layer information and second business control information in the standard product business object information are determined;

[0015] The first business control information and the second business control information are XML parsed to obtain first business control parameters and second business control parameters, respectively;

[0016] The first business control parameters and the second business control parameters are compared to determine whether there is an abnormal configuration item in the business object extension layer information compared with the standard product business object information.

[0017] In some implementations, the comparison of the business control parameters between the N-layer business object extension layer information and the merged layer information includes:

[0018] For the N-layer business object extension layer information, the standard product business object information is deserialized to obtain a second metadata object;

[0019] If the preset field exists in the N-1th business object extension layer information, the business control modified by the customized development product is queried in the second metadata object, and the parameter of the business control is modified. If the preset field does not exist in the N-1th business object extension layer information, the business control parameter modified by the customized development product is added to the control list in the second metadata object to obtain the merged layer information.

[0020] The business control parameters between the merged layer information and the Nth business object extension layer information are compared.

[0021] In some implementations, the first product configuration information further includes code information, and the comparison between the first product configuration information and the second product configuration information based on the preset comparison detection strategy includes:

[0022] If the preset comparison detection strategy is a plug-in code detection strategy, a target string in the first code information is captured based on the plug-in code detection strategy by using a preset code detection tool.

[0023] Whether there is a configuration exception item in the first product configuration information compared with the second product configuration information is determined based on the target string by using a regular matching mode.

[0024] In some implementations, the first product configuration information further includes script information, and the comparison between the first product configuration information and the second product configuration information based on the preset comparison detection strategy includes:

[0025] If the preset comparison detection strategy is a script detection strategy, a target keyword in the script information is read based on the script detection strategy.

[0026] Whether there is a configuration exception item in the first product configuration information compared with the second product configuration information is determined based on the target keyword by using a regular matching mode.

[0027] In some implementations, the second product configuration information further includes file information of a standard product library file, and the comparison between the first product configuration information and the second product configuration information based on the preset comparison detection strategy includes:

[0028] If the preset comparison detection strategy is a configuration file detection strategy, whether the standard product library file exists in the first product configuration information, whether the file path of the standard product library file in the customized development product is the same as that in the latest standard product, and whether the deployment mode of the standard product library file in the customized development product is the target deployment mode are determined based on the configuration file detection strategy.

[0029] If yes, it is determined that the customized development product has configuration abnormal items compared with the latest standard product.

[0030] In a second aspect, the present application further provides a system upgrade early warning device, comprising:

[0031] An acquisition module is configured to acquire first product configuration information of a customized development product of a system to be upgraded, and acquire second product configuration information of a latest standard product.

[0032] A comparison module is configured to compare the first product configuration information with the second product configuration information based on a preset comparison detection strategy, to determine whether the customized development product has configuration abnormal items compared with the latest standard product.

[0033] An issuing module is configured to issue a warning prompt information if the customized development product has configuration abnormal items compared with the latest standard product.

[0034] In a third aspect, the present application further provides a computer device comprising a processor and a memory, wherein the memory is configured to store a computer program, and the computer program is configured to be executed by the processor to implement the system upgrade early warning method according to the first aspect.

[0035] In a fourth aspect, the present application further provides a computer readable storage medium storing a computer program, and the computer program is configured to be executed by a processor to implement the system upgrade early warning method according to the first aspect.

[0036] In a fifth aspect, the present application further provides a computer program product, and when the computer program product is run on a computer device, the computer device is caused to implement the system upgrade early warning method according to the first aspect.

[0037] Compared with the prior art, the present application has at least the following beneficial effects:

[0038] The present application acquires first product configuration information of a customized development product of a system to be upgraded, and acquires second product configuration information of a latest standard product, and compares the first product configuration information with the second product configuration information based on a preset comparison detection strategy, to determine whether the customized development product has configuration abnormal items compared with the latest standard product, thereby detecting whether there is a configuration conflict between the customized development product and the latest standard product, and further detecting a system upgrade risk. If the customized development product has configuration abnormal items compared with the latest standard product, a warning prompt information is issued to inform a user to make configuration correction, thereby effectively avoiding a system upgrade risk and ensuring successful system upgrade.

[0039] In addition, this application also performs configuration conflict detection from multiple dimensions, such as the plugin code, scripts, business objects and product library files of the customized product, in order to more comprehensively detect the risks of system upgrades and further ensure the security of system upgrades.

[0040] This application also performs layer-by-layer configuration conflict detection for business objects across multiple extension layers. It can detect not only configuration conflicts between customized and standard products, but also configuration conflicts between parallel extension layers, thereby achieving comprehensive detection of product business objects and further ensuring the security of system upgrades. Attached Figure Description

[0041] Figure 1 This is a flowchart illustrating the system upgrade early warning method in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram illustrating the caching process of the second product configuration information in an embodiment of this application;

[0043] Figure 3 This is a schematic diagram of a business object, taking a document as an example, as shown in an embodiment of this application;

[0044] Figure 4 This is a schematic diagram illustrating the detection process of a multi-layered business object extension layer in an embodiment of this application;

[0045] Figure 5 This is a schematic diagram of the system upgrade early warning device shown in the embodiments of this application;

[0046] Figure 6 This is a schematic diagram of the structure of a computer device shown in an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0048] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a system upgrade early warning method provided in an embodiment of this application. The system upgrade early warning method of this application embodiment can be applied to computer devices, including but not limited to smartphones, laptops, tablets, desktop computers, physical servers, and cloud servers. Figure 1 As shown, the system upgrade early warning method of this embodiment includes steps S101 to S103, which are described in detail below:

[0049] In step S101, first product configuration information of a customized development product of a system to be upgraded is acquired, and second product configuration information of a latest standard product is acquired.

[0050] In this step, the system to be upgraded is a software system containing a customized development product, such as an ERP system customized by an enterprise, wherein the customized development product is a product obtained by customizing a standard product, which inherits the standard configuration information of the standard product. The upgrading process of the system to be upgraded is to upgrade the standard configuration information of the customized development product to the latest version corresponding to the latest standard product.

[0051] Optionally, the first product configuration information is configuration information describing business functions of the customized development product, which includes but is not limited to plug-in code information, script information, business object information and product library file information. The second product configuration information is configuration information describing business functions of the latest standard product, which also includes but is not limited to code information, business object information and product library file information, and specifically includes but is not limited to the latest published business object, the inherited business object, the latest table structure, the view structure, the stored procedure, the component list, the enumeration data and the auxiliary materials, etc.

[0052] Optionally, for the second product configuration information: as shown in the cache process diagram of the second product configuration information in FIG. 8, the Product microservice is built based on the K8s+docker cloud native architecture, the latest standard product publishes all business objects (including the latest published business and all the inherited basic business objects) through the WebAPI customized product function plug-in, the dynamic domain model is used to merge and serialize the multiple business objects into XML and extract them to the cloud service; at the same time, the latest table structure, view structure, stored procedure, component list, enumeration data and auxiliary materials are extracted to the Product service, and these second product configuration information of the latest standard product is cached to the Redis database for calling by the computer device for upgrading early warning detection. Figure 2

[0053] In step S102, based on a preset comparison and detection strategy, the first product configuration information and the second product configuration information are compared to determine whether there is a configuration abnormal item in the customized development product compared with the latest standard product.

[0054] ​In this step, the preset comparison detection strategy is a preset comparison detection step, which includes but is not limited to a business object detection strategy, a plug-in code detection strategy, a script detection strategy, and a configuration file detection strategy. The business object detection strategy is a detection step for a business object newly added to the standard product based on the customized development product. The plug-in code detection strategy is a detection step for plug-in code of the customized development product. The script detection strategy is a detection step for a script of the customized development product, which can be a SQL script detection strategy. The configuration file detection strategy is a detection step for product library file information of the customized development product.

[0055] It can be understood that the business object is a carrier object of all businesses and information, can clearly express the business description relationship between different roles in the system to be upgraded, and can clearly record the association relationship between businesses. Different business objects can implement corresponding business functions and facilitate flexible expansion of businesses.

[0056] Optionally, the preset comparison detection strategy can be executed in parallel in the computer device to comprehensively detect the upgrade risk of the system to be upgraded. The configuration abnormal item includes but is not limited to KEY conflict, field conflict, layout conflict, view conflict, and the like.

[0057] In step S103, if the customized development product has a configuration abnormal item compared with the latest standard product, a warning prompt information is sent.

[0058] In this step, the warning prompt information is used to prompt the user that the system to be upgraded has an upgrade risk and suggest correcting the configuration abnormal item.

[0059] It should be noted that the first product configuration information of the customized development product of the system to be upgraded is acquired, the second product configuration information of the latest standard product is acquired, and the first product configuration information and the second product configuration information are compared based on the preset comparison detection strategy to determine whether the customized development product has a configuration abnormal item compared with the latest standard product, so as to detect whether there is a configuration conflict between the customized development product and the latest standard product, and further detect the system upgrade risk. If the customized development product has a configuration abnormal item compared with the latest standard product, a warning prompt information is sent to inform the user to correct the configuration, so as to effectively avoid the system upgrade risk and ensure the success of the system upgrade.

[0060] In some embodiments, for the business object, the step S102 includes:

[0061] If the preset comparison detection strategy is the business object detection strategy, for the first layer business object extension layer information, comparing the business control parameters between the first layer business object extension layer information and the standard product business object information to determine whether there is a configuration exception item in the business object extension layer information compared with the standard product business object information;

[0062] For the Nth layer business object extension layer information, merging the first N-1 layer business object extension layer information and the standard product business object information to obtain the merged layer information, and comparing the business control parameters between the merged layer information and the Nth layer business object extension layer information, wherein N>1.

[0063] In the embodiment, the first product configuration information includes multi-layer business object extension layer information, and the second product configuration information includes standard product business object information. As shown in a business object schematic diagram taking a bill as an example, “[KD] purchase order” is a standard product business object, and “purchase order” is an extension layer business object based on the standard product, which includes a stepped extension layer business object and a parallel extension layer business object. Figure 3 The “purchase order 1” and the “purchase order 2” in FIG. 4 are the stepped extension layer business objects, and the “purchase order 1” and the “purchase order 3” in FIG. 5 are the parallel extension layer business objects. Figure 3 Figure 3

[0064] ​​Exemplarily, the business object information of the "purchase order 1" is the first layer business object extension layer information, and the business object information of the "purchase order 2" and the business object information of the "purchase order 3" are the second layer business object extension layer information and the third layer business object extension layer information respectively. For the first layer business object extension layer information, the business control parameters between the business object information of the "purchase order 1" and the business object information of the "[KD] purchase order" are compared to determine whether there is a configuration conflict of the configuration information of the "purchase order 1" compared with the "[KD] purchase order". For the Nth layer (i.e. the second layer and above) business object extension layer information, for example, the second layer business object extension layer information, the business object information of the "purchase order 1" and the business object information of the "[KD] purchase order" are merged to obtain the merged layer information, and the business control parameters between the merged layer information and the business object information of the "purchase order 2" are compared to determine whether there is a configuration conflict of the configuration information of the "purchase order 2" compared with the "[KD] purchase order" and the "purchase order 1", so as to not only detect the configuration conflict between the custom development product and the standard product, but also detect the configuration conflict between the parallel extension layers, so as to realize comprehensive detection of the business object and further guarantee the safety of system upgrade.

[0065] Optionally, for the comparison process between the business object extension information and the standard product business object information, based on the domain model, the business object extension layer information in the XML format is deserialized into a metadata object, and meanwhile, the self-defined XML parsing method is used to obtain the modified content of the business object extension layer information, and then the metadata object obtained by deserializing the upper layer information in the XML format based on the domain model is compared. The comparison content includes but is not limited to the comparison detection of the business control identification, the attribute name and the field name of the custom development product, the comparison detection of the business control layout overlap of the custom development product, the comparison detection of the modified standard product business control attribute name, the comparison detection of the business object of the standard product used in the extension layer, the comparison detection of the business control identification, the attribute name and the field name in the parallel extension layer, and the comparison detection of the metadata enumeration value of the custom development product being covered.

[0066] The domain model is an extension of the model driven architecture (MDA) design idea, which is a three-layer architecture composed of a model-element-attribute, and divides the entire function module into a plurality of specific basic elements for research. For example, a typical page is composed of a menu, a text input box, a time input box, a list, display information and a plurality of controls, each kind of control can be regarded as a basic element, which is a meta model for domain model research. Among them, the difference of the element can be represented by the attribute of the element, and each element has a plurality of dynamically modifiable attributes, such as the type, length, height, bound database field and the like of the text box.

[0067] Optionally, the comparison and detection process for the first-layer business object extension layer information includes:

[0068] For the first-layer business object extension layer information, the business object extension layer information and the standard product business object information are deserialized to obtain the first metadata object;

[0069] Based on the first metadata object, determine the first business control information in the business object extension layer information and the second business control information in the standard product business object information;

[0070] The first business control information and the second business control information are parsed using XML to obtain the first business control parameters and the second business control parameters, respectively.

[0071] The parameters of the first business control and the parameters of the second business control are compared to determine whether there are any configuration anomalies in the extended information of the business object compared to the information of the standard product business object.

[0072] In this embodiment, with Figure 3 For example, the XML of "Purchase Order 1" is deserialized to obtain a metadata object. Based on this metadata object, the newly added business controls in "Purchase Order 1" can be identified. Using XML parsing methods (XML attribute nodes containing Action="edit"), the modified business controls in "Purchase Order 1" and their parameter values ​​can be determined. By traversing all business controls in "[KD] Purchase Order" (which has been deserialized into a metadata object) and examining the parameters of the business controls between "Purchase Order 1" and "[KD] Purchase Order," it can be determined whether there is a conflict between the newly added or modified business controls in "Purchase Order 1" and the business controls in "[KD] Purchase Order." For instance, if the business control names in "Purchase Order 1" and "[KD] Purchase Order" are the same, causing the system to be unable to accurately call extended layer business controls or standard product business controls, resulting in unusable business functions, then it is determined that there is a conflict between the newly added or modified business controls in "Purchase Order 1" and the business controls in "[KD] Purchase Order."

[0073] Optionally, the value of the extension layer before modification can be retrieved by the object identifier (oid), and the configuration conflict between the extension layer before and after modification can be compared to achieve detection between parallel extension layers.

[0074] Optionally, the comparison and detection process for the extension layer information of the Nth layer business object includes:

[0075] For the Nth layer business object extension layer information, the standard product business object information is deserialized to obtain the second metadata object;

[0076] If the N-1th layer business object extension layer information has a preset field, then the modified business control of the customized development product is found in the second metadata object, and the parameters of the business control are modified. If the N-1th layer business object extension layer information does not have a preset field, then the modified business control parameters of the customized development product are added to the control list in the second metadata object to obtain the merged layer information.

[0077] Compare the business control parameters between the merged layer information and the Nth layer business object extension layer information.

[0078] In this embodiment, as Figure 4 The diagram illustrates the detection process for the multi-layered business object extension layer. "Customized development results" refer to customized development products. Configuration information for the first product is retrieved from the customized development results, and configuration information for the second product is retrieved from the Redis cache. The extension layer is then compared layer by layer in the analysis client (computer device). For every N layers of extension layers, the comparison object is the combined information of the first N-1 layers and the standard product. For example... Figure 4 As shown, for the comparison test of extended level B, extended level A is merged with the standard document (standard product) to obtain the first merged layer, and then the first merged layer is compared with extended level B; for the comparison test of extended level C, extended level B is merged with the first merged layer to obtain the second merged layer, and then the second merged layer is compared with extended level C, and so on.

[0079] Specifically, the standard product XML is deserialized into a metadata object, which is then merged with the extension layer XML. If the extension layer XML contains Action="edit", the corresponding modified business control in the extension layer is queried in the standard product's metadata object, and its attribute value is modified. If the extension layer XML does not contain Action="edit", the business control is added to the control list in the standard product's metadata object. This process is repeated for other parallel extension layers. A comparison process identical to that used for the first-layer business object extension layer is then employed. Simultaneously, all business controls in the metadata object are traversed, and based on their attribute length and height, it is determined whether any controls are obscuring each other. This process is repeated sequentially, allowing for analysis of all extension layers through continuous merging and expansion. This enables the detection of configuration conflicts not only with the standard product but also between parallel extensions, ensuring comprehensive analysis of business objects.

[0080] In some embodiments, for plugin code, step S102 includes:

[0081] If the preset comparison detection strategy is a plug-in code detection strategy, based on the plug-in code detection strategy, a preset code detection tool is used to capture a target string in the first code information;

[0082] A regular matching method is used to determine whether there is a configuration abnormal item in the first product configuration information compared with the second product configuration information according to the target string.

[0083] In this embodiment, the first product configuration information further includes code information. For example, a stylecop custom detection tool is used to capture a target string in plug-in code, and the latest standard product table, view structure, stored procedure and function in the second product configuration information are obtained, and a regular matching method is used to determine whether there is a modification of the latest standard product table, view structure, stored procedure or function in the target string according to keywords such as Update, delete and Drop in the target string.

[0084] In some embodiments, for a script, the step S102 includes:

[0085] If the preset comparison detection strategy is a script detection strategy, based on the script detection strategy, a target keyword in the script information is read;

[0086] A regular matching method is used to determine whether there is a configuration abnormal item in the first product configuration information compared with the second product configuration information according to the target keyword.

[0087] In this embodiment, the first product configuration information further includes script information, which can be a SQL script. For example, each statement containing a target keyword such as Update, delete and Drop in the script is read, and the latest standard product table, view structure, stored procedure and function in the second product configuration information are obtained, and a regular matching method is used to determine whether there is a modification of the latest standard product table, view structure, stored procedure or function in the script according to the target keyword.

[0088] In some embodiments, for a product library file, the step S102 includes:

[0089] If the preset comparison detection strategy is a configuration file detection strategy, based on the configuration file detection strategy, it is determined whether the standard product library file exists in the first product configuration information, whether the file path of the standard product library file in the customized development product is the same as that in the latest standard product, and whether the deployment mode of the standard product library file in the customized development product is not the target deployment mode.

[0090] If both are true, then it is determined that the customized development product has configuration anomalies compared to the latest standard product.

[0091] In this embodiment, the second product configuration information also includes file information of the standard product library files. For example, the filename and storage location of the latest standard product library are obtained. If the custom-developed product contains this file, and the file's deployment path is the same as the latest standard product's storage path, and the file's deployment method is not Merge, then it is determined that the custom-developed product has a file overwriting risk.

[0092] To implement the system upgrade early warning method corresponding to the above method embodiments, and to achieve the corresponding functions and technical effects. See also Figure 5 , Figure 5 This diagram illustrates a structural block diagram of a system upgrade early warning device according to an embodiment of this application. For ease of explanation, only the parts relevant to this embodiment are shown. The system upgrade early warning device provided in this embodiment includes:

[0093] The acquisition module 501 is used to acquire the first product configuration information of the customized development product of the system to be upgraded, and the second product configuration information of the latest standard product.

[0094] The comparison module 502 is used to compare the configuration information of the first product with the configuration information of the second product based on a preset comparison detection strategy, so as to determine whether the customized development product has any configuration anomalies compared with the latest standard product;

[0095] The issuing module 503 is used to issue a warning message if the customized development product has configuration anomalies compared to the latest standard product.

[0096] In some embodiments, the preset comparison detection strategy includes at least one of the following preset comparison detection strategies: business object detection strategy, plugin code detection strategy, script detection strategy, and configuration file detection strategy.

[0097] In some embodiments, the first product configuration information includes multi-layer business object extension layer information, the second product configuration information includes standard product business object information, and the comparison module 502 includes:

[0098] The first comparison unit is used to compare the business control parameters between the first-layer business object extension information and the standard product business object information if the preset comparison detection strategy is the business object detection strategy, so as to determine whether there are any configuration anomalies in the business object extension information compared with the standard product business object information.

[0099] The second comparison unit is configured to, for the Nth layer of the service object extension layer information, merge the first N-1 layers of the service object extension layer information and the standard product service object information to obtain merged layer information, and compare service control parameters between the merged layer information and the Nth layer of the service object extension layer information, where N>1.

[0100] In some embodiments, the first comparison unit is specifically configured to:

[0101] For the first layer of the service object extension layer information, the service object extension layer information and the standard product service object information are deserialized to obtain a first metadata object;

[0102] Based on the first metadata object, first service control information in the service object extension layer information and second service control information in the standard product service object information are determined;

[0103] The first service control information and the second service control information are parsed by using XML to obtain first service control parameters and second service control parameters, respectively;

[0104] The first service control parameters and the second service control parameters are compared to determine whether there is a configuration exception item in the service object extension information compared with the standard product service object information.

[0105] In some embodiments, the second comparison unit is specifically configured to:

[0106] For the Nth layer of the service object extension layer information, the standard product service object information is deserialized to obtain a second metadata object;

[0107] If the N-1th layer of the service object extension layer information has a preset field, the service control that has been modified by the customized development product is queried in the second metadata object, and the parameter of the service control is modified. If the N-1th layer of the service object extension layer information does not have a preset field, the service control parameter that has been modified by the customized development product is added to a control list in the second metadata object to obtain merged layer information.

[0108] The service control parameters between the merged layer information and the Nth layer of the service object extension layer information are compared.

[0109] In some embodiments, the first product configuration information further includes code information, and the comparison module 502 includes:

[0110] The grabbing unit is configured to, if the preset comparison detection strategy is a plug-in code detection strategy, based on the plug-in code detection strategy, use a preset code detection tool to grab a target string in the first code information.

[0111] The determining unit is configured to determine, by using a regular matching manner, whether the first product configuration information has configuration abnormal items compared with the second product configuration information according to the target string.

[0112] In some embodiments, the first product configuration information further comprises script information, and the comparison module 502 comprises:

[0113] The reading unit is configured to read a target keyword in the script information based on the script detection strategy if the preset comparison detection strategy is the script detection strategy.

[0114] The determining unit is configured to determine, by using a regular matching manner, whether the first product configuration information has configuration abnormal items compared with the second product configuration information according to the target keyword.

[0115] In some embodiments, the second product configuration information further comprises file information of a standard product library file, and the comparison module 502 comprises:

[0116] The judging unit is configured to determine, based on the configuration file detection strategy, whether the standard product library file exists in the first product configuration information, whether the file path of the standard product library file in the customized development product and the file path of the standard product library file in the latest standard product are the same, and whether the deployment manner of the standard product library file in the customized development product is the target deployment manner if the preset comparison detection strategy is the configuration file detection strategy.

[0117] The determining unit is configured to determine that the customized development product has configuration abnormal items compared with the latest standard product if all the conditions are met.

[0118] The system upgrade early warning device described above can implement the system upgrade early warning method of the method embodiments described above. The optional items in the method embodiments described above are also applicable to this embodiment, and will not be described in detail herein. The remaining content of this embodiment can be referred to the content of the method embodiments described above, and will not be described in detail herein.

[0119] Figure 6 A structural schematic diagram of a computer device according to an embodiment of the present application is shown in FIG. 6. As shown in FIG. 6, the computer device 6 of this embodiment comprises at least one processor 60 (only one processor is shown in the figure), a memory 61, and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, wherein the processor 60 implements the steps in any method embodiment described above when executing the computer program 62. Figure 6 Figure 6

[0120] ​​The computer device 6 can be a smart phone, a tablet computer, a desktop computer, a cloud server, and the like. The computer device can include, but is not limited to, a processor 60, a memory 61. Those skilled in the art can understand that Figure 6 The computer device 6 is only an example and does not constitute a limitation on the computer device 6, and can include more or fewer components than shown, or combine certain components, or different components, for example, can also include an input / output device, a network access device, and the like.

[0121] The processor 60 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, and the like. The general-purpose processor can be a microprocessor or can also be any conventional processor.

[0122] The memory 61 can be an internal storage unit of the computer device 6 in some embodiments, for example, a hard disk or a memory of the computer device 6. The memory 61 can also be an external storage device of the computer device 6 in other embodiments, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, and the like. Further, the memory 61 can include both the internal storage unit and the external storage device of the computer device 6. The memory 61 is used to store an operating system, an application program, a boot loader, data, and other programs, for example, program codes of the computer program, and the like. The memory 61 can also be used to temporarily store data that has been output or will be output.

[0123] In addition, the embodiment of the present application further provides a computer readable storage medium, the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps in any method embodiment described above.

[0124] The embodiment of the present application provides a computer program product, when the computer program product is run on a computer device, so that the computer device executes the steps in each method embodiment described above.

[0125] In several embodiments provided in the present application, it can be understood that each block in the flowchart or block diagram can represent a module, a segment or a portion of code which includes one or more executable instructions for implementing the specified logic function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figure. For example, two blocks noted in succession can in fact be executed substantially concurrently or in the reverse order, depending on the functionality involved.

[0126] If the functions are realized in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes several instructions for causing a computer device to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media capable of storing program codes.

[0127] The specific embodiments described above further illustrate the purposes, technical solutions and beneficial effects of the present application. It should be understood that the above description is only for specific embodiments of the present application and is not intended to limit the protection scope of the present application. It is particularly pointed out that any modification, equivalent replacement, improvement, etc. made by those skilled in the art within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A system upgrade early warning method, characterized in that, include: Obtain the first product configuration information of the customized development product of the system to be upgraded, and obtain the second product configuration information of the latest standard product; Based on a preset comparison and detection strategy, the configuration information of the first product is compared with the configuration information of the second product to determine whether the customized development product has any configuration anomalies compared with the latest standard product; If the customized product has configuration anomalies compared to the latest standard product, a warning message will be issued. The first product configuration information includes multi-layer business object extension layer information, and the second product configuration information includes standard product business object information. The comparison of the first product configuration information and the second product configuration information based on a preset comparison and detection strategy includes: If the preset comparison detection strategy is a business object detection strategy, then for the first layer business object extension layer information, the business control parameters between the first layer business object extension information and the standard product business object information are compared to determine whether the business object extension information has any configuration anomalies compared to the standard product business object information; For the Nth layer business object extension layer information, the business object extension layer information of the first N-1 layers is merged with the standard product business object information to obtain merged layer information, and the business control parameters between the merged layer information and the Nth layer business object extension layer information are compared, where N>1; For the Nth layer business object extension layer information, the preceding N-1 layers of business object extension layer information are merged with the standard product business object information to obtain merged layer information. The business control parameters between the merged layer information and the Nth layer business object extension layer information are then compared, including: For the Nth layer business object extension layer information, the standard product business object information is deserialized to obtain the second metadata object; The judgment is performed sequentially from the first layer to the (N-1)th layer. If the current layer business object extension layer information has a preset field, the modified business control of the customized development product is found in the second metadata object, and the parameters of the business control are modified. If the current layer business object extension layer information does not have a preset field, the modified business control parameters of the customized development product are added to the control list in the second metadata object. This process continues until the current layer is the (N-1)th layer, at which point the merged layer information is obtained. Compare the business control parameters between the merged layer information and the Nth layer business object extension layer information.

2. The system upgrade early warning method as described in claim 1, characterized in that, The preset comparison detection strategy includes at least one of the following: business object detection strategy, plugin code detection strategy, script detection strategy, and configuration file detection strategy.

3. The system upgrade early warning method as described in claim 2, characterized in that, The comparison of business control parameters between the first-layer business object extension information and the standard product business object information includes: For the first-layer business object extension layer information, the business object extension layer information and the standard product business object information are deserialized to obtain the first metadata object; Based on the first metadata object, determine the first business control information in the business object extension layer information and the second business control information in the standard product business object information; The first business control information and the second business control information are parsed using XML to obtain the first business control parameters and the second business control parameters, respectively. The parameters of the first business control and the parameters of the second business control are compared to determine whether there are any configuration anomalies in the extended information of the business object compared to the information of the standard product business object.

4. The system upgrade early warning method as described in claim 2, characterized in that, The first product configuration information also includes code information. The comparison of the first product configuration information with the second product configuration information based on a preset comparison detection strategy includes: If the preset comparison detection strategy is a plugin code detection strategy, the target string in the first code information is captured based on the plugin code detection strategy and using a preset code detection tool. Using regular expression matching, based on the target string, it is determined whether there are any configuration anomalies in the first product configuration information compared to the second product configuration information.

5. The system upgrade early warning method as described in claim 2, characterized in that, The first product configuration information also includes script information. The comparison of the first product configuration information with the second product configuration information based on a preset comparison detection strategy includes: If the preset comparison detection strategy is a script detection strategy, the target keyword in the script information is read based on the script detection strategy; Using regular expression matching, based on the target keyword, it is determined whether there are any configuration anomalies in the first product configuration information compared to the second product configuration information.

6. The system upgrade early warning method as described in claim 2, characterized in that, The second product configuration information also includes file information from the standard product library. The comparison of the first product configuration information with the second product configuration information based on a preset comparison detection strategy includes: If the preset comparison detection strategy is a configuration file detection strategy, based on the configuration file detection strategy, it is determined whether the standard product library file exists in the first product configuration information, whether the file path of the standard product library file in the customized development product is the same as the file path in the latest standard product, and whether the deployment method of the standard product library file in the customized development product is not the target deployment method. If both are true, then it is determined that the customized development product has configuration anomalies compared to the latest standard product.

7. A system upgrade early warning device, characterized in that, include: The acquisition module is used to acquire the first product configuration information of the customized development product of the system to be upgraded, and the second product configuration information of the latest standard product. The comparison module is used to compare the configuration information of the first product with the configuration information of the second product based on a preset comparison detection strategy, so as to determine whether the customized development product has any configuration anomalies compared with the latest standard product; The issuing module is used to issue a warning message if the customized development product has configuration anomalies compared to the latest standard product; The comparison module includes: The first comparison unit is used to compare the business control parameters between the first-layer business object extension information and the standard product business object information if the preset comparison detection strategy is a business object detection strategy, so as to determine whether there are any configuration anomalies in the business object extension information compared with the standard product business object information. The second comparison unit is used to merge the business object extension layer information of the first N-1 layers with the standard product business object information for the Nth layer business object extension layer information to obtain merged layer information, and compare the business control parameters between the merged layer information and the Nth layer business object extension layer information, where N>1; The second comparison unit is specifically used to: for the Nth layer business object extension layer information, deserialize the standard product business object information to obtain the second metadata object; If the N-1th layer business object extension layer information has a preset field, then the modified business control of the customized development product is found in the second metadata object, and the parameters of the business control are modified. If the N-1th layer business object extension layer information does not have a preset field, then the modified business control parameters of the customized development product are added to the control list in the second metadata object to obtain the merged layer information. Compare the business control parameters between the merged layer information and the Nth layer business object extension layer information.

8. A computer device, characterized in that, It includes a processor and a memory, the memory being used to store a computer program, which, when executed by the processor, implements the system upgrade early warning method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the system upgrade early warning method as described in any one of claims 1 to 6.

Images