CN107766068B - Application system patch installation method and device, computer equipment and storage medium - Google Patents
Application system patch installation method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN107766068B CN107766068B CN201710935600.0A CN201710935600A CN107766068B CN 107766068 B CN107766068 B CN 107766068B CN 201710935600 A CN201710935600 A CN 201710935600A CN 107766068 B CN107766068 B CN 107766068B
- Authority
- CN
- China
- Prior art keywords
- patch
- registry
- missing
- file
- patch file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The invention relates to an application system patch installation method, an application system patch installation device, computer equipment and a storage medium. The method comprises the following steps: after the first terminal successfully installs the patch file, sending patch information containing the patch file to the middle layer server, wherein the patch information is used for indicating the middle layer server to install the patch file; writing a patch identifier corresponding to the patch file into a first registry of the shared database; when the second terminal logs in the application system, acquiring a first registry, and detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the patch identifications which are missing in the second registry from the first registry; sending a request for acquiring a patch file corresponding to the missing patch identification to a middle layer server; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file. Thereby improving patch installation efficiency.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for installing an application system patch, a computer device, and a storage medium.
Background
Programs of the application system are written by people, and imperfect places or bugs inevitably occur during writing, or bugs also occur during the use process of the application system, and the bugs are generally called bugs. Patches are small programs made by application system developers and specifically used to repair these bugs. When detecting that the bug occurs in the application system, downloading and installing the corresponding patch file released by the developer, thereby achieving the purposes of preventing the intrusion of the same type of virus and enhancing the software function.
In general, when a plurality of terminals are equipped with the same application system, it is necessary to detect whether the application system in each terminal has a bug. When a bug exists, the patch file needs to be downloaded and installed for each terminal, so that bug repair work of the application system in multiple terminals is completed. Obviously this patch installation method is very time consuming.
Disclosure of Invention
In view of the foregoing, there is a need to provide an application system patch installation method, apparatus, computer device and storage medium that reduce the time consumption for application system patch installation.
An application system patch installation method comprises the following steps: after the first terminal successfully installs the patch file, sending patch information containing the patch file to a middle layer server, wherein the patch information is used for indicating the middle layer server to install the patch file; writing the patch identification corresponding to the patch file into a first registry of a shared database; when a second terminal logs in an application system, acquiring the first registry, and detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the patch identifications missing from the second registry from the first registry; sending a request for acquiring a patch file corresponding to the missing patch identification to the middle layer server; and receiving the patch file corresponding to the lost patch identification returned by the middle layer server and installing the patch file.
An application system patch installation method comprises the following steps: when a second terminal logs in an application system, detecting whether a second registry in the second terminal has missing patch files or not; when the missing patch file exists, determining a patch identifier of the missing patch file; sending a request for acquiring a missing patch file of a missing patch file to a middle layer server, wherein the request comprises a patch identifier of the missing patch file; and receiving the patch file corresponding to the lost patch identification returned by the middle layer server and installing the patch file.
In one embodiment, the detecting whether the second registry in the second terminal has a missing patch file or not includes: acquiring a first registry in a shared database; detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch files are inconsistent, judging that the missing patch files in the second registry are missing patch files, and when the patch files are consistent, judging that the missing patch files in the second registry are not missing patch files; the determining the patch identifier of the missing patch file includes: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
In one embodiment, the first registry includes a patch identifier sent by the first terminal.
In one embodiment, the detecting whether there is a missing patch file in a second registry in the second terminal includes: acquiring first updating time of a first registry in a shared database; acquiring second updating time of a second registry in a second terminal; and judging whether the second registry in the second terminal has the missing patch file or not according to the first updating time and the second updating time.
An application system patch installation method comprises the following steps: the method comprises the steps that when a second terminal logs in an application system, a second registry in the second terminal is obtained; sending a message containing the second registry to a middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification according to the patch identification in the second registry; receiving verification result information sent by the middle layer server; and when the verification result information contains the missing patch file and the missing patch file, installing the missing patch file and the missing patch file.
An application system patch installation apparatus, the apparatus comprising: the patch file missing detection module is used for detecting whether missing patch files are missing patch files in a second registry in the second terminal when the application system is logged in; when the missing patch file exists, determining a patch identifier of the missing patch file; the first patch file installation module is used for sending a request for acquiring missing patch files of the missing patch files to the middle layer server, wherein the request comprises patch identifications of the missing patch files; and receiving the patch file corresponding to the lost patch identification returned by the middle layer server and installing the patch file.
In one embodiment, the patch file loss detection module is further configured to obtain a first registry in a shared database; detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch files are inconsistent, judging that the missing patch files in the second registry are missing patch files, and when the patch files are consistent, judging that the missing patch files in the second registry are not missing patch files; the determining the patch identification of the missing patch file comprises: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
An application system patch installation apparatus, the apparatus comprising: the patch file missing checking module is used for acquiring a second registry in the second terminal when logging in the application system; sending a message containing the second registry to a middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification according to the patch identification in the second registry; receiving verification result information sent by the middle layer server; and the second patch file installation module is used for installing the missing patch file when the verification result information contains the missing patch file.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the above application system patch installation methods when executing the computer program.
A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of any of the above-mentioned application system patch installation methods.
According to the application system patch installation method, the application system patch installation device, the computer equipment and the storage medium, after the first terminal successfully installs the patch file, the patch file can be sent to the middle layer server, the middle layer server is instructed to install the patch file, and meanwhile the patch identification corresponding to the patch file is written into the shared database. When the second terminal logs in the application system, all the patch identifications in the shared database can be obtained, whether the second terminal has missing patch files or not can be automatically detected according to all the patch identifications in the shared database, if yes, the missing patch files are obtained from the middle layer server and are installed, and therefore patch installation efficiency of the application system can be improved.
Drawings
FIG. 1 is a diagram of an application environment for a method for applying a system patch installation according to an embodiment;
FIG. 2 is a flow diagram of a method for application system patch installation, according to one embodiment;
FIG. 3 is a flowchart of a method for application system patch installation in another embodiment;
FIG. 4 is a flow diagram of a method for application system patch installation in yet another embodiment;
FIG. 5 is a block diagram of an application system patch installation apparatus in one embodiment;
FIG. 6 is a block diagram showing the construction of a patch installation apparatus for an application system according to another embodiment;
fig. 7 is a schematic diagram of the internal structure of the terminal in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It will be understood that, as used herein, the terms "first," "second," and the like may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, a first terminal may be termed a second terminal, and, similarly, a second terminal may be termed a first terminal, without departing from the scope of the present invention. The first terminal and the second terminal are both terminals, but they are not the same terminal.
Fig. 1 is a schematic diagram of an application environment of an application system patch installation method in one embodiment. As shown in fig. 1, the application environment includes a first terminal 110, a middle tier server 120, a shared database 130, a second terminal 140 (e.g., the second terminal 140-1, the second terminal 140-2, the second terminal 140-3 in fig. 1), and a patch server 150. The first terminal 110, the middle Server 120, the shared database 130, and the second terminal 140 are in a C/S (Client/Server) environment. The C/S architecture comprises a three-layer system structure of a terminal layer, a middle layer and a database, wherein the terminal layer is provided with a plurality of terminal devices, the middle layer is provided with a middle layer server 120, and the database is provided with a shared database 130. The first terminal 110 is an administrator terminal of the terminal layer, and the second terminal 140 (e.g., the second terminal 140-1, the second terminal 140-2, and the second terminal 140-3 in fig. 1) is a common terminal in the terminal layer. Any one or more terminal devices may be provided in the terminal layer as the first terminal 110. The middle tier server 120 and the terminal tier and the database may be communicatively connected, that is, the middle tier server 120 and the first terminal 110, the second terminal 140 and the shared database 140 are communicatively connected. The shared database 140 may be used to enable data sharing between the first terminal 110 and the second terminal 140. The patch server 150 may be used to provide the terminal in the terminal layer with the patch file of the corresponding system. When the first terminal 110 receives the patch file sent by the patch server 150, the patch file is installed; after the first terminal 110 is successfully installed, the patch file is sent to the middle tier server 120, and meanwhile, a patch identifier corresponding to the patch file is written into the shared database 130; after the middle layer server 120 obtains the patch file, the patch file is installed; when the second terminal 140 lacks the patch identifier in the shared database 130, the middle tier server 120 may send the patch file corresponding to the lacking patch identifier to the second terminal 140, and the second terminal 140 acquires the patch file corresponding to the lacking patch identifier and then installs the patch file. Thereby enabling application system patch installation in the second terminal 140.
In an embodiment, as shown in fig. 2, a method for installing an application system patch is provided, and this embodiment mainly takes the application environment shown in fig. 1 as an example to illustrate the method. The method comprises the following steps:
step S202, after the first terminal successfully installs the patch file, the first terminal sends patch information containing the patch file to the middle layer server, and the patch information is used for indicating the middle layer server to install the patch file; and writing the patch identification corresponding to the patch file into a first registry of the shared database.
In this embodiment, the patch information may include a patch file, a patch identifier corresponding to the patch file, an installation instruction of the patch file, and the like, where the installation instruction of the patch file is used to instruct the middle-layer server to install the patch file. The middle layer server is arranged in the middle layer of the C/S architecture three-layer system structure and is used for communicating with a terminal layer and a database of the C/S architecture three-layer system structure and can realize communication connection with a first terminal and a second terminal in the terminal layer, namely the middle layer server can receive the patch file sent by the first terminal and send the patch file to the second terminal after the patch file is installed. The communication with the shared database can be realized, that is, the first terminal and the second terminal in the terminal layer can realize the communication with the shared database through the middle layer server. The patch identification may be a string uniquely corresponding to the patch file or a patch address uniquely associated with the patch file such that each patch file may be uniquely identified according to the string or the patch address.
The shared database is a database in a three-layer system structure of the C/S architecture and can communicate with the middle-layer server to realize the sharing of the patch identification between the first terminal and the second terminal. That is, the first terminal may write the patch identifier into the shared database through the middle tier server, and may send the patch identifier to the second terminal through the middle tier server. The first registry is a registry containing patch identifications of all patch files in the first terminal, and the first registry is stored in the shared database. The first terminal may send the patch identifier corresponding to the installed patch file to the shared database through the middle tier server, and write the patch identifier into a first registry of the shared database.
In one embodiment, the installation instruction of the patch file is used for instructing the middle layer server to detect whether the patch identifier corresponding to the patch file exists, and if so, instructing the middle layer server to delete the patch identifier and install the patch file; and if not, indicating the middle layer server to directly install the patch file. And after obtaining the patch file, the intermediate layer server judges whether a patch identifier corresponding to the patch file exists in a local file, if so, deletes the patch identifier corresponding to the patch file and installs the patch file, and if not, directly installs the patch file.
Step S204, when the second terminal logs in the application system, acquiring a first registry, and detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the patch identifications which are missing in the second registry from the first registry; sending a request for acquiring a patch file corresponding to the missing patch identification to a middle layer server; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
In this embodiment, the number of the second terminals may be one or more, and the application system is any application system or application software in the second terminal, such as an ERP system. When the second terminal detects a login request of the application system, all patch identifications in the first registry of the shared database can be acquired. The second registry is a registry containing patch identifications corresponding to all patch files in the second terminal, and the second registry is stored in the second terminal.
The second terminal can trigger the instruction for acquiring the first registry when detecting the operation on the preset application system login control. The application system login control may be an application system login virtual button displayed on a screen interface of the second terminal, or an entity control arranged on the second terminal, where the entity control includes, but is not limited to, a keyboard, a touch pad, a mouse, or the like connected to the second terminal. For example, when the click operation on the login virtual button of the application system is detected, the instruction for acquiring the first registry is triggered, or when the mouse corresponding cursor is detected on the shortcut icon of the application system displayed on the screen interface of the second terminal and the left button of the mouse is continuously clicked twice, the instruction for acquiring the first registry can be triggered.
In one embodiment, when logging in an application system, a second terminal acquires a first registry in a shared database, where the first registry stores a patch identifier corresponding to a patch file. Comparing all patch identifications in a first registry in the shared database with patch identifications in a second registry in the second terminal one by one, if the first registry has patch identifications which are not in the second registry, judging that the second registry in the second terminal has missing patch files, and if the second registry has all patch identifications in the first registry, judging that the second registry in the second terminal does not have missing patch files.
In one embodiment, the first terminal, the middle tier server, and the second terminal may each install the patch file by means of silent installation. The silent installation means that installation is directly carried out according to default settings without any user intervention.
Taking the second terminal as an example, after the second terminal obtains the patch file, the second terminal can automatically decompress the patch file, start silent installation of the patch, and automatically jump out of the login interface of the application system after installation is completed. Therefore, the installation of the second terminal patch can be automatically judged and installed only after the application program is started, and each client machine does not need to be manually and respectively installed, so that the convenience of patch installation is improved.
In this embodiment, because the patch installation operation of the application system is triggered by the second terminal when logging in the application system, the second terminal may automatically detect whether the application system has a missing patch file, and then obtain the missing patch file from the middle-tier server and install the missing patch file. When the same application system in the second terminals needs to install the patch, the user does not need to log in the middle layer server and each second terminal, and then the patch installation of the second terminals can be completed. The patch installation is convenient for users, the workload of installing the patch by the users is greatly reduced, and the patch installation efficiency is improved.
Taking the environment of the C/S architecture as an example, in the prior art, patch installation needs to be performed on each middle-tier server and each terminal device respectively. When there are hundreds of terminal devices and a plurality of intermediate servers, installing a patch requires copying the patch to each terminal device and each intermediate server, and manually installing the patch for each intermediate server and terminal device, which requires a large amount of work. Moreover, the account password of each terminal device and the intermediate server must be known, and if the account password is not available, the patch cannot be installed. Meanwhile, the security of the middle-layer server is reduced due to the fact that the account number and the password can be leaked. When a user installs a patch in each terminal device and the middle-layer server, the user needs to wait for time consumption when manually clicking the patch program. Compared with the prior art, according to the application system patch installation method provided by the application system patch installation method, a user does not need to log in each terminal device and the middle-layer server, the patch installation is convenient for the user, and the workload of installing the patch by the user is greatly reduced; the user can complete the installation of the patch without the login account password of the terminal equipment and the middle-layer server, so that the safety of patch installation is improved; meanwhile, in the process of installing the system patch, the patch program does not need to be clicked manually, unattended installation can be achieved, and time consumed by patch installation is reduced.
In an embodiment, as shown in fig. 3, another application system patch installation method is provided, and this embodiment mainly takes the application of this method to the second terminal 140 shown in fig. 1 as an example for description. The method comprises the following steps:
step S302, when the second terminal logs in the application system, whether a second registry in the second terminal has a missing patch file is detected.
In an embodiment, when logging in the application system, the second terminal may automatically trigger a preset patch file missing detection instruction, and detect whether the second terminal itself has a missing patch file according to the missing detection instruction. The second terminal can obtain the first registry in the shared database and compare the first registry with the second registry of the second terminal to determine whether the missing patch file exists.
In one embodiment, the second terminal may determine whether the second terminal has a missing patch file according to whether the patch identifications contained in the two registries are consistent. Whether the patch file is missing can also be judged according to whether the updating time of the two registries is consistent. When the patch files in the two registries are not consistent, the patch files are judged to be missing, or the updating time of the first registry is longer than that of the second registry, the patch files can also be judged to be missing.
Step S304, when the missing patch file exists, determining the patch identification of the missing patch file.
In an embodiment, when it is detected that a second registry in the second terminal lacks a patch file, the second terminal may obtain a patch identifier different from a patch identifier included in the second registry in the first registry, and determine that the different patch identifier is the patch identifier of the missing patch file.
Step S306, sending a request for obtaining the missing patch file to the middle tier server, where the request includes a patch identifier of the missing patch file.
In an embodiment, after determining that the missing patch file exists, the second terminal may trigger a request for obtaining the missing patch file, carry a patch identifier of the missing patch file in the request, and send the request to the middle-layer server. The request may instruct the intermediate tier server to uniquely determine the missing patch file based on the patch identifier and send the missing patch file to the second terminal.
In one embodiment, after acquiring a request for missing a patch file, the middle tier server extracts a patch identifier included in the request, and searches a patch file corresponding to the patch identifier in a local file of the middle tier server.
And step S308, receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
In one embodiment, the second terminal may receive a response message returned by the intermediate-layer server for the request, where the message includes, but is not limited to, a missing patch identifier, a patch file corresponding to the missing patch identifier, and the like. The second terminal may parse the information, and install the patch file when the patch file corresponding to the missing patch identifier is parsed.
According to the application system patch installation method, when the second terminal logs in the application system, the second registry in the second terminal is detected to determine whether the second registry has the missing patch file, and when the second registry has the missing patch file, the missing patch file is obtained from the middle-layer server and is installed, so that patch installation of the application system is achieved. The patch installation operation of the application system is triggered by the second terminal when the second terminal logs in the application system, the second terminal can automatically detect whether the application system has a missing patch file or not, then the patch file is obtained from the middle-layer server and installed, when the same application system in the multiple terminals needs to install the patch, the patch installation time can be reduced, and not every terminal obtains the patch from a website containing the needed patch file and installs the patch manually, so that the patch installation efficiency is improved.
In one embodiment, step S302 includes: acquiring a first registry in a shared database; detecting whether a patch identifier in a second registry in a second terminal is consistent with a patch identifier in a first registry; and when the patch files are consistent, judging that the missing patch files exist in the second registry, and when the patch files are consistent, judging that the missing patch files do not exist in the second registry.
In one embodiment, the first registry is a registry set in the shared database, and the first registry includes the patch identifier sent by the first terminal. After the first terminal successfully installs the patch file, writing a patch identifier corresponding to the patch file into a first registry of the shared database. Optionally, the shared database may detect a patch file installed in the first terminal in real time, obtain a patch identifier corresponding to the patch file, write the patch identifier into the first registry, and keep the patch identifier in the first registry and the patch identifier of the patch installed in the first terminal in synchronization, so that the second terminal performs comparison of the patch identifiers.
In one embodiment, a first registry in a shared database is obtained, whether a patch identifier in a second registry in a second terminal is missing compared with a patch identifier in the first registry is detected, if so, a missing patch file is determined to exist in the second registry, and if not, a missing patch file is determined not to exist in the second registry.
In one embodiment, a first registry in a shared database is obtained, the first registry containing patch identifications for patch files. Scanning all patch identifications in the first registry one by one, searching patch identifications identical to the patch identifications in the first registry in a second registry in the second terminal, if the patch identifications identical to all the patch identifications in the first registry are not searched in the second registry, judging that missing patch identifications exist in the second registry, namely missing patch files exist in the second terminal, and if the patch identifications identical to all the patch identifications in the first registry are searched in the second registry, judging that the missing patch identifications do not exist in the second registry, namely missing patch files do not exist in the second terminal. The missing patch file is identified as the missing patch file by the missing patch identification.
In the embodiment, whether the patch identification in the second registry in the second terminal is lost or not can be judged according to the detection result by detecting whether the patch identification in the second registry in the second terminal is consistent with the patch identification in the first registry in the shared database, so that the convenience of patch installation of the application system is improved.
In one embodiment, step S304 includes: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
In one embodiment, a patch identifier that does not exist in the second registry is extracted from the first registry, the non-existing patch identifier is a missing patch identifier, and the missing patch identifier can uniquely identify a missing patch file.
In the embodiment, the patch identifier missing in the second registry is acquired from the first registry, so that the convenience of the patch installation of the application system is improved.
In another embodiment, step 302 includes: acquiring first updating time of a first registry in a shared database; acquiring second updating time of a second registry in a second terminal; and judging whether the second registry in the second terminal has the missing patch file or not according to the first updating time and the second updating time.
In this embodiment, the first update time is a time when the first registry is updated last time, and the second update time is a time when the second registry is updated last time.
In one embodiment, a file containing the first registry update time information and the second registry update time information is called, and the last update time of the first registry and the last update time of the second registry are extracted from the file. And comparing the updating time of the first registry and the updating time of the second registry, if the last updating time of the first registry is greater than the last updating time of the second registry, judging that the second registry in the second terminal has the missing patch file, and if the last updating time of the first registry is less than the last updating time of the second registry, judging that the second registry in the second terminal does not have the missing patch file.
In the embodiment, the first updating time of the first registry in the shared database is compared with the second updating time of the second registry in the second terminal, and the comparison result is used as the judgment basis for judging whether the missing patch file exists in the second registry of the second terminal, so that the judgment operation of the missing patch file is simplified, and the patch installation efficiency of the application system is improved.
In an embodiment, as shown in fig. 4, another application system patch installation method is provided, and this embodiment also mainly takes the application of this method to the second terminal 140 shown in fig. 1 as an example for description. The method comprises the following steps:
step S402, when the second terminal logs in the application system, a second registry in the second terminal is obtained.
Step S404, sending a message containing the second registry to the middle layer server, wherein the message is used for instructing the middle layer server to perform patch file missing verification according to the patch identification in the second registry.
In this embodiment, the second terminal sends a message including the second registry to the middle tier server, where the message is used to instruct the middle tier server to check whether the patch identifier in the second registry is missing according to the patch identifier in the first registry of the shared database.
Step S406, receiving the verification result information sent by the middle tier server.
In this embodiment, the verification result information is result information of whether the second terminal lacks the patch file. When there is a missing patch file, the verification result information may further include all the detected missing patch files.
And step S408, when the verification result information contains the missing patch file, installing the missing patch file.
In one embodiment, the second terminal analyzes the verification result information after receiving the verification result information sent by the middle layer server, and when the verification result information is determined to have the missing patch file, all the missing patch files contained in the verification result information can be acquired, and the missing patch file can be automatically installed.
According to the application system patch installation method, the acquired second registry in the second terminal is sent to the middle layer server, so that the middle layer server performs patch file missing verification, receives the missing patch files in the verification result information of the middle layer server, and installs the missing patch files. The missing verification is carried out on the middle layer server, and the missing patch file is obtained from the middle layer server, so that the patch installation operation of the application system is simplified, and the patch installation efficiency of the application system is improved.
In one embodiment, as shown in FIG. 5, an application system patch installation apparatus is provided. The apparatus includes a patch file loss detection module 502 and a patch file first installation module 504.
The patch file missing detection module 502 is configured to detect whether a missing patch file exists in a second registry in the second terminal when logging in the application system; when the missing patch file exists, determining a patch identifier of the missing patch file; the patch file first installation module 504 is configured to send a request for obtaining a missing patch file of a missing patch file to the middle tier server, where the request includes a patch identifier of the missing patch file; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
According to the application system patch installation device, the application system patch installation operation is triggered by the second terminal when the second terminal logs in the application system, the second terminal can automatically detect whether the application system has missing patch files according to the first detection table in the shared database, and if yes, the missing patch files are obtained from the middle-layer server and installed. When the same application system in the second terminals needs to install the patch, the user does not need to log in the middle layer server and each second terminal, and then the patch installation of the second terminals can be completed. Therefore, the patch installation device of the application system can improve the patch installation efficiency.
In one embodiment, the patch file loss detection module 502 is further configured to obtain a first registry in the shared database; detecting whether a patch identifier in a second registry in a second terminal is consistent with a patch identifier in a first registry; when the patch files are inconsistent, judging that the missing patch files in the second registry are missing patch files, and when the patch files are consistent, judging that the missing patch files in the second registry are not missing patch files; determining the patch identification of the missing patch file comprises: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
In one embodiment, the patch file loss detection module 502 is further configured to obtain a first update time of a first registry in the shared database; acquiring second updating time of a second registry in a second terminal; and judging whether a second registry in the second terminal has a missing patch file or not according to the first updating time and the second updating time.
In one embodiment, as shown in FIG. 6, another application system patch installation apparatus is provided. The apparatus includes a patch file missing check module 602 and a patch file second installation module 604.
The patch file missing checking module 602 is configured to obtain a second registry in the second terminal when logging in the application system; sending a message containing a second registry to the middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification according to the patch identification in the second registry; receiving verification result information sent by the middle layer server; the patch file second installation module 604 is configured to install the missing patch file when the verification result information includes the missing patch file.
According to the application system patch installation device, the application system patch installation operation is triggered by the second terminal when the second terminal logs in the application system, the second terminal can automatically detect whether the application system has missing patch files, and then the missing patch files are obtained from the middle-layer server and installed. When the same application system in the second terminals needs to install the patch, the user does not need to log in the middle layer server and each second terminal, and then the patch installation of the second terminals can be completed. Therefore, the patch installation device of the application system can improve the patch installation efficiency.
The various modules in the above-described apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules. The processor can be a Central Processing Unit (CPU), a microprocessor, a singlechip and the like.
In one embodiment, a computer device is provided, the computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: after the first terminal successfully installs the patch file, sending patch information containing the patch file to the middle layer server, wherein the patch information is used for indicating the middle layer server to install the patch file; writing a patch identifier corresponding to the patch file into a first registry of the shared database; when a second terminal logs in an application system, acquiring a first registry, and detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the patch identifications missing from the second registry from the first registry; sending a request for acquiring a patch file corresponding to the missing patch identification to a middle layer server; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file. The processor can be a Central Processing Unit (CPU), a microprocessor, a singlechip and the like.
In one embodiment, when the processor executes the computer program, the following steps are further implemented: when the second terminal logs in the application system, detecting whether a second registry in the second terminal has a missing patch file; when the missing patch file exists, determining a patch identifier of the missing patch file; sending a request for acquiring a missing patch file to a middle layer server, wherein the request comprises a patch identifier of the missing patch file; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
In one embodiment, when the processor executes the computer program to detect whether the second registry in the second terminal has the missing patch file, the following steps are further implemented: acquiring a first registry in a shared database; detecting whether a patch identifier in a second registry in a second terminal is consistent with a patch identifier in a first registry; when the two registries are inconsistent, determining that the second registry has missing patch files, and when the two registries are consistent, determining that the second registry does not have missing patch files; determining the patch identification of the missing patch file comprises: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
In one embodiment, when the processor executes the computer program to detect whether a missing patch file exists in a second registry in the second terminal, the following steps are further implemented: acquiring first updating time of a first registry in a shared database; acquiring second updating time of a second registry in a second terminal; and judging whether the second registry in the second terminal has the missing patch file or not according to the first updating time and the second updating time.
In one embodiment, when the processor executes the computer program, the following steps are further implemented: the method comprises the steps that when a second terminal logs in an application system, a second registry in the second terminal is obtained; sending a message containing a second registry to the middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification according to the patch identification in the second registry; receiving verification result information sent by the middle layer server; and when the verification result information contains the missing patch file, installing the missing patch file.
In one embodiment, as shown in fig. 7, there is also provided a terminal including a processor, a memory, a display screen, a network interface, and an input device connected through a system bus. Wherein, the processor is used for providing calculation and control capability and supporting the operation of the whole terminal. The memory is used for storing data, programs, and/or instruction codes, etc., and at least one computer program is stored on the memory, and the computer program can be executed by the processor to realize the application system patch installation method suitable for the terminal provided in the embodiment of the application. The Memory may include a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random-Access-Memory (RAM). For example, in one embodiment, the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a database, and a computer program. The database stores data related to the application system patch installation method provided by each embodiment. The computer program can be executed by a processor for implementing the application system patch installation method provided by the embodiments. The internal memory provides a cached operating environment for the operating system, databases, and computer programs in the non-volatile storage medium. The display screen is used for displaying information input by a user or information provided for the user, and the display screen can be a liquid crystal display screen or an electronic ink display screen. The network interface is used for performing network communication with the server or other terminals, receiving or transmitting data, for example, sending a request for obtaining a patch file to the server or other terminals, receiving the patch file sent by the server or other terminals, and the like. The input device may be a touch layer covered on the display screen, or may be a key, a track ball or a touch pad arranged on the terminal housing, or may be an external keyboard, a touch pad or a mouse, etc. Those skilled in the art will appreciate that the configuration shown in fig. 7 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation on the terminal to which the present application is applied, and that a particular terminal may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer-readable storage medium is provided, having stored thereon a computer program which, when executed by a processor, performs the steps of: after the first terminal successfully installs the patch file, sending patch information containing the patch file to the middle layer server, wherein the patch information is used for indicating the middle layer server to install the patch file; writing a patch identifier corresponding to the patch file into a first registry of the shared database; when the second terminal logs in the application system, acquiring a first registry, and detecting whether a patch identifier in a second registry in the second terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the patch identifications which are missing in the second registry from the first registry; sending a request for acquiring a patch file corresponding to the missing patch identification to a middle layer server; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the second terminal logs in the application system, detecting whether a second registry in the second terminal has a missing patch file; when the missing patch file exists, determining a patch identifier of the missing patch file; sending a request for acquiring a missing patch file to a middle layer server, wherein the request comprises a patch identifier of the missing patch file; and receiving the patch file corresponding to the missing patch identification returned by the middle layer server and installing the patch file.
In one embodiment, the computer program is executed by a processor to implement the following steps when detecting whether a missing patch file exists in a second registry in a second terminal: acquiring a first registry in a shared database; detecting whether a patch identifier in a second registry in a second terminal is consistent with a patch identifier in a first registry; when the two registries are inconsistent, determining that the second registry has missing patch files, and when the two registries are consistent, determining that the second registry does not have missing patch files; determining the patch identification of the missing patch file comprises: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
In one embodiment, the computer program is executed by a processor to implement the following steps when detecting whether a missing patch file exists in a second registry in a second terminal: acquiring first updating time of a first registry in a shared database; acquiring second updating time of a second registry in a second terminal; and judging whether the second registry in the second terminal has the missing patch file or not according to the first updating time and the second updating time.
In one embodiment, the computer program when executed by the processor further performs the steps of: the method comprises the steps that when a second terminal logs in an application system, a second registry in the second terminal is obtained; sending a message containing a second registry to the middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification according to the patch identification in the second registry; receiving verification result information sent by the middle layer server; and when the verification result information contains the missing patch file, installing the missing patch file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (11)
1. An application system patch installation method comprises the following steps:
after a first administrator terminal in the C/S framework receives a patch file sent by a patch server, installing the patch file in a silent installation mode; after the first administrator terminal successfully installs the patch file, sending patch information containing the patch file to an intermediate layer server, wherein the patch information contains the patch file, a patch identifier corresponding to the patch file and an installation instruction of the patch file, and the installation instruction in the patch information is used for instructing the intermediate layer server in a C/S framework to detect whether the patch identifier corresponding to the patch file exists in a local file or not, if so, instructing the intermediate layer server to delete the patch identifier and install the patch file, and if not, instructing the intermediate layer server to install the patch file in a silent installation mode; writing the patch identification corresponding to the patch file into a first registry of a shared database in a C/S architecture; the silent installation means that the patch file is installed directly according to default settings without user intervention when the patch file is installed; the shared database is used for communicating with the middle layer server so as to realize the sharing of the patch identification between the first administrator terminal and the second common terminal; the patch file is an applet which is made by an application system developer and is specially used for repairing the bug;
when a second common terminal in a C/S framework logs in an application system, automatically triggering and acquiring a first registry in the shared database, and detecting whether a patch identifier in a second registry in the second common terminal is consistent with a patch identifier in the first registry; when the patch identifications are inconsistent, acquiring the missing patch identifications in the second registry from the first registry, wherein the second registry is a registry containing the patch identifications corresponding to all patch files in the second common terminal, and the second registry is stored in the second common terminal; sending a request for acquiring a patch file corresponding to the missing patch identification to the middle layer server; receiving a patch file corresponding to the missing patch identification returned by the middle layer server, and installing the patch file in a silent installation mode; the C/S architecture comprises more than one second common terminal.
2. An application system patch installation method comprises the following steps:
when a second common terminal in a C/S framework logs in an application system, automatically triggering and acquiring a first registry in a shared database, and detecting whether a second registry in the second common terminal has a missing patch file or not according to a patch identifier in the first registry; the patch identification in the first registry is obtained by writing the patch identification corresponding to the patch file into a first registry of a shared database after the first administrator terminal successfully installs the patch file, the second registry is a registry containing the patch identifications corresponding to all patch files in the second common terminal, and the second registry is stored in the second common terminal; the shared database is used for communicating with a middle layer server to realize the sharing of the patch identifier between the first administrator terminal and the second common terminal, and the C/S architecture comprises more than one second common terminal; when the missing patch file exists, determining a patch identifier of the missing patch file; the patch file is an applet which is made by an application system developer and is specially used for repairing the bug;
sending a request for acquiring a missing patch file to a middle layer server, wherein the request comprises a patch identifier of the missing patch file;
receiving a patch file corresponding to the missing patch identification returned by the middle layer server, and installing the patch file in a silent installation mode; and the silent installation means that the patch file is directly installed according to default settings without user intervention when being installed.
3. The method according to claim 2, wherein the automatically triggering detection of whether a second registry in the second generic terminal has a missing patch file comprises:
automatically triggering and acquiring a first registry in a shared database;
detecting whether a patch identifier in a second registry in the second common terminal is consistent with a patch identifier in the first registry;
when the patch files are inconsistent, judging that the second registry has missing patch files, and when the patch files are consistent, judging that the second registry does not have missing patch files;
the determining the patch identifier of the missing patch file includes: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
4. The method of claim 2, wherein the first registry comprises patch identifications transmitted by the first administrator terminal.
5. The method according to claim 2, wherein the automatically triggering detection of whether the patch file is missing in a second registry in the second generic terminal comprises:
automatically triggering and acquiring first updating time of a first registry in a shared database;
acquiring second updating time of a second registry in a second common terminal;
and judging whether a second registry in the second common terminal has a missing patch file or not according to the first updating time and the second updating time.
6. An application system patch installation method comprises the following steps:
when a second common terminal in the C/S framework logs in the application system, automatically triggering to acquire a second registry in the second common terminal;
sending a message containing the second registry to a middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification based on a patch identifier in a first registry in a shared database and according to the patch identifier in the second registry; the patch identification in the first registry is obtained by writing the patch identification corresponding to the patch file into a first registry of a shared database after the first administrator terminal successfully installs the patch file, the second registry is a registry containing the patch identifications corresponding to all patch files in the second common terminal, and the second registry is stored in the second common terminal; the shared database is used for communicating with the middle layer server so as to realize the sharing of the patch identification between the first administrator terminal and the second common terminal; the C/S architecture comprises more than one second common terminal; the patch file is an applet which is made by an application system developer and is specially used for repairing the bug;
receiving verification result information sent by the middle layer server;
when the verification result information contains missing patch files, installing the missing patch files in a silent installation mode; and the silent installation means that the patch file is directly installed according to default settings without user intervention when being installed.
7. An application system patch installation apparatus, the apparatus comprising:
the patch file loss detection module is used for automatically triggering and acquiring a first registry in a shared database when a second common terminal in the C/S architecture logs in an application system, and detecting whether a second registry in the second common terminal has a missing patch file or not according to a patch identifier in the first registry; when the missing patch file exists, determining a patch identifier of the missing patch file; the patch identification in the first registry is obtained by writing the patch identification corresponding to the patch file into a first registry of a shared database after the first administrator terminal successfully installs the patch file, the second registry is a registry containing the patch identifications corresponding to all patch files in the second common terminal, and the second registry is stored in the second common terminal; the shared database is used for communicating with a middle layer server so as to realize the sharing of the patch identification between the first administrator terminal and the second common terminal; the C/S architecture comprises more than one second common terminal;
the patch file first installation module is used for sending a request for acquiring a missing patch file to the middle layer server, wherein the request comprises a patch identifier of the missing patch file; receiving a patch file corresponding to the missing patch identification returned by the middle layer server, and installing the patch file in a silent installation mode; the silent installation means that the patch file is installed directly according to default settings without user intervention when the patch file is installed; the patch file is an applet created by an application system developer and specifically used to repair the bug.
8. The apparatus of claim 7, wherein the patch file loss detection module is further configured to automatically trigger acquisition of a first registry in a shared database; detecting whether a patch identifier in a second registry in the second common terminal is consistent with a patch identifier in the first registry; when the patch files are inconsistent, judging that the second registry has missing patch files, and when the patch files are consistent, judging that the second registry does not have missing patch files; the determining the patch identification of the missing patch file comprises: and acquiring the missing patch identification in the second registry from the first registry, wherein the missing patch identification is the patch identification of the missing patch file.
9. An application system patch installation apparatus, the apparatus comprising:
the patch file missing checking module is used for automatically triggering and acquiring a second registry in a second common terminal in the C/S architecture when the second common terminal logs in the application system; sending a message containing the second registry to a middle layer server, wherein the message is used for indicating the middle layer server to perform patch file missing verification based on a patch identifier in a first registry in a shared database and according to the patch identifier in the second registry; the patch identification in the first registry is obtained by writing the patch identification corresponding to the patch file into a first registry of a shared database after the first administrator terminal successfully installs the patch file, the second registry is a registry containing the patch identifications corresponding to all patch files in the second common terminal, and the second registry is stored in the second common terminal; the shared database is used for communicating with the middle layer server so as to realize the sharing of the patch identification between the first administrator terminal and the second common terminal; receiving verification result information sent by the middle layer server; the C/S architecture comprises more than one second common terminal; the patch file is an applet which is made by an application system developer and is specially used for repairing the bug;
the second patch file installation module is used for installing the missing patch files in a silent installation mode when the verification result information contains the missing patch files; and the silent installation means that the patch file is directly installed according to default settings without user intervention when being installed.
10. A computer arrangement comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the application system patch installation method as claimed in any one of claims 2 to 6 are implemented by the processor when executing the computer program.
11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the application system patch installation method of any one of claims 2 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710935600.0A CN107766068B (en) | 2017-10-10 | 2017-10-10 | Application system patch installation method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710935600.0A CN107766068B (en) | 2017-10-10 | 2017-10-10 | Application system patch installation method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107766068A CN107766068A (en) | 2018-03-06 |
| CN107766068B true CN107766068B (en) | 2020-12-29 |
Family
ID=61266469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710935600.0A Active CN107766068B (en) | 2017-10-10 | 2017-10-10 | Application system patch installation method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107766068B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108536460A (en) * | 2018-04-17 | 2018-09-14 | 南京高盛信息科技有限公司 | A kind of software automatic updating system of lightweight |
| CN113050977B (en) * | 2019-12-27 | 2022-06-17 | 武汉斗鱼网络科技有限公司 | Data processing method and system |
| CN112465466A (en) * | 2020-12-10 | 2021-03-09 | 金蝶软件（中国）有限公司 | Flow task execution method and device, computer equipment and storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9720674B1 (en) * | 2008-05-05 | 2017-08-01 | Open Invention Network, Llc | Automating application of software patches to a server having a virtualization layer |
| CN101621398A (en) * | 2008-06-30 | 2010-01-06 | 中兴通讯股份有限公司 | Client/server system and method for automatic multi-client synchronous configuration thereof |
| CN102176695A (en) * | 2011-01-14 | 2011-09-07 | 北京格致璞科技有限公司 | Method and device for software environment among synchronous equipment |
| CN102262552B (en) * | 2011-07-06 | 2015-08-19 | 惠州Tcl移动通信有限公司 | A kind of application program striding equipment synchronous method and system |
| US9244673B2 (en) * | 2012-06-08 | 2016-01-26 | Apple Inc. | System and method for updating application archive files |
| US9141635B2 (en) * | 2012-09-28 | 2015-09-22 | Oracle International Corporation | Transparently upgrading derived database objects |
| CN104281365A (en) * | 2014-09-24 | 2015-01-14 | 深圳市金立通信设备有限公司 | Terminal |
| CN104639652A (en) * | 2015-03-04 | 2015-05-20 | 太仓市同维电子有限公司 | Method and system for automatically updating programs |
| CN107193600A (en) * | 2017-05-24 | 2017-09-22 | 深信服科技股份有限公司 | A kind of patch management method, the first equipment, the first plug-in unit, system and fire wall |
-
2017
- 2017-10-10 CN CN201710935600.0A patent/CN107766068B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107766068A (en) | 2018-03-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109831420B (en) | Method and device for determining kernel process permission | |
| JP6100898B2 (en) | Method and device for processing messages | |
| US10194321B2 (en) | Periodic mobile forensics | |
| CN106940651B (en) | POS terminal software upgrading method and device | |
| CN103390130B (en) | Based on the method for the rogue program killing of cloud security, device and server | |
| US9811356B2 (en) | Automated software configuration management | |
| US10452469B2 (en) | Server performance correction using remote server actions | |
| US11762979B2 (en) | Management of login information affected by a data breach | |
| CN102254113A (en) | Method and system for detecting and intercepting malicious code of mobile terminal | |
| US8745610B2 (en) | Maintenance system, maintenance method and program for maintenance | |
| JP2017511923A (en) | Virus processing method, apparatus, system, device, and computer storage medium | |
| CN105631312B (en) | The processing method and system of rogue program | |
| CN107766068B (en) | Application system patch installation method and device, computer equipment and storage medium | |
| US10216601B2 (en) | Agent dynamic service | |
| CN109818972B (en) | Information security management method and device for industrial control system and electronic equipment | |
| US10025646B2 (en) | Naming of nodes in NET framework | |
| CN106802821B (en) | Method and device for identifying installation source of application program | |
| CN110928787B (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| CN112148545A (en) | Security baseline detection method and security baseline detection system of embedded system | |
| CN111666567A (en) | Detection method, device, computer program and medium for malicious modification of application program | |
| JP5150546B2 (en) | Information processing apparatus, operation history acquisition method, computer program | |
| CN109933990B (en) | Multi-mode matching-based security vulnerability discovery method and device and electronic equipment | |
| CN109714371B (en) | Industrial control network safety detection system | |
| CN113656291A (en) | Dynamic calling method for software script engine | |
| CN114070632A (en) | Automatic penetration testing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |