Version updating system and version updating method

Abstract

The invention provides a version updating system and a version updating method. The version updating system comprises a cloud server. The cloud server is used for executing the version updating tool, the version matching component and the heterogeneous system management module. The heterogeneous system management module communicates with the heterogeneous system and the sub-service system. When the cloud server receives a version updating requirement of the cloud application program, the version updating tool executes the version matching component, so that the version matching component obtains version information of the heterogeneous system through the heterogeneous system management module. When the version information of the heterogeneous system does not meet the version requirement, the version matching component records that the version information of the heterogeneous system does not meet the version requirement, and the version matching component sends a version updating notification to the sub-service system. And after the sub-service system stops operation according to the version updating notification, the version matching component notifies a version updating tool to enable the version updating tool to perform version updating operation of the cloud application program.

Description

Technical Field

[0001] The present invention relates to a maintenance method for cloud applications and heterogeneous systems, and in particular to a version update system and a version update method. Background Art

[0002] After the service system applied to the local enterprise (such as the Enterprise Resource Planning (ERP) system) is connected to the cloud service framework, there will be a problem of consistency between the cloud system application and the enterprise-side application version. Because the local enterprise service may be deployed in the traditional overall service mode, the modification of an application requires the update of the operating software of the entire system. However, the operating software also contains many different applications, and it is not released in the form of Software as a Service (SaaS) in the cloud system. In this regard, the cloud system application must not only be implemented with hot deployment, but also be oriented to all enterprises served by software vendors, but the system upgrades of each enterprise may have completely different operating results. Summary of the invention

[0003] According to an embodiment of the present invention, the version update system of the present invention includes a cloud server. The cloud server is used to execute a version update tool, a version matching component and a heterogeneous system management module. The heterogeneous system management module communicates with the heterogeneous system and the sub-business system. When the cloud server receives a version update request of a cloud application, the version update tool executes the version matching component so that the version matching component obtains the version information of the heterogeneous system through the heterogeneous system management module. When the version information of the heterogeneous system does not meet the version requirement, the version matching component records that the version information of the heterogeneous system does not meet the version requirement, and the version matching component sends a version update notification to the sub-business system. After the sub-business system stops operating according to the version update notification, the version matching component notifies the version update tool so that the version update tool performs the version update operation of the cloud application.

[0004] According to an embodiment of the present invention, the version update method of the present invention includes the following steps: when a cloud server receives a version update request from a cloud application, a version matching component is executed through a version update tool, so that the version matching component obtains the version information of the heterogeneous system through a heterogeneous system management module; when the version information of the heterogeneous system does not meet the version requirement, the version matching component is used to record that the version information of the heterogeneous system does not meet the version requirement, and a version update notification is sent to a sub-business system through the version matching component; and after the sub-business system stops operating according to the version update notification, the version update tool is notified through the version matching component, so that the version update tool performs a version update operation on the cloud application.

[0005] Based on the above, the version update system and the version update method of the present invention can effectively update the version of the cloud application.

[0006] In order to make the above features and advantages of the present invention more clearly understood, embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a schematic diagram of a version update system according to an embodiment of the present invention;

[0008] Figure 2 is a schematic diagram of a version updating method according to an embodiment of the present invention;

[0009] Figure 3 is a schematic diagram of a version update process of a cloud application program according to an embodiment of the present invention;

[0010] Figure 4 is a schematic diagram of a version update process of a heterogeneous system according to an embodiment of the present invention;

[0011] Figure 5 It is a flow chart of calling a heterogeneous system according to an embodiment of the present invention.

[0012] Description of Reference Numerals

[0013] 100: Version update system;

[0014] 110: cloud server;

[0015] 111: Version update tool;

[0016] 112: Version matching component;

[0017] 113: Heterogeneous system management module;

[0018] 120_1~120_M: sub-business system;

[0019] 130_1~130_N: heterogeneous system;

[0020] 301: front-end page;

[0021] 302: Designer;

[0022] 401: Cloud system service component;

[0023] 501: message distribution unit;

[0024] 502: Enterprise subscription application relationship management service;

[0025] S210~S230, S301~S319, S401~S405, S501~S509: steps. DETAILED DESCRIPTION

[0026] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numerals are used in the drawings and the description to refer to the same or like parts.

