A software system upgrade method in unix environment

Abstract

The invention provides a UNIX environment software system upgrading method. The method comprises the steps that 1, a directory structure is built for upgrade packages in advance; 2, the upgrade packages are installed and deployed; 3, rule mapping tables are built according to the configuration variances between application servers, and the rule mapping tables are stored into all the application servers in advance; 4, the upgrade packages which are installed successfully are applied to other application servers by synthesizing the rule mapping tables; 5, self-adaptive upgrade package installation and deploying are completed for all the application servers. According to the UNIX environment software system upgrading method, formal environment patches are automatically generated, the patch content is not manually changed, and patch accuracy and consistency are ensured.

Description

technical field [0001] The invention belongs to the technical field of computers, in particular to a UNIX environment software system upgrading method. Background technique [0002] Many important software systems (such as large-scale PDM systems) in enterprises are usually deployed in UNIX systems with stable performance or in Unix-like operating system environments such as Linux. Such as figure 1 As shown, the system administrator’s personal operation terminal is generally separated from the application system server by a firewall, and the administrator connects the personal operation terminal to the server area management intermediate machine (usually Windows operating system) through the corresponding port or software, and then communicates with the application system The system server establishes a connection for management operations. [0003] The application system upgrade activities are restricted by the upgrade environment. After the application system administrat...

AI Technical Summary

Problems solved by technology

[0010] ① The patch provided by the developer is correct, but if there is an error in the upgrade steps in the patch deployment instructions, the upgrade may fail;

[0011] ②Application system administrators directly log in to the application server for operation, there is a possibility of misoperation other than normal upgrade commands, and unpredictable problems may be introduced due to an upgrade;

[0012] ③ There are differences in the form of patch packages provided by different patch package providers, and there are also differences in the way application managers maintain upgrade packages, which will lead to irregularities in the upgrade process;

[0013] ④When an upgrade involves hundreds of files that need to be updated or added, the process is quite cumbersome and error-prone;

[0015] ⑥If you need to roll back after the upgrade, especially if you need to roll back to the state before several upgrades, it will be a disaster for the implementer

This has the following potential defects: First, if the upgrade package provided by the developer is correct, but if there is an error in the upgrade step in the patch deployment instructions, the upgrade may fail; The possibility of misoperations other than normal upgrade commands may cause unpredictable problems due to an upgrade; third, if an upgrade involves hundreds of files that need to be updated or added, the process is quite cumbersome, time-consuming and error-prone

However, this method only supports rollback after the current upgrade fails, and does not support the need to roll back due to other needs after the current upgrade is successful, or to roll back all previous upgrade operations.

Images