Intelligent patch push method and system applied to complex erp system

Abstract

The invention discloses an intelligent patch pushing method and system applied to a complex ERP system. The intelligent patch pushing system applied to the complex ERP system comprises a project information module, a project management module, a pushing module, an execution module and a patch management module, wherein the project information module is used for managing all the product service modules and versions installed for each implemented project; the project management module is used for setting concerned projects and selecting service modules associated with the projects; the pushing module is used for formulating a corresponding pushing scheme according to information in the project information module and the project management module; the execution module is used for installing corresponding patches according to a scheme pushed by the pushing module, and feeding the patch installation information back to a cloud server, and the cloud server filters projects installed with patches according to the fedback information; the patch management module is positioned on the cloud server, and used for performing sort management on version information of patches, patch information corresponding to projects, official patch information and patch information opened for users. According to the invention, the advantages of efficient and convenient management and product patch maintenance are achieved.

Description

technical field [0001] The invention relates to the field of data processing, in particular to an intelligent patch pushing method and system applied to complex ERP systems. Background technique [0002] At present, the maintenance and support system of ERP products operates in a problem-driven manner, that is, the problem can only be dealt with passively after the customer discovers a product error. Customers often go to the patch management system to query and search for patches after they have problems, resulting in a lag in problem handling. Moreover, some high-risk and important patches that have been discovered cannot be pushed and applied to customer projects in a timely manner, causing problems to repeatedly occur in different customer products, posing a great risk. [0003] For the general version problem of the product, the maintenance process has to go through links such as customers, branch consultants, headquarters support personnel, and headquarters R&D person...

AI Technical Summary

Problems solved by technology

Customers often go to the patch management system to query and search for patches after they have problems, resulting in a lag in problem handling

Moreover, some high-risk and important patches that have been discovered cannot be pushed and applied to customer projects in time, causing problems to occur repeatedly in different customer products, posing a great risk

[0003] For the general version problem of the product, the maintenance process has to go through links such as customers, branch consultants, headquarters support personnel, and headquarters R&D personnel. The maintenance support process is too long, and developers cannot accurately know whether there is a patch for each problem. , bringing a lot of repetitive work; if the general version patch is not applied to the project in time, it will also cause serious data error problems, which need to be repeatedly invested in resources to deal with

[0004] Patches downloaded by customers have high quality requirements, and the existing patch management methods often fail to verify the patches or only upload problematic customers to the patch management system for all users to download, so the quality of the patches cannot be guaranteed, and Bring hidden dangers to the stable operation of the system

[0005] Due to the multi-module characteristics of NC products, the version consistency cannot be guaranteed for each service module product

In the existing patch management system, the download of different patches often needs to be cumbersomely queried and downloaded according to the version, and it is not easy to manage

Customers with relatively strict management require that all known patch files be installed during the product implementation process. However, due to the relatively loose patch management of the existing patch management system, the frontline can only download patches based on their own experience. Lack of standardized process

[0006] For front-line personnel, even if the patch is installed, it is impossible to confirm whether the patch has been inserted correctly

Often due to differences in the technical level of front-line personnel, the patch is not entered correctly and the patch cannot take effect

Images