[0027] Figure 1 Schematic diagram of a version update system according to an embodiment of the present invention. Figure 1 , the version update system 100 includes a cloud server 110, wherein the cloud server 110 is suitable for communicating with the sub-business systems 120_1~120_M and the heterogeneous systems 130_1~130_N in a wired, wireless or Internet manner, wherein M and N are positive integers respectively. In this embodiment, the sub-business systems 120_1~120_M can be set in the cloud server 110, or other cloud servers. The heterogeneous systems 130_1~130_N can be set in the same or different local servers. Alternatively, the heterogeneous systems 130_1~130_N can also be set in a private cloud server deployed by the enterprise. In this embodiment, the cloud server 110 can execute a version update tool 111, a version matching component 112, and a heterogeneous system management module 113.

[0028] In this embodiment, the cloud server 110 may include a processor and a storage device. The processor may be a system on a chip (SOC), or may include, for example, a central processing unit (CPU) or other programmable general-purpose or special-purpose microprocessor, a digital signal processor (DSP), a programmable controller, an application-specific integrated circuit (ASIC), a programmable logic device (PLD), other similar processing devices or a combination of these devices. The storage device may be, for example, a dynamic random access memory (DRAM), a flash memory or a non-volatile random access memory (NVRAM). The storage device may store the version update tool 111, the version matching component 112 and the heterogeneous system management module 113 for execution by the processor.

[0029] In this embodiment, the cloud server 110 can be used for, but not limited to, implementing the distributed architecture of Kubernetes (K8S), wherein Kubernetes (K8S) can be a system for managing microservices, and can automatically deploy and manage multiple containers on multiple machines. In this regard, the version update tool 111, the version matching component 112, the heterogeneous system management module 113, and the designer, the front-end page message distribution unit, and the enterprise subscription application relationship management service in the following embodiments can be deployed on the cloud server and run as an independent service through a container. In one embodiment, the version update tool 111, the version matching component 112, the heterogeneous system management module 113, and the designer, the front-end page message distribution unit, and the enterprise subscription application relationship management service in the following embodiments can also be implemented in programming languages ​​such as JSON (JavaScript Object Notation), Extensible Markup Language (XML), or YAML.

[0030] Figure 2 Schematic diagram of a version update method according to an embodiment of the present invention. Figure 1 as well as Figure 2 , the version update system 100 may execute the following steps S210 to S230 to implement the version update operation. In step S210, when the cloud server 110 receives the version update request of the cloud application, the version update tool 111 may execute the version matching component 112, so that the version matching component 112 obtains the version information of the heterogeneous systems 130_1 to 130_N through the heterogeneous system management module 113. In step S220, when the version information of at least one of the heterogeneous systems 130_1 to 130_N does not meet the version requirement, the version matching component 112 records that the version information of at least one of the heterogeneous systems 130_1 to 130_N does not meet the version requirement, and the version matching component 112 sends a version update notification to the business subsystems 120_1 to 120_M. In step S230, after the business subsystems 120_1 to 120_M stop operating according to the version update notification, the version matching component 112 notifies the version update tool 111 so that the version update tool 111 performs the version update operation of the cloud application. Therefore, the version update method of the present invention can effectively avoid the situation where the business subsystems 120_1 to 120_M mistakenly call the heterogeneous systems 130_1 to 130_N when the cloud application performs the version update. However, the detailed version update operation of the cloud application will be described in detail by the following embodiments.

[0031] Figure 3Schematic diagram of the version update process of the cloud application program according to an embodiment of the present invention. Figure 1 as well as Figure 3 In this embodiment, the version update system 100 may perform the following steps S301 to S312 to perform the version update operation of the cloud application. In step S301, the version update tool 111 may receive a version update request instruction, for example, issued by a software update publisher. In step S302, the version update tool 111 may execute instructions to operate the version matching component 112. In step S303, the version matching component 112 may notify the user or designer (operated by the software designer in the software development or enterprise setting stage) through the front-end page 301, for example, five minutes in advance to stop using it. In step S304, the version update tool 111 may wait for a preset time (for example, five minutes) before performing subsequent operations. In step S305, the version update tool 111 sends a version update notification to the version matching component 112 to perform the stop operation process. In step S306, the version matching component 112 sends a version update notification to the business subsystem 120 (this embodiment is described with one business subsystem, which can be analogized to multiple cases), so that the business subsystem 120 suspends the call operation and notifies the user or tenant to stop the operation. The business subsystem 120 can be, for example, a data change perception subsystem, a workflow subsystem, or a front-end page subsystem, etc., but the present invention is not limited thereto. Taking the data change perception subsystem as an example, in step S307, the business subsystem 120 can reject the operation of the designer 302 (operated by the software designer in the software development or enterprise setting stage). In step S308, after the designer 302 successfully suspends the operation, the designer 302 notifies the business subsystem 120. In step S309, the business subsystem 120 notifies the version matching component 112 that the suspension has been completed. In step S310, the version matching component 112 notifies the version update tool 111 that the suspension has been completed. In step S311, the version update tool 111 performs the version update operation of the cloud application. In step S312 , the version update tool 111 notifies the version matching component 112 of the successful completion of the version update or the failure of the version update.

