CN112882741A - Application management system and method - Google Patents
Application management system and method Download PDFInfo
- Publication number
- CN112882741A CN112882741A CN201911200912.2A CN201911200912A CN112882741A CN 112882741 A CN112882741 A CN 112882741A CN 201911200912 A CN201911200912 A CN 201911200912A CN 112882741 A CN112882741 A CN 112882741A
- Authority
- CN
- China
- Prior art keywords
- application
- sub
- new sub
- new
- configuration 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000007726 management method Methods 0.000 claims description 47
- 230000001419 dependent effect Effects 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 9
- 239000000126 substance Substances 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims 2
- 230000037430 deletion Effects 0.000 claims 2
- 238000011161 development Methods 0.000 abstract description 9
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 241001417516 Haemulidae Species 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
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
- G06F8/656—Updates while running
-
- 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
- G06F8/658—Incremental updates; Differential updates
-
- 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
Abstract
The invention discloses an application management system and method, and relates to the technical field of computers. One embodiment of the application management system includes: an application configuration center and an application management center; the application configuration center is used for receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and the configuration information of the applications is updated according to the sub-application updating request; and the application management center is used for updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time. The embodiment can realize the hot update of the sub-application, realize the unified management and maintenance of the sub-application and improve the development efficiency of the sub-application.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an application management system and method.
Background
In the actual development process, a great deal of time and energy are consumed for realizing the development of the application from zero to some, and in order to improve the development efficiency of the application, various scaffold tools are produced, such as Create-React-app officially released by act (a JavaScript library for constructing a user interface), Vue-cli officially released by Vue (a progressive framework for constructing a web interface), and the like, which greatly improve the efficiency of the application development.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: the existing scaffold tool has poor expansibility, only supports single frames such as React or Vue and the like, has high later maintenance cost under the condition of needing a plurality of scaffold tools, and does not support the unified management and maintenance of a plurality of applications; under the condition that the configuration file has an update, the application needs to be restarted, the hot update cannot be supported, and the user experience is poor.
Disclosure of Invention
In view of this, the present invention provides an application management system and method, which can implement thermal update of sub-applications, implement unified management and maintenance of sub-applications, and improve the development efficiency of sub-applications.
To achieve the above object, according to one aspect of the present invention, there is provided an application management system including: an application configuration center and an application management center; wherein the content of the first and second substances,
the application configuration center is used for receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and the configuration information of the applications is updated according to the sub-application updating request;
and the application management center is used for updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time.
Optionally, the sub-application is comprised of one or more middleware invoked in sequence.
Optionally, the method further comprises: an application routing center; wherein the content of the first and second substances,
the application configuration center is further configured to receive a new sub-application request sent by a user, and update configuration information of an application to which a new sub-application belongs according to the new sub-application request;
the application management center is used for creating the new sub-application according to the configuration information;
and the application routing center is used for updating the routing information of the application to which the new sub-application belongs according to the configuration information so that the new sub-application is called according to the routing information.
Optionally, the creating the new sub-application according to the configuration information includes:
registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs;
registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs;
creating the new sub-application according to the middleware called by the new sub-application;
and sequentially loading and executing the middleware to start the new application.
Optionally, the updating, according to the configuration information, the routing information of the application to which the new sub-application belongs includes:
determining the routing information of the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application.
Optionally, the middleware called by the new sub-application includes: a module packer;
the application management center is further configured to set the query dependent path of the module packager as a preset integrated query dependent path before the child new application is created.
Optionally, the new sub-application request indicates a name of the new sub-application;
the application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, notify the user that the name of the new sub-application is wrong.
Optionally, the application configuration center is further configured to receive a request for deleting a sub-application sent by a user, and update configuration information of an application to which the sub-application belongs according to the request for deleting the sub-application;
the application management center is used for deleting the sub-application according to the configuration information;
and the application routing center is used for updating the routing information of the application to which the sub-application belongs according to the configuration information so that the sub-application cannot be called according to the routing information.
In order to achieve the above object, according to another aspect of the present invention, there is provided an application management method applied to an application management system, including:
receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and updating the configuration information of the applications according to the sub-application updating request;
and updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time.
Optionally, the sub-application is comprised of one or more middleware invoked in sequence.
Optionally, the method further comprises:
receiving a new sub-application request sent by a user, and updating configuration information of an application to which a new sub-application belongs according to the new sub-application request;
creating the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the configuration information so that the new sub-application is called according to the routing information.
Optionally, the creating the new sub-application according to the configuration information includes:
registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs;
registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs;
creating the new sub-application according to the middleware called by the new sub-application;
and sequentially loading and executing the middleware to start the new application.
Optionally, the updating, according to the configuration information, the routing information of the application to which the new sub-application belongs includes:
determining the routing information of the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application.
Optionally, the middleware called by the new sub-application includes: a module packer;
and before the new sub-application is created, setting the query dependent path of the module packer as a preset integrated query dependent path.
Optionally, the method further comprises:
the new sub-application request indicates the name of the new application;
and judging whether the name of the new sub-application exists in the current configuration list, and if so, notifying the user that the name of the new sub-application is wrong.
Optionally, receiving a request for deleting a sub-application sent by a user, and updating configuration information of an application to which the sub-application belongs according to the request for deleting the sub-application;
deleting the sub-application according to the configuration information;
and updating the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic device for application management, including: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method of any of the application management methods described above.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer readable medium having stored thereon a computer program, characterized in that the program, when executed by a processor, implements any of the methods of application management as described above.
The invention has the following advantages or beneficial effects: the application configuration center of the application management system can generate or configure configuration information of the application, and unified management and maintenance of one or more sub-applications are realized by newly building the sub-applications, deleting the sub-applications, updating the sub-applications and the like in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before updating and the like, and the updated middleware is loaded and run when the sub-application is started next time, so that the hot update of the sub-application is realized. In addition, before the new word application is created, the path on which the module packager of the sub-application queries depends is changed into the preset integrated query path of the module packager integrating one or more sub-applications, so that the number of query dependent paths required to be installed when the sub-application is newly created is greatly reduced, the creation time is shortened, and the development efficiency of the application is improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of the main structure of an application management system according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a main flow of a method for updating a sub-application applied to a management system according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of the main flow of a method for managing a newly created sub-application of a system according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of the main flow of another method for managing a newly created sub-application of a system according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a main flow of a method for deleting a sub-application applied to a management system according to an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of the main structure of an application management system according to an embodiment of the present invention; as shown in fig. 1, an application management system 100 includes: an application configuration center 101 and an application management center 102; wherein the content of the first and second substances,
the application configuration center 101 is configured to receive a sub-application update request sent by a user, where the sub-application belongs to one or more applications, and update configuration information of the application according to the sub-application update request;
the application management center 102 is configured to update one or more middleware called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middleware when being started next time.
It will be appreciated that the sub-applications can be attributed to one or more applications, and as such, one or more sub-applications can be attributed to the same application. For example, there are multiple boards under a product, such as a monitoring platform, the whole platform can be regarded as an application, and the application has a mobile phone terminal monitoring sub-application, a PC segment monitoring sub-application, and the like. The one or more middleware invoked by the sub-application includes, but is not limited to, message middleware, module packagers, Apache, and the like. In a preferred embodiment, the sub-application is made up of one or more middleware that are invoked in sequence. That is, the sub-application is composed by one or more middleware to accelerate the construction or update of the sub-application, or the like. Therefore, the update request of the sub-application includes, but is not limited to, update of the number of pieces of middleware constituting the sub-application, change of the kind of middleware, change of an instance of the middleware, and the like. It is noted that the updating of the sub-application may be implemented both in case the sub-application is started and in case the sub-application is already closed. When updating is carried out under the condition that the sub-application is started, the currently operated sub-application still uses one or more middleware which are loaded and executed during the starting, meanwhile, the middleware is updated according to the notification of the application configuration center, and after the sub-application is closed after the starting and the running are finished, the updated one or more middleware is loaded and used when a user restarts the sub-application next time, so that the heat of the sub-application is more obvious, and the use experience of the sub-application is further improved.
Still referring to fig. 1, on the basis of the above embodiment, the application management system 100 further includes: an application routing center 103; wherein the content of the first and second substances,
the application configuration center 101 is further configured to receive a new sub-application request sent by a user, and update configuration information of an application to which a new sub-application belongs according to the new sub-application request;
the application management center 102 is configured to create the new sub-application according to the configuration information;
the application routing module 103 is configured to update routing information of an application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.
Specifically, the routing information indicates a call relationship between the sub-applications and/or a call relationship between the applications and the sub-applications.
In an optional implementation manner, the creating the new sub-application according to the configuration information includes: registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs; registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs; creating the new sub-application according to the middleware called by the new sub-application; and sequentially loading and executing the middleware to start the new application. On the basis, unified management and maintenance can be carried out on the sub-applications through the sub-application list and the like of the application to which the sub-applications belong according to actual requirements, and meanwhile, the applications, the sub-applications, middleware and the like can be monitored in real time through a preset visualization function and the like. In a preferred embodiment, the newly created new sub-application is comprised of one or more middleware that are invoked in sequence. Therefore, the time and experience required for creating the new sub-application from scratch are greatly reduced by the mode of creating the new sub-application through one or more middleware, and the efficiency of creating the new sub-application is improved.
In an optional implementation manner, the updating, according to the configuration information, the routing information of the application to which the new sub-application belongs includes: determining the routing information of the new sub-application according to the configuration information; and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application. Based on the updated routing information of the application to which the new sub-application belongs, the application and the sub-application can be called.
In an optional embodiment, the middleware called by the new sub-application comprises: a module packer; the application management center is further configured to set the query dependent path of the module packager as a preset integrated query dependent path before the child new application is created.
Module packagers include, but are not limited to: webpack, grunt, Gulp, etc. At present, most of applications need to install the query dependent path used by the module packager during initialization, and the query dependent path is various and takes long time during installation. Therefore, by integrating the query dependent paths which may need to be installed in the current application and modifying the query dependence of the module packager into the preset integrated query dependent path before creating the sub-application, the number of the query dependent paths installed by the application itself is greatly reduced, and meanwhile, when a new sub-application is created, the creation time of the sub-application can be shortened.
In an optional embodiment, the new sub-application request indicates a name of the new sub-application; the application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, notify the user that the name of the new sub-application is wrong. Therefore, the uniqueness of names among different sub-applications can be ensured, and confusion or errors caused by repeated names when the sub-applications are called can be prevented.
On this basis, after the application is started, the application configuration center 101 reads the configuration information of all sub-applications in the directory corresponding to the application, synchronizes the relevant configuration information to the application management center 102 and the application routing center 103 after the initialization of the configuration information is completed, after the application management center 102 receives the configuration information, the current all sub-applications are registered in the sub-application list of the application in the application management center, and simultaneously, according to the middleware configured in all the sub-applications, the middleware called by the new sub-applications is registered, so that the middleware is added to the sub-application list of the application to which the sub-applications belong; and then sequentially loading and executing the middleware according to the configured middleware sequence so as to finish the starting of all the sub-applications.
Still referring to fig. 1, on the basis of the above embodiment, the application configuration center 101 is further configured to receive a request for deleting a sub-application sent by a user, and update configuration information of an application to which the sub-application belongs according to the request for deleting the sub-application; the application management center 102 is configured to delete the sub-application according to the configuration information; the application routing center 103 is configured to update the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.
Based on the embodiment, the application configuration center of the application management system can generate or configure the configuration information of the application, and the unified management and maintenance of one or more sub-applications are realized in the modes of newly building the sub-applications, deleting the sub-applications, updating the sub-applications and the like in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before updating and the like, and the updated middleware is loaded and run when the sub-application is started next time, so that the hot update of the sub-application is realized. In addition, before the new word application is created, the path on which the module packager of the sub-application queries depends is changed into the preset integrated query path of the module packager integrating one or more sub-applications, so that the number of query dependent paths required to be installed when the sub-application is newly created is greatly reduced, the creation time is shortened, and the development efficiency of the application is improved.
Referring to fig. 2, on the basis of the foregoing embodiment, an embodiment of the present invention provides a method for updating a sub-application applied to a management system, where the method specifically includes the following steps:
step S201, receiving a sub-application update request sent by a user, wherein the sub-application belongs to one or more applications, and updating the configuration information of the applications according to the sub-application update request. The sub-application is composed of one or more pieces of middleware called in sequence, and the sub-application updating request indicates the change of the number and the type of the middleware of the sub-application or the change of the middleware instance.
Step S202, updating one or more middleware called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middleware when starting next time.
Referring to fig. 3, on the basis of the foregoing embodiment, an embodiment of the present invention provides a method for creating a new sub-application applied to a management system, where the method specifically includes the following steps:
step S301, receiving a new sub-application request sent by a user, and updating configuration information of an application to which a new sub-application belongs according to the new sub-application request. The new sub-application is composed of one or more invoked middleware, and the configuration information indicates the one or more invoked middleware of the sub-application.
In an optional embodiment, the middleware called by the new sub-application comprises: a module packer; before the new sub-application is created, the query dependent path of the module packer is set as a preset integrated query dependent path, so that the efficiency of creating the new sub-application is improved.
In an alternative embodiment, the new sub-application request indicates the name of the new application; and judging whether the name of the new sub-application exists in the current configuration list, and if so, notifying the user that the name of the new sub-application is wrong.
Step S302, the new sub-application is created according to the configuration information.
Specifically, the new sub-application is registered so as to be added to a sub-application list of the application to which the new sub-application belongs; registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs; creating the new sub-application according to the middleware called by the new sub-application; and sequentially loading and executing the middleware to start the new application.
Step S303, updating the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.
Specifically, determining the routing information of the new sub-application according to the configuration information; and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application.
Referring to fig. 4, on the basis of the foregoing embodiment, an embodiment of the present invention provides another method for creating a new sub-application applied to a management system, where the method specifically includes the following steps:
step S401, receiving a new sub-application request sent by a user, wherein the middleware called by the new sub-application comprises: and a module packer. That is, the new sub-application is composed of one or more middleware, wherein one middleware is a module wrapper of Webpack, grunt, Gulp, and the like. It can be understood that, after receiving a new sub-application request, it should be further determined whether the name of the new sub-application exists in the current configuration list, if so, the user is notified that the name of the new sub-application is incorrect to prevent different sub-applications from having the same name, and if not, the following steps are continuously performed.
Step S402, setting the query dependent path of the module packer as a preset integrated query dependent path.
Step S403, updating the configuration information of the application to which the new sub-application belongs according to the request of the new sub-application.
Step S404, the new sub-application is created according to the configuration information.
Step S405, updating the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.
Referring to fig. 5, on the basis of the foregoing embodiment, a method for deleting a sub-application applied to an application management system is provided, where the method specifically includes the following steps:
step S501, receiving a request for deleting a sub-application sent by a user, and updating the configuration information of the application to which the sub-application belongs according to the request for deleting the sub-application.
Step S502, deleting the sub-application according to the configuration information.
Step S503, updating the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.
Fig. 6 illustrates an exemplary system architecture 600 in which the application management method of embodiments of the present invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, and the like, may be installed on the terminal devices 601, 602, and 603.
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The background management server can analyze and process the received data such as the product information inquiry request and feed back the processing result (the new sub-application name already exists) to the terminal equipment.
It should be noted that the application management method provided by the embodiment of the present invention is generally executed by the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and updating the configuration information of the applications according to the sub-application updating request; and updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time.
According to the technical scheme of the embodiment of the invention, the application configuration center of the application management system can generate or configure the configuration information of the application, and the unified management and maintenance of one or more sub-applications are realized by newly building the sub-applications, deleting the sub-applications, updating the sub-applications and the like in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before updating and the like, and the updated middleware is loaded and run when the sub-application is started next time, so that the hot update of the sub-application is realized. In addition, before the new word application is created, the path on which the module packager of the sub-application queries depends is changed into the preset integrated query path of the module packager integrating one or more sub-applications, so that the number of query dependent paths required to be installed when the sub-application is newly created is greatly reduced, the creation time is shortened, and the development efficiency of the application is improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (16)
1. An application management system, comprising: an application configuration center and an application management center; wherein the content of the first and second substances,
the application configuration center is used for receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and the configuration information of the applications is updated according to the sub-application updating request;
and the application management center is used for updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time.
2. The application management system of claim 1, further comprising: an application routing center; wherein the content of the first and second substances,
the application configuration center is further configured to receive a new sub-application request sent by a user, and update configuration information of an application to which a new sub-application belongs according to the new sub-application request;
the application management center is used for creating the new sub-application according to the configuration information;
and the application routing center is used for updating the routing information of the application to which the new sub-application belongs according to the configuration information so that the new sub-application is called according to the routing information.
3. The application management system of claim 2, wherein the creating the new sub-application according to the configuration information comprises:
registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs;
registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs;
creating the new sub-application according to the middleware called by the new sub-application;
and sequentially loading and executing the middleware to start the new application.
4. The application management system according to claim 2, wherein the updating the routing information of the application to which the new sub-application belongs according to the configuration information includes:
determining the routing information of the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application.
5. The application management system of claim 3,
the middleware called by the new sub-application comprises the following steps: a module packer;
the application management center is further configured to set the query dependent path of the module packager as a preset integrated query dependent path before the child new application is created.
6. The application management system of claim 2,
the new sub-application request indicates the name of the new sub-application;
the application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, notify the user that the name of the new sub-application is wrong.
7. The application management system of claim 2,
the application configuration center is further configured to receive a sub-application deletion request sent by a user, and update configuration information of an application to which the sub-application belongs according to the sub-application deletion request;
the application management center is used for deleting the sub-application according to the configuration information;
and the application routing center is used for updating the routing information of the application to which the sub-application belongs according to the configuration information so that the sub-application cannot be called according to the routing information.
8. An application management method is applied to an application management system and comprises the following steps:
receiving a sub-application updating request sent by a user, wherein the sub-application belongs to one or more applications, and updating the configuration information of the applications according to the sub-application updating request;
and updating one or more middleware called by the sub-application according to the updated configuration information so as to load and execute the updated middleware when the application is started next time.
9. The application management method according to claim 8, further comprising:
receiving a new sub-application request sent by a user, and updating configuration information of an application to which a new sub-application belongs according to the new sub-application request;
creating the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the configuration information so that the new sub-application is called according to the routing information.
10. The application management method according to claim 9, wherein the creating the new sub-application according to the configuration information comprises:
registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs;
registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information so as to add the middleware to a sub-application list of the application to which the new sub-application belongs;
creating the new sub-application according to the middleware called by the new sub-application;
and sequentially loading and executing the middleware to start the new application.
11. The method according to claim 9, wherein the updating the routing information of the application to which the new sub-application belongs according to the configuration information includes:
determining the routing information of the new sub-application according to the configuration information;
and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application.
12. The application management method according to claim 10,
the middleware called by the new sub-application comprises the following steps: a module packer;
and before the new sub-application is created, setting the query dependent path of the module packer as a preset integrated query dependent path.
13. The application management method according to claim 9, further comprising:
the new sub-application request indicates the name of the new application;
and judging whether the name of the new sub-application exists in the current configuration list, and if so, notifying the user that the name of the new sub-application is wrong.
14. The application management method according to claim 9,
receiving a sub-application deleting request sent by a user, and updating the configuration information of the application to which the sub-application belongs according to the sub-application deleting request;
deleting the sub-application according to the configuration information;
and updating the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.
15. An electronic device for application management, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
16. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911200912.2A CN112882741A (en) | 2019-11-29 | 2019-11-29 | Application management system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911200912.2A CN112882741A (en) | 2019-11-29 | 2019-11-29 | Application management system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112882741A true CN112882741A (en) | 2021-06-01 |
Family
ID=76038610
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911200912.2A Pending CN112882741A (en) | 2019-11-29 | 2019-11-29 | Application management system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112882741A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010205153A (en) * | 2009-03-05 | 2010-09-16 | Towa System Inc | Repository management server |
| US20150084892A1 (en) * | 2013-09-24 | 2015-03-26 | Kabushiki Kaisha Toshiba | Control device, display device, control method and program product |
| CN105653331A (en) * | 2015-12-29 | 2016-06-08 | Tcl集团股份有限公司 | Middleware application method and apparatus |
| CN109445832A (en) * | 2018-10-09 | 2019-03-08 | 深圳点猫科技有限公司 | Language carries out the method and electronic equipment of hot update to application program based on programming |
| CN109725909A (en) * | 2018-05-07 | 2019-05-07 | 中国平安人寿保险股份有限公司 | Code file is packaged dispositions method, continuous integrating server and system |
| CN109857427A (en) * | 2018-12-29 | 2019-06-07 | 深圳云天励飞技术有限公司 | Configure update method and Related product |
| CN109885347A (en) * | 2017-12-01 | 2019-06-14 | 财付通支付科技有限公司 | A kind of acquisition methods of configuration data, device and terminal, system, storage medium |
| CN110190997A (en) * | 2019-05-31 | 2019-08-30 | 深圳前海微众银行股份有限公司 | Configuration information obtaining method, device, equipment and computer readable storage medium |
-
2019
- 2019-11-29 CN CN201911200912.2A patent/CN112882741A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010205153A (en) * | 2009-03-05 | 2010-09-16 | Towa System Inc | Repository management server |
| US20150084892A1 (en) * | 2013-09-24 | 2015-03-26 | Kabushiki Kaisha Toshiba | Control device, display device, control method and program product |
| CN105653331A (en) * | 2015-12-29 | 2016-06-08 | Tcl集团股份有限公司 | Middleware application method and apparatus |
| CN109885347A (en) * | 2017-12-01 | 2019-06-14 | 财付通支付科技有限公司 | A kind of acquisition methods of configuration data, device and terminal, system, storage medium |
| CN109725909A (en) * | 2018-05-07 | 2019-05-07 | 中国平安人寿保险股份有限公司 | Code file is packaged dispositions method, continuous integrating server and system |
| CN109445832A (en) * | 2018-10-09 | 2019-03-08 | 深圳点猫科技有限公司 | Language carries out the method and electronic equipment of hot update to application program based on programming |
| CN109857427A (en) * | 2018-12-29 | 2019-06-07 | 深圳云天励飞技术有限公司 | Configure update method and Related product |
| CN110190997A (en) * | 2019-05-31 | 2019-08-30 | 深圳前海微众银行股份有限公司 | Configuration information obtaining method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 林钰杰;皇甫汉聪;: "基于SOA的文档管理系统集成方案研究", 电子设计工程, no. 18, 20 September 2017 (2017-09-20) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113495921B (en) | Routing method and device for database cluster | |
| CN109245908B (en) | Method and device for switching master cluster and slave cluster | |
| CN111427701A (en) | Workflow engine system and business processing method | |
| CN116303608A (en) | Data processing method and device for application service | |
| CN113296828A (en) | Method, server and system for issuing application | |
| CN113541987A (en) | Method and device for updating configuration data | |
| CN111414154A (en) | Method and device for front-end development, electronic equipment and storage medium | |
| CN108536447B (en) | Operation and maintenance management method | |
| CN115442129A (en) | Method, device and system for managing cluster access authority | |
| CN112882741A (en) | Application management system and method | |
| CN111176679B (en) | Application program updating method and device | |
| CN109213815B (en) | Method, device, server terminal and readable medium for controlling execution times | |
| CN112099841A (en) | Method and system for generating configuration file | |
| CN112463616A (en) | Chaos testing method and device for Kubernetes container platform | |
| CN113742617A (en) | Cache updating method and device | |
| CN111984616A (en) | Method, device and system for updating shared file | |
| CN113741951A (en) | Local packaging method and device | |
| CN110262756B (en) | Method and device for caching data | |
| CN111314457B (en) | Method and device for setting virtual private cloud | |
| CN113468053B (en) | Application system testing method and device | |
| CN113495747B (en) | Gray scale release method and device | |
| CN112965747B (en) | Method, apparatus, device and computer readable medium for mining code loopholes | |
| CN113778847A (en) | Test report generation method and device | |
| CN113535167A (en) | Method, device, electronic equipment and computer readable medium for processing list page | |
| CN113326108A (en) | Method and device for managing application service |
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 |