CN111158749B - Software version replacement method, device, equipment and readable storage medium - Google Patents
Software version replacement method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN111158749B CN111158749B CN201911342537.5A CN201911342537A CN111158749B CN 111158749 B CN111158749 B CN 111158749B CN 201911342537 A CN201911342537 A CN 201911342537A CN 111158749 B CN111158749 B CN 111158749B
- Authority
- CN
- China
- Prior art keywords
- software
- information
- target
- version
- software information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 77
- 238000012986 modification Methods 0.000 claims description 28
- 230000004048 modification Effects 0.000 claims description 28
- 230000008569 process Effects 0.000 claims description 19
- 238000004806 packaging method and process Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 11
- 238000011160 research Methods 0.000 abstract description 4
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000011161 development Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a software version replacing method, which comprises the following steps: acquiring a login request sent by a user, and determining target software information according to the login request; wherein the target software information is stored locally; judging whether the target software information is the same as the current software information; if the target software information is different from the current software information, replacing the current software information in the current version software by using the target software information to generate the target version software; according to the method, corresponding target software information is determined according to a login request, and when the target software information is different from the current software information, the current software information is replaced by the target software information, so that the replacement of the software version is completed; therefore, only one piece of software is developed, and the replacement of the software version can be realized by replacing the software information, so that the workload of research personnel and test personnel is reduced; in addition, the invention also provides a software version replacing device, equipment and a computer readable storage medium, which also have the beneficial effects.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a software version replacing method, a software version replacing device, a software version replacing apparatus, and a computer readable storage medium.
Background
Factory commission manufacturing (Original Equipment Manufacturer, OEM) refers to the manufacturer producing corresponding products for customers according to their needs and authorizations, i.e. according to customer specific conditions. Such a cooperative manner of entrusting production by others is abbreviated as OEM, and a manufacturer who accepts a processing job is called an OEM manufacturer.
With the development of computer technology, more and more clients have special requirements on software when buying the software. For example, the software is required to use information such as the name, logo, and the like of the client company in the interface displayed after login. The existing software customization method is used for developing a customized version of branches by pulling the branches from the software code of an initialized version, and binding the customized version of software with a client so as to enable the client to use the software of the corresponding version and meet the requirements of the client. However, when many clients with special requirements are required, the development of multiple specialized versions is required, so that the workload of research personnel and testers is greatly increased, and the development process of the specialized version software consumes a great deal of manpower and time.
Therefore, how to solve the problem that the development process of the customized version software consumes a lot of manpower and time by the existing software customization method is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
In view of the above, the present invention is directed to a software version replacing method, a software version replacing device, a software version replacing apparatus and a computer readable storage medium, which solve the problem that the development process of the customized version software consumes a lot of manpower and time due to the existing software customization method.
In order to solve the technical problems, the invention provides a software version replacing method, which comprises the following steps:
acquiring a login request sent by a user, and determining target software information according to the login request; wherein the target software information is stored locally;
judging whether the target software information is the same as the current software information;
and if the target software information is different from the current software information, replacing the current software information in the current version software by using the target software information to generate the target version software.
Optionally, the determining the target software information according to the login request includes:
acquiring identity information in the login request;
and determining a target information number corresponding to the identity information by using a software information corresponding table, and determining the software information corresponding to the target information number as the target software information.
Optionally, the method further comprises:
acquiring a modification request sent by the user, and determining first software information designated by the modification request;
and modifying the target information number corresponding to the identity information in the software information corresponding table into a first information number corresponding to the first software information.
Optionally, before the obtaining the login request sent by the user, the method further includes:
performing an access port number setting operation;
correspondingly, the obtaining the login request sent by the user includes:
acquiring a first request through a port, and judging whether a port number corresponding to the first request is a first port number or not;
if the port number corresponding to the first request is a first port number, determining the first request as the login request;
correspondingly, the obtaining the modification request sent by the user includes:
acquiring a second request through the port, and judging whether the port number corresponding to the second request is a second port number or not;
and if the port number corresponding to the second request is the second port number, determining the second request as the modification request.
Optionally, the method further comprises:
acquiring and analyzing an uploading request to obtain uploading data; the uploading data comprises logo picture data, HTML file data, jsp file data and information data;
packaging the uploading data according to preset packaging rules to obtain uploading software information;
and storing the uploading software information.
Optionally, after the generating the target version software, the method further includes:
and running the target version software, and acquiring and executing the operation instruction sent by the user.
Optionally, the replacing the current software information in the current version software with the target software information generates the target version software, including:
acquiring the current version software from a TOMCAT server, and initializing the current version software to obtain initialization software;
and writing the target software information into a target position of the initialization software to obtain the target version software, and storing the target version software into the TOMCAT server.
The invention also provides a software version replacing device, which comprises:
the determining module is used for acquiring a login request sent by a user and determining target software information according to the login request; wherein the target software information is stored locally;
the judging module is used for judging whether the target software information is the same as the current software information;
and the generating module is used for replacing the current software information in the current version software by using the target software information if the target software information is different from the current software information, so as to generate the target version software.
The invention also provides a software version replacement device, which comprises a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the software version replacement method described above.
The invention also provides a computer readable storage medium for storing a computer program, wherein the computer program realizes the software version replacing method when being executed by a processor.
According to the software version replacing method provided by the invention, a login request sent by a user is obtained, and target software information is determined according to the login request; wherein the target software information is stored locally. And judging whether the target software information is the same as the current software information. If the target software information is different from the current software information, the current software information in the current version software is replaced by the target software information, and the target version software is generated.
Therefore, the method determines the corresponding target software information according to the login request, and can judge whether the current version of software is matched with the user by judging whether the target software information is the same as the current software information. If the target software information is the same as the current software information, the fact that the current version software corresponding to the current software information is not matched with the user is indicated, the software version needs to be replaced, the target version software can be generated by replacing the current software information with the target software information, and the replacement of the software version is completed. Therefore, a plurality of specialized version software is not required to be developed, only one software is required to be developed, the replacement of the software version can be realized by replacing software information, the workload of research personnel and testers is reduced, the manpower and time loss in the development process of the specialized version software is reduced, and the problem that the development process of the specialized version software consumes a great deal of manpower and time by the existing software customization method is solved.
In addition, the invention also provides a software version replacing device, software version replacing equipment and a computer readable storage medium, and the device and the method have the same beneficial effects.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a software version replacement method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a software information acquiring method according to an embodiment of the present invention;
FIG. 3 is a flowchart of a method for generating a target version software according to an embodiment of the present invention;
FIG. 4 is a flowchart of a method for determining and modifying target software information according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a software version replacing device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a software version replacing device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, fig. 1 is a flowchart of a software version replacing method according to an embodiment of the present invention.
The method comprises the following steps:
s101: acquiring a login request sent by a user, and determining target software information according to the login request; wherein the target software information is stored locally.
It should be noted that, each step of the software judgment replacement method provided by the invention can be executed by an OEM platform, and the OEM platform can be built by a server, for example, can be built by an NGINX server and a TOMCAT server, and can be used for storing software information and providing services for users.
The login request is sent by the user and is used for logging in the software of the corresponding version of the login request, and the specific form of the login request is not limited in this embodiment. The user may send various instructions or requests, including login requests, to the OEM platform through the terminal used by the user. And determining target software information corresponding to the target user according to the login request, wherein the target software information is stored locally on the OEM platform and is used for generating target version software, namely the version software corresponding to the user. The target software information may include a plurality of items of data, and may include logo picture data, user names, HTML files, jsp files, "about" information, and the like, for example. The number and the variety of the data items contained in different software information can be the same or different, and the data items can be set according to actual conditions and requirements of users. For example, the software information a includes a user name, logo picture data, and "about" information, and the software information B includes a user name, an HTML file, and a jsp file.
Specifically, the login information may include identity information of the user, and corresponding target software information is determined according to the identity information of the user; or the login information can comprise the number information of the target software information, and the corresponding target software information is determined according to the number information. After determining the target software information, the process proceeds to step S102.
S102: and judging whether the target software information is the same as the current software information.
After the target software information is determined, whether the target software information is the same as the current software information or not is judged, and the current software information is information in the current version software. After the target software information is determined, whether the number of the target software information is the same as that of the current software information or not can be compared, and if the number is the same, the target software information is determined to be the same as the current software information; if the numbers are different, determining that the target software information is different from the current software information. Or the first information in the target software information and the first information in the current software information can be compared to be the same, and the first information is fixed as a certain item of information in the software information, for example, logo picture data or a user name. If the two pieces of first information are the same, indicating that the target software information is the same as the current software information; if the two first information are different, the target software information is different from the current software information. When it is determined that the target software information is different from the current software information, step S103 may be entered; when it is determined that the target software information is the same as the current software information, step S104 may be performed, that is, a preset operation is performed, and the specific content of the preset operation is not limited in this embodiment, for example, an operation instruction sent by the user may be acquired and executed, or no operation may be performed, that is, no operation may be performed.
S103: and replacing the current software information in the current version software by the target software information to generate the target version software.
When the target software information is determined to be different from the current software information, the current software information in the current version software is replaced by the target software information, so that the target version software is generated, and the replacement of the software version is realized. The embodiment does not limit the specific process of replacing the current software information by the target software information, and the specific replacing process can also be different according to the difference of the number and the content of the data items in the target software information and the current software information, for example, whether the client names in the target software information and the current software information are the same or not can be judged, if so, the replacement is illustrated to be the replacement of different updated versions of the same user, so that only partial information such as 'related' information can be modified; if the software information is different, the replacement is replaced by the replacement among the software information corresponding to different users, all the current software information is deleted, and then the target software information is written in, so that the target version software is generated. By replacing software information in the software, the software can be switched in different versions, and the software-customized service can be provided for different users according to the requirements of the users.
Further, after the target version software is generated, other operations may be performed, for example, the target version software may be run, and meanwhile, an operation instruction sent by the user may be obtained and executed, so as to complete the normal service sent by the user.
By applying the software version replacing method provided by the embodiment of the invention, the corresponding target software information is determined according to the login request, and whether the current version of software is matched with the user can be judged by judging whether the target software information is identical with the current software information. If the target software information is the same as the current software information, the fact that the current version software corresponding to the current software information is not matched with the user is indicated, the software version needs to be replaced, the target version software can be generated by replacing the current software information with the target software information, and the replacement of the software version is completed. Therefore, a plurality of specialized version software is not required to be developed, only one software is required to be developed, the replacement of the software version can be realized by replacing software information, the workload of research personnel and testers is reduced, the manpower and time loss in the development process of the specialized version software is reduced, and the problem that the development process of the specialized version software consumes a great deal of manpower and time by the existing software customization method is solved.
Based on the above embodiment of the invention, before determining the target software information, one or more types of software information need to be stored on the OEM platform so as to generate different versions of software. Referring to fig. 2, fig. 2 is a flowchart of a software information obtaining method according to an embodiment of the present invention, including:
s201: acquiring and analyzing an uploading request to obtain uploading data; the uploading data comprises logo picture data, HTML file data, jsp file data and information data.
Specifically, the upload request is used to upload software information, i.e., newly-added software information on the OEM platform. There are multiple storage units in the OEM platform, each storing one piece of software information. After the uploading request is acquired, the uploading request is analyzed to obtain uploading data, and the uploading data can comprise multiple items of data. In the embodiment of the invention, the uploading data comprises logo picture data, HTML file data, jsp file data and information data, wherein the information data can comprise user name, version number information, information about and the like.
S202: and packaging the uploading data according to preset packaging rules to obtain uploading software information.
After the uploading data is obtained, the uploading data is packaged according to preset packaging rules, and the preset packaging rules are set in advance and are used for packaging the uploading data to obtain corresponding uploading software information. The number and the kind of the data items of the uploading data corresponding to different uploading requests are not necessarily the same, so that the uploading software information obtained by encapsulation is not necessarily the same.
S203: and storing the uploading software information.
After the uploading software information is obtained, the uploading software information is stored locally. Specifically, a storage unit may be newly created according to the file size of the uploaded software information, the uploaded software information may be stored in the newly created storage unit, and other operations such as software information numbering may be performed at the same time, which is not limited in this embodiment.
By applying the software version replacing method provided by the embodiment of the invention, before the target software information is determined, the corresponding uploading software information can be generated according to the uploading request and stored locally on the OEM platform so as to be used for generating the software of the corresponding version later.
Based on the above embodiment of the invention, a specific process of generating the target version software will be described in the embodiment of the invention. Referring to fig. 3, fig. 3 is a flowchart of a method for generating a target version software according to an embodiment of the present invention, including:
s301: and obtaining the current version of software from the TOMCAT server, and initializing the current version of software to obtain the initialized software.
In the embodiment of the invention, the OEM platform consists of an NGINX server and a TOMCAT server, wherein the TOMCAT server is used for storing the generated software and completing the normal business instructions of the user. Nginx (engine x) is a high-performance HTTP and reverse proxy server, and the Tomcat server is a Web server that provides a Web interface for users to call software through the Web interface. To ensure replacement accuracy when software information is replaced, some information is prevented from being replaced. The embodiment of the invention obtains the current version software from the TOMCAT server, and performs initialization processing on the current version software to obtain initialization software. The initialization process is to empty all the positions where the software information can be written in the current version of software, and the software does not contain any software information.
S302: and writing the target software information into a target position of the initialization software to obtain target version software, and storing the target version software into the TOMCAT server.
After the initialization software is acquired, the target software information is written into the target position of the initialization software, and the target version software is obtained. The target location is related to specific content of the target software information, and the specific location and number thereof are not limited in this embodiment. After the target version of software is obtained, the target version of software is stored in the TOMCAT server so that the user can call the target version of software.
Based on the above embodiment of the invention, a specific process for determining target software information and a process for modifying target software information corresponding to a user will be described in the embodiment of the invention. Referring to fig. 4, fig. 4 is a flowchart of a method for determining and modifying target software information according to an embodiment of the present invention, including:
s401: and acquiring the identity information in the login request.
In the embodiment of the invention, the login request is analyzed after being acquired, and the identity information can be obtained. The identity information is used for recording the identity of the user and determining the corresponding target software information of the user.
S402: and determining a target information number corresponding to the identity information by using the software information corresponding table, and determining the software information corresponding to the target information number as target software information.
The software information corresponding table is used for recording the software information corresponding to different users, and when a new user exists, the table items are newly added in the software information corresponding table. The entry of each software information correspondence table records the identity information of the user and the corresponding information change. After the identity information is acquired, the software information corresponding table is utilized to determine the target information number corresponding to the identity information, for example, the software information corresponding table can be traversed, the information number corresponding to the acquired identity information is determined to be the target information number, and the software information corresponding to the target information number is determined to be the target software information.
Further, the user may modify the corresponding software information, for example, the corresponding software information before the user modifies the corresponding software information into the software information a, and the user wants to modify the corresponding software information into the software information B according to the actual needs, and the specific modification process is S403 step and S404 step.
S403: and acquiring a modification request sent by a user, and determining first software information designated by the modification request.
In the embodiment of the invention, the user can send a modification request to the OEM platform for modifying the corresponding software information. The specific method for sending the modification request is not limited in this embodiment, for example, when the OEM platform is composed of an NGINX server and a TOMCAT server, the user may access the NGINX server to browse each piece of software information, and click to save after selecting the piece of software information to generate the modification request. The modification request is used to determine the first software information, and may include, for example, a number corresponding to the first software information, or may include a storage location of the first software information. After the modification request is obtained, the first software information is determined using the modification request.
S404: and modifying the target information number corresponding to the identity information in the software information corresponding table into a first information number corresponding to the first software information.
After the first software information is determined, the target information number corresponding to the identity information in the software information corresponding table is modified to be the first information number corresponding to the first software information, and then the software information modification corresponding to the user is completed.
Based on the above steps, in order to enable a user to obtain different services through the same IP access, the user may access the software platform, i.e. directly log in and call the software, and may access the OEM platform, i.e. perform management operations such as corresponding software information modification and uploading, and in the embodiment of the present invention, preferably, the access port number setting operation is performed, i.e. the requests with different port numbers are classified, for example, two port numbers may be set, the first is 443, the second is 82, and the requests sent through 443 are all requests for accessing the software platform, i.e. login requests; the requests sent through the 82 ports are all requests for OEM login, i.e. modification requests or upload requests.
After the access port number setting operation is performed, correspondingly, the step of obtaining a login request sent by a user comprises the following steps:
acquiring a first request through a port, and judging whether a port number corresponding to the first request is a first port number or not; and if the port number corresponding to the first request is the first port number, determining the first request as a login request.
The first port number is a port number for obtaining a login request.
Correspondingly, acquiring the modification request sent by the user comprises the following steps:
acquiring a second request through a port, and judging whether a port number corresponding to the second request is a second port number or not; and if the port number corresponding to the second request is the second port number, determining the second request as a modification request.
The second port number is a port number for acquiring the modification request.
The following describes a software version replacing device provided by an embodiment of the present invention, and the software version replacing device described below and the software version replacing method described above can be referred to correspondingly.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a software version replacing device according to an embodiment of the present invention, including:
a determining module 510, configured to obtain a login request sent by a user, and determine target software information according to the login request; wherein the target software information is stored locally;
a judging module 520, configured to judge whether the target software information is the same as the current software information;
and the generating module 530 is configured to replace the current software information in the current version software with the target software information if the target software information is different from the current software information, and generate the target version software.
Optionally, the determining module 510 includes:
the identity information acquisition unit is used for acquiring the identity information in the login request;
and the first determining unit is used for determining a target information number corresponding to the identity information by utilizing the software information corresponding table and determining the software information corresponding to the target information number as target software information.
Optionally, the method further comprises:
the modification request acquisition module is used for acquiring a modification request sent by a user and determining first software information designated by the modification request;
and the modifying module is used for modifying the target information number corresponding to the identity information in the software information corresponding table into a first information number corresponding to the first software information.
Optionally, the method further comprises:
the port number setting module is used for performing access port number setting operation;
accordingly, the determining module 510 includes:
the first judging unit is used for obtaining a first request through a port and judging whether the port number corresponding to the first request is the first port number or not;
a second determining unit, configured to determine the first request as a login request if the port number corresponding to the first request is the first port number;
correspondingly, the modification request acquisition module comprises:
the second judging unit is used for acquiring a second request through the port and judging whether the port number corresponding to the second request is the second port number or not;
and the third determining unit is used for determining the second request as a modification request if the port number corresponding to the second request is the second port number.
Optionally, the method further comprises:
the uploading data acquisition module is used for acquiring and analyzing the uploading request to obtain uploading data; the uploading data comprises logo picture data, HTML file data, jsp file data and information data;
the packaging module is used for packaging the uploading data according to preset packaging rules to obtain uploading software information;
and the storage module is used for storing the uploading software information.
Optionally, the method further comprises:
and the execution module is used for running the target version software and acquiring and executing the operation instruction sent by the user.
Optionally, the generating module 530 includes:
the initialization unit is used for acquiring the current version software from the TOMCAT server, and initializing the current version software to obtain initialization software;
and the generating unit is used for writing the target software information into the target position of the initialization software to obtain target version software, and storing the target version software into the TOMCAT server.
The following describes a software version replacing device provided by an embodiment of the present invention, and the software version replacing device described below and the software version replacing method described above may be referred to correspondingly.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a software version replacing device according to an embodiment of the present invention, where the software version replacing device includes a memory and a processor, and the structure includes:
a memory 610 for holding a computer program;
a processor 620 for executing a computer program to implement the software version replacement method described above.
The following describes a computer readable storage medium provided in an embodiment of the present invention, where the computer readable storage medium described below and the software version replacement method described above may be referred to correspondingly.
The invention also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor implements the steps of the software version replacement method described above.
The computer readable storage medium may include: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it is further noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The foregoing has described in detail a software version replacement method, a software version replacement device, a software version replacement apparatus and a computer readable storage medium, to which specific examples are applied to illustrate the principles and embodiments of the present invention, the above examples being provided only to help understand the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (9)
1. A software version replacement method, comprising:
acquiring a login request sent by a user, and determining target software information according to the login request; wherein the target software information is stored locally;
judging whether the target software information is the same as the current software information;
if the target software information is different from the current software information, replacing the current software information in the current version software by using the target software information to generate target version software;
correspondingly, the replacing the current software information in the current version software with the target software information to generate the target version software includes:
acquiring the current version software from a TOMCAT server, and initializing the current version software to obtain initialization software; the initialization process is to empty all the positions capable of writing in the software information in the current version of software, and does not contain any software information;
and writing the target software information into a target position of the initialization software to obtain the target version software, and storing the target version software into the TOMCAT server.
2. The software version replacement method according to claim 1, wherein the determining target software information according to the login request includes:
acquiring identity information in the login request;
and determining a target information number corresponding to the identity information by using a software information corresponding table, and determining the software information corresponding to the target information number as the target software information.
3. The software version replacement method according to claim 2, further comprising:
acquiring a modification request sent by the user, and determining first software information designated by the modification request;
and modifying the target information number corresponding to the identity information in the software information corresponding table into a first information number corresponding to the first software information.
4. The software version replacement method according to claim 3, further comprising, before said obtaining the login request sent by the user:
performing an access port number setting operation;
correspondingly, the obtaining the login request sent by the user includes:
acquiring a first request through a port, and judging whether a port number corresponding to the first request is a first port number or not;
if the port number corresponding to the first request is a first port number, determining the first request as the login request;
correspondingly, the obtaining the modification request sent by the user includes:
acquiring a second request through the port, and judging whether the port number corresponding to the second request is a second port number or not;
and if the port number corresponding to the second request is the second port number, determining the second request as the modification request.
5. The software version replacement method according to any one of claims 1 to 4, further comprising:
acquiring and analyzing an uploading request to obtain uploading data; the uploading data comprises logo picture data, HTML file data, jsp file data and information data;
packaging the uploading data according to preset packaging rules to obtain uploading software information;
and storing the uploading software information.
6. The software version replacement method according to claim 1, further comprising, after the generating the target version software:
and running the target version software, and acquiring and executing the operation instruction sent by the user.
7. A software version replacement apparatus, comprising:
the determining module is used for acquiring a login request sent by a user and determining target software information according to the login request; wherein the target software information is stored locally;
the judging module is used for judging whether the target software information is the same as the current software information;
the generation module is used for replacing the current software information in the current version software by utilizing the target software information if the target software information is different from the current software information, so as to generate the target version software;
correspondingly, the generating module comprises:
the initialization unit is used for acquiring the current version software from the TOMCAT server, and initializing the current version software to obtain initialization software; the initialization process is to empty all the positions capable of writing in the software information in the current version of software, and does not contain any software information;
and the generating unit is used for writing the target software information into the target position of the initialization software to obtain target version software, and storing the target version software into the TOMCAT server.
8. A software version replacement device comprising a memory and a processor, wherein:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the software version replacement method according to any one of claims 1 to 6.
9. A computer readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the software version replacement method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911342537.5A CN111158749B (en) | 2019-12-23 | 2019-12-23 | Software version replacement method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911342537.5A CN111158749B (en) | 2019-12-23 | 2019-12-23 | Software version replacement method, device, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111158749A CN111158749A (en) | 2020-05-15 |
| CN111158749B true CN111158749B (en) | 2023-12-01 |
Family
ID=70558192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911342537.5A Active CN111158749B (en) | 2019-12-23 | 2019-12-23 | Software version replacement method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111158749B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179425A (en) * | 2006-12-11 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Client terminal software updating control method and system |
| CN101877650A (en) * | 2010-05-20 | 2010-11-03 | 中兴通讯股份有限公司 | Method and system for updating software version automatically |
| CN103593183A (en) * | 2013-11-01 | 2014-02-19 | 浪潮电子信息产业股份有限公司 | Construction method for system compatible with mainline version and OEM versions |
| CN106603311A (en) * | 2017-01-18 | 2017-04-26 | 北京洋浦伟业科技发展有限公司 | OTA upgrade method, client, server and system |
| CN106909429A (en) * | 2017-04-05 | 2017-06-30 | 微鲸科技有限公司 | A kind of synchronous upgrade method and device |
| CN107688464A (en) * | 2017-06-28 | 2018-02-13 | 上海壹账通金融科技有限公司 | Software customized server, method and computer-readable recording medium |
| CN109408067A (en) * | 2018-10-22 | 2019-03-01 | 浙江明度智控科技有限公司 | A kind of data managing method and server based on monomer applications |
| CN109669672A (en) * | 2018-12-14 | 2019-04-23 | 郑州云海信息技术有限公司 | A kind of neutralisation version building, page response method, system and relevant apparatus |
| CN110244963A (en) * | 2019-05-24 | 2019-09-17 | 深圳市明源云科技有限公司 | Data-updating method, device and terminal device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10719312B2 (en) * | 2017-09-13 | 2020-07-21 | Fisher-Rosemount Systems, Inc. | Systems and methods for assessing configuration files associated with a process control system |
-
2019
- 2019-12-23 CN CN201911342537.5A patent/CN111158749B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179425A (en) * | 2006-12-11 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Client terminal software updating control method and system |
| CN101877650A (en) * | 2010-05-20 | 2010-11-03 | 中兴通讯股份有限公司 | Method and system for updating software version automatically |
| CN103593183A (en) * | 2013-11-01 | 2014-02-19 | 浪潮电子信息产业股份有限公司 | Construction method for system compatible with mainline version and OEM versions |
| CN106603311A (en) * | 2017-01-18 | 2017-04-26 | 北京洋浦伟业科技发展有限公司 | OTA upgrade method, client, server and system |
| CN106909429A (en) * | 2017-04-05 | 2017-06-30 | 微鲸科技有限公司 | A kind of synchronous upgrade method and device |
| CN107688464A (en) * | 2017-06-28 | 2018-02-13 | 上海壹账通金融科技有限公司 | Software customized server, method and computer-readable recording medium |
| CN109408067A (en) * | 2018-10-22 | 2019-03-01 | 浙江明度智控科技有限公司 | A kind of data managing method and server based on monomer applications |
| CN109669672A (en) * | 2018-12-14 | 2019-04-23 | 郑州云海信息技术有限公司 | A kind of neutralisation version building, page response method, system and relevant apparatus |
| CN110244963A (en) * | 2019-05-24 | 2019-09-17 | 深圳市明源云科技有限公司 | Data-updating method, device and terminal device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111158749A (en) | 2020-05-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Wittig et al. | Amazon Web Services in Action: An in-depth guide to AWS | |
| US11269660B2 (en) | Methods and systems for integrated development environment editor support with a single code base | |
| US7543228B2 (en) | Template for rendering an electronic form | |
| Menasce et al. | Capacity Planning for Web Performance: metrics, models, and methods | |
| US10983774B2 (en) | Extensions for deployment patterns | |
| JP6463393B2 (en) | Tenant data recovery across tenant migration | |
| CN104067276B (en) | Client-side minimum is downloaded and the page navigation feature of simulation | |
| US9165087B2 (en) | Validity path node pattern for structure evaluation of time-dependent acyclic graphs | |
| US8983935B2 (en) | Methods for utilizing a javascript emulator in a web content proxy server and devices thereof | |
| US20080162616A1 (en) | Skip relation pattern for graph structures | |
| US9032367B2 (en) | Providing a demo appliance and migrating the demo appliance to a production appliance | |
| WO2017083156A1 (en) | Generation of an application from template | |
| US20170091069A1 (en) | Testing of software upgrade | |
| US20080162563A1 (en) | Generic graph services utilizing anonymous and identified graph pattern | |
| Kunszt et al. | iPortal: the swiss grid proteomics portal: Requirements and new features based on experience and usability considerations | |
| US11334472B2 (en) | Automated testing for metadata-driven custom applications | |
| US20080162777A1 (en) | Graph abstraction pattern for generic graph evaluation | |
| US10019293B2 (en) | Enhanced command selection in a networked computing environment | |
| US10055393B2 (en) | Distributed version control of orchestration templates | |
| CN110213105A (en) | It is a kind of cross-platform micro- using creation method | |
| US10951540B1 (en) | Capture and execution of provider network tasks | |
| US10452371B2 (en) | Automating enablement state inputs to workflows in z/OSMF | |
| US9037597B2 (en) | Verifying file versions in a networked computing environment | |
| CN105739717B (en) | Data inputting method and device | |
| CN111158749B (en) | Software version replacement method, device, equipment and readable storage medium |
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 |