[0032] In this embodiment, when the cloud application successfully completes the version update operation, the version update system 100 may perform the following steps S312 to S317. In step S312, the version update tool 111 may notify the version matching component 112 to update the version information of the cloud application. In step S313, the version matching component 112 may notify the heterogeneous system management module 113. In step S314, the heterogeneous system management module 113 may obtain / update the version information of the heterogeneous system 130 (this embodiment is described with one heterogeneous system, which can be analogized to multiple situations). In step S315, the heterogeneous system management module 113 may synchronize and update the version information of the heterogeneous system 130 to the version matching component 112. In this embodiment, when the version information of the cloud application is inconsistent with the version information of the heterogeneous system 130, the version matching component 112 may periodically access the heterogeneous system management module 113 to continuously update the version information of the heterogeneous system 130 (i.e., the latest stable version), and compare its result with that of the cloud application. In step S316, the version matching component 112 may notify the business subsystem 120. In step S317, the business subsystem 120 resumes the operation of the designer 302 or notifies the user or tenant that the cloud application successfully completes the version update.

[0033] In this embodiment, when the cloud application fails to be updated, the version update system 100 may perform the following steps S312, S318-S319. In step S312, the version update tool 111 may notify the version matching component 112 so that the version matching component 112 may cancel the version update of the heterogeneous system 130 through the heterogeneous system management module 113. In step S318, the version matching component 112 may notify the business subsystem 120. In step S319, the business subsystem 120 restores the operation of the designer 302 or notifies the user or tenant that the cloud application version update failed.

[0034] Therefore, the version update system 100 and the version update method of this embodiment can automatically sense and operate the heterogeneous system of the enterprise system to suspend the provision of business services when the cloud application running on the cloud server is updated, so as to effectively avoid service operation errors. In addition, the version update system 100 and the version update method of this embodiment can instantly update the version information or instantly restore the system operation according to the result of the success or failure of the update of the cloud application.

[0035] Figure 4 Schematic diagram of the version update process of the heterogeneous system according to an embodiment of the present invention. Figure 1 as well as Figure 4, the version update system 100 may perform the following steps S401 to S405 to implement the version update of the heterogeneous system (enterprise local system). In this embodiment, the cloud server 110 may also execute the cloud system service component 401. In step S401, the cloud system service component 401 may receive the latest installed component. In step S402, the heterogeneous system 130 may connect to the cloud system service component 401 according to the user or tenant operation or automatically to scan whether there is the latest installed component. In step S403, the heterogeneous system 130 may obtain the latest installed component from the cloud system service component 401. In step S404, when the heterogeneous system 130 completes the version update according to the latest installed component, the heterogeneous system 130 notifies the heterogeneous system management module 113. If the heterogeneous system 130 fails to update, the heterogeneous system 130 will also notify the heterogeneous system management module 113. Therefore, the heterogeneous system management module 113 can effectively record the version information of the heterogeneous system 130.

[0036] Figure 5 Schematic diagram of the flow of calling a heterogeneous system according to an embodiment of the present invention. Figure 1 as well as Figure 5 , the version update system 100 may perform the following steps S501 to S509, so as to determine whether to stop the sub-business system 120 from calling the heterogeneous system 130 when the cloud application is notified of the version update. In this embodiment, the cloud server 110 may also execute the message distribution unit 501 and the enterprise subscription application relationship management service 502. In step S501, the sub-business system 120 may initiate a call request and provide a business code to the message distribution unit 501. In step S502, the message distribution unit 501 sends the business code to the enterprise subscription application relationship management service 502. In step S503, the enterprise subscription application relationship management service 502 provides the corresponding application name and product name (including the cloud system application name version number and the minimum enterprise application version number of the heterogeneous system) to the message distribution unit 501 according to the business code. In step S504, the message distribution unit 501 obtains the dependency relationship between the cloud application and the heterogeneous system 130 through the heterogeneous system management module 113 to determine whether the version information of the heterogeneous system 130 meets the version requirements. The message distribution unit 501 may obtain the application name and product name from the enterprise subscription application relationship management service 502 according to the business code, and provide them to the heterogeneous system management module 113. In step S505, the heterogeneous system management module 113 obtains the dependency relationship between the cloud application and the heterogeneous system 130 according to the application name and the product name. In this embodiment, the dependency relationship may be the dependency relationship between the cloud system application name version number of the cloud application and the minimum enterprise application version number of the heterogeneous system.

[0037] In step S506, when the version information of the heterogeneous system meets the version requirements, the heterogeneous system management module 113 initiates a data call to the heterogeneous system 130. In step S507, the heterogeneous system 130 may return data to the message distribution unit 501. In step S508, the message distribution unit 501 may return data to the sub-business system 120 to complete the call. In another case, when the version information of the heterogeneous system does not meet the version requirements, the heterogeneous system management module 113 notifies the message distribution unit 501 to suspend (reject) access to the heterogeneous system 130. Therefore, the version update system 100 of this embodiment can effectively avoid service operation errors when the cloud application running on the cloud server is updated.

[0038] Regarding the dependency relationship between the cloud system application name version number of the cloud application and the minimum enterprise application version number of the heterogeneous system, please refer to the following Table 1 for an example. First of all, it is explained that the data required by the cloud application comes from the enterprise application (i.e., the heterogeneous system). In this regard, even if the version of the enterprise application is old, it can still provide enough data for the cloud application with a newer version to use, so the cloud application needs to give it the oldest enterprise application version number that it depends on for operation. The version number is established by the operator performing the version update operation of the cloud application. Before performing the version update operation of the cloud application, the operator can provide or select the cloud-ground version correspondence relationship to generate and record the version number data. For example, when a new version of a cloud application is released and the version correspondence relationship between the cloud application and the enterprise application needs to be created, the information is recorded. Therefore, when the cloud system is continuously updated in the subsequent version, the relationship will not be updated until the cloud application and the enterprise application need to be updated at the same time, and then the relationship will be updated again. This information record can be used to determine the dependency relationship between the cloud system application name version number of the cloud application and the minimum enterprise application version number of the heterogeneous system.

[0039] Referring to Table 1 below, it is assumed that the cloud application and the heterogeneous system are updated on April 10, May 10, June 10, and July 10, respectively. On April 10, the cloud application and the heterogeneous system respectively successfully perform the version update operation, and the system (i.e., the cloud server) can record the dependency relationship between the version "1.0" of the cloud application and the version "1.0" of the heterogeneous system based on the operator's settings. On May 10, the cloud application and the heterogeneous system respectively successfully perform the version update operation, and the system (i.e., the cloud server) can record the dependency relationship between the version "1.1" of the cloud application and the version "1.03" of the heterogeneous system based on the operator's settings. On June 10, the cloud application and the heterogeneous system respectively successfully perform the version update operation, and the system (i.e., the cloud server) can record the dependency relationship between the version "1.2" of the cloud application and the version "1.06" of the heterogeneous system based on the operator's settings. On July 10, the cloud application and the heterogeneous system successfully executed version update operations respectively, and the system (i.e., the cloud server) was able to record the dependency between version "1.3" of the cloud application and version "1.12" of the heterogeneous system based on the operator's settings.

[0040] It is worth noting that on June 10, assuming that the system determines that the heterogeneous system failed to upgrade and remains at version "1.03", since the system can query the version "1.0" that depends on the heterogeneous system through the cloud application version "1.2", it means that the heterogeneous system can still provide enough data for the cloud application to use. In this way, the system can automatically determine that the cloud application service (that is, the call to the heterogeneous system) does not need to be suspended.

[0041]

[0042] Table 1

[0043] In summary, the version update system and version update method of the present invention can automatically sense and operate whether the heterogeneous systems of the enterprise system suspend providing business services when the cloud application running on the cloud server is updated, so as to effectively avoid service operation errors.

[0044] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A version update system, characterized in that: include: A cloud server is used to execute a version update tool, a version matching component, and a heterogeneous system management module, wherein the heterogeneous system management module communicates with the heterogeneous system and the sub-business system, When the cloud server receives a version update request from a cloud application, the version update tool executes the version matching component so that the version matching component obtains the version information of the heterogeneous system through the heterogeneous system management module. When the version information of the heterogeneous system does not meet the version requirement, the version matching component records that the version information of the heterogeneous system does not meet the version requirement, and the version matching component sends a version update notification to the sub-business system. After the sub-business system stops operating according to the version update notification, the version matching component notifies the version update tool so that the version update tool performs a version update operation on the cloud application.

2. The version update system according to claim 1, characterized in that: When the cloud application successfully completes the version update operation, the version update tool notifies the version matching component to update the version information of the cloud application.

3. The version update system according to claim 1, characterized in that: When the cloud application fails to be updated, the version update tool notifies the version matching component, and the version matching component cancels the version update of the heterogeneous system through the heterogeneous system management module.

4. The version update system according to claim 1, characterized in that: The cloud server is also used to execute the cloud system service component, wherein the heterogeneous system is connected to the cloud system service component to obtain the latest installation component, and when the heterogeneous system completes the version update according to the latest installation component, the heterogeneous system notifies the heterogeneous system management module.

5. The version update system according to claim 1, characterized in that: The cloud server is also used to execute a message distribution unit, wherein the sub-business system initiates a call request to the message distribution unit, The message distribution unit obtains the dependency relationship between the cloud application and the heterogeneous system through the heterogeneous system management module to determine whether the version information of the heterogeneous system meets the version requirement.

6. The version update system according to claim 5, characterized in that: When the version information of the heterogeneous system does not meet the version requirement, the heterogeneous system management module notifies the message distribution unit to deny access to the heterogeneous system.

7. The version update system according to claim 5, characterized in that: When the version information of the heterogeneous system meets the version requirement, the heterogeneous system management module initiates a data call to the heterogeneous system and returns data through the message distribution unit.

8. The version update system according to claim 5, characterized in that: The dependency relationship is the dependency relationship between the cloud system application name version number of the cloud application program and the minimum enterprise application version number of the heterogeneous system.

9. The version update system according to claim 5, characterized in that: The cloud server is also used to execute the enterprise subscription application relationship management service. The sub-business system provides the business code to the message distribution unit. The message distribution unit obtains the application name and product name from the enterprise subscription application relationship management service according to the business code, and provides them to the heterogeneous system management module, so that the heterogeneous system management module obtains the dependency relationship between the cloud application and the heterogeneous system according to the application name and the product name.

10. The version update system according to claim 1, characterized in that: The heterogeneous system management module periodically accesses the heterogeneous system to update the version information of the heterogeneous system.

11. A version update method, characterized in that: include: When the cloud server receives a version update request from the cloud application, the version matching component is executed through the version update tool, so that the version matching component obtains the version information of the heterogeneous system through the heterogeneous system management module; When the version information of the heterogeneous system does not meet the version requirement, the version matching component records that the version information of the heterogeneous system does not meet the version requirement, and sends a version update notification to the sub-business system through the version matching component; as well as After the sub-business system stops operating according to the version update notification, the version update tool is notified through the version matching component, so that the version update tool performs a version update operation of the cloud application.

12. The version update method according to claim 11, characterized in that: Also includes: When the cloud application successfully completes the version update operation, the version matching component is notified through the version update tool to update the version information of the cloud application.

13. The version update method according to claim 11, characterized in that: Also includes: When the cloud application fails to be updated, notifying the version matching component through the version update tool; as well as The version update of the heterogeneous system is canceled through the version matching component and the heterogeneous system management module.

14. The version update method according to claim 11, characterized in that: Also includes: Connecting to the cloud system service component through the heterogeneous system to obtain the latest installed component; as well as When the heterogeneous system completes the version update according to the latest installed component, the heterogeneous system notifies the heterogeneous system management module through the heterogeneous system.

15. The version update method according to claim 11, characterized in that: Also includes: Initiate a call request to the message distribution unit through the sub-business system; as well as The message distribution unit obtains the dependency relationship between the cloud application and the heterogeneous system through the heterogeneous system management module to determine whether the version information of the heterogeneous system meets the version requirement.

16. The version update method according to claim 15, characterized in that: Also includes: When the version information of the heterogeneous system does not meet the version requirement, the message distribution unit is notified through the heterogeneous system management module to deny access to the heterogeneous system.

17. The version update method according to claim 15, characterized in that: Also includes: When the version information of the heterogeneous system meets the version requirement, a data call is initiated to the heterogeneous system through the heterogeneous system management module, and data is returned through the message distribution unit.

18. The version update method according to claim 15, characterized in that: The dependency relationship is the dependency relationship between the cloud system application name version number of the cloud application program and the minimum enterprise application version number of the heterogeneous system.

19. The version update method according to claim 15, characterized in that: Also includes: Providing a service code to the message distribution unit through the sub-service system; as well as The message distribution unit obtains the application name and product name from the enterprise subscription application relationship management service according to the business code, and provides them to the heterogeneous system management module, so that the heterogeneous system management module obtains the dependency relationship between the cloud application and the heterogeneous system according to the application name and the product name.

20. The version update method according to claim 11, characterized in that: The heterogeneous system management module periodically accesses the heterogeneous system to update the version information of the heterogeneous system.

Images