CN109445925B - Application program takeover method, device and system - Google Patents
Application program takeover method, device and system Download PDFInfo
- Publication number
- CN109445925B CN109445925B CN201811334290.8A CN201811334290A CN109445925B CN 109445925 B CN109445925 B CN 109445925B CN 201811334290 A CN201811334290 A CN 201811334290A CN 109445925 B CN109445925 B CN 109445925B
- Authority
- CN
- China
- Prior art keywords
- application program
- request
- service
- takeover
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000013507 mapping Methods 0.000 claims description 130
- 238000012545 processing Methods 0.000 claims description 104
- 238000012508 change request Methods 0.000 claims description 28
- 239000002699 waste material Substances 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004064 recycling Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a device and a system for taking over an application program. Therefore, the agent application program can replace the business application program which is already quitted from running to process the service business, and the service business can still be processed through the agent application program when the business application program is quitted from running. Therefore, the agent application program can take over the service business of the business application program with lower access frequency, so that the business application programs with lower access frequency quit running, and release the system resources occupied by the running business application programs, so that other business application programs can reuse the system resources, and the virtual machine resources are recycled, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a system for taking over an application program.
Background
With the development of the information society, more and more companies move services to the cloud. In the prior art, each company needs to lease at least one virtual machine to a cloud platform company according to its business requirements, so that multiple businesses of the company can run on the virtual machines, and each business can occupy resources corresponding to its requirements.
The access frequencies of all services running on the virtual machine are different, and the access frequencies of some services are higher, so that the services are required to be provided uninterruptedly; some services have a low access frequency and require a long service interval. However, in the prior art, in order to ensure the normal operation of the services, the virtual machine needs to provide sufficient resources for each service.
However, since the traffic with a low access frequency always occupies the resources of the virtual machine, the resources are not continuously used, but the resources occupied by the traffic are used once at intervals of a long time. Therefore, the waste of virtual machine resources is caused, the utilization rate of the virtual machine is low, and the cost of cloud service is increased.
Disclosure of Invention
In order to meet the requirements, the application program takeover method, device and system can achieve recycling of virtual machine resources through takeover of the application program, so that waste of the virtual machine resources is avoided, utilization rate of the virtual machine resources is improved, and cost of cloud services is reduced.
In order to achieve the above purpose, the technical solution provided by the present application is as follows:
the application provides various application program takeover methods, which are applied to business application programs, and the methods comprise the following steps:
sending a takeover request to a proxy application program, so that the proxy application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the proxy application program according to the port change request, and returns a mapping completion message to the proxy application program;
receiving a message sent by the agent application program and used for determining take-over;
receiving a mapping completion message sent by the agent application program; wherein the mapping completion message is a mapping completion message forwarded by the agent application;
and exiting the operation so that the agent application program replaces the business application program to process the service request.
Optionally, before sending the takeover request to the agent application, the method further includes:
registering with the agent application to enable the agent application to obtain registration information of the business application; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
Optionally, before sending the takeover request to the agent application, the method further includes:
judging whether the service application program is in an idle state or not;
the sending of the takeover request to the agent application specifically includes:
and when the business application program is determined to be in an idle state, sending a takeover request to the agent application program.
Optionally, after the operation quitting, the method further includes:
after the service application program is restarted, sending a message forwarding request to the agent application program, so that the agent application program forwards all message requests received during the period of taking over the service application program to the service application program according to the message forwarding request;
receiving all message requests forwarded by the agent application program;
and processing all message requests according to all received message requests.
Optionally, the number of all the message requests is multiple, and the message requests include non-takeover message requests;
the processing all the message requests according to all the received message requests specifically includes:
judging whether a non-takeover message request is related to other message requests except the non-takeover message request in all the message requests according to all the received message requests;
if yes, processing all message requests according to a receiving sequence;
if not, processing the non-takeover message requests, and then processing the rest message requests according to the receiving sequence;
wherein the non-takeover message request is the last message request of all received message requests; the receiving order refers to the order in which the agent application receives all message requests.
The application also provides an application taking-over method which is applied to the proxy application and comprises the following steps:
receiving the takeover request sent by the business application program;
sending the message for determining take-over to the service application program, and sending a port change request to the port mapping module, so that the port mapping module maps an access port of the service application program to the proxy application program according to the port change request, and sends a mapping completion message to the proxy application program;
receiving a mapping completion message sent by the port mapping module;
sending the mapping completion message to the service application program to enable the service application program to quit operation;
the service request is processed in place of the business application.
Optionally, the processing of the service request instead of the service application specifically includes:
processing according to the received service request and the registration information; the service request is a service request which is forwarded by the port mapping module and sent to the business application program by a user; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list comprises proxypable service requests, running codes and types of return messages;
obtaining a processing result according to the type of the return message;
and storing the processing result and the service request so as to obtain the processing result and the service request after the business application program is restarted.
Optionally, the processing according to the received service request and the registration information specifically includes:
determining that the service request is located in the proxiable service request list according to the received service request and the registration information;
and processing the service request according to the running code.
Optionally, the processing according to the received service request and the registration information further includes:
determining that the service request is not located in the proxiable service request list according to the received service request and the registration information;
sending the request for starting the service application program to a scheduling module so that the scheduling module starts the service application program according to the received request for starting the service application program and feeds back a message for determining the start to the agent application program; wherein the request to enable the business application comprises: the start-up information; the start-up information includes: starting the resource requirement and the starting code of the business application program;
sending a message that the current system is busy to the user;
receiving the message which is sent by the scheduling module and used for determining the starting of the service application program;
and sending a port mapping canceling request to the port mapping module so that the port mapping module cancels the port mapping of the agent application program to the service application program according to the port mapping canceling request.
Optionally, the scheduling module starts the service application program according to the received request for starting the service application program, and specifically includes:
the scheduling module acquires a resource requirement for starting the service application program according to the received request for starting the service application program;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting message so as to start the service application program;
when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit operation so as to facilitate the scheduling module to judge whether the current system resource meets the resource requirement; the application to be exited is at least one business application running under the current system.
Optionally, when the current system resource does not meet the resource requirement, the scheduling module instructs the application program to be exited to exit from running, which specifically includes:
the scheduling module obtains a resource difference value between the current system resource and the resource demand;
the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value;
and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
Optionally, the storing the processing result and the service request specifically includes:
and storing the processing result and the service request on at least one storage medium.
The application further provides an application takeover device, which is applied to a business application, and includes:
a first sending unit, configured to send a takeover request to an agent application program, so that the agent application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the agent application program according to the port change request, and returns a mapping completion message to the agent application program;
the first receiving unit is used for receiving the message which is sent by the agent application program and used for determining take-over;
a second receiving unit, configured to receive a mapping completion message sent by the proxy application; wherein the mapping completion message is a mapping completion message forwarded by the agent application;
and the exit unit is used for exiting operation so as to enable the agent application program to replace the business application program to process the service request.
Optionally, the method further includes:
a registration unit, configured to register with the proxy application program, so that the proxy application program obtains registration information of the service application program; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
Optionally, the method further includes:
the first judging unit is used for judging whether the service application program is in an idle state or not;
the first sending unit specifically includes: and when the business application program is determined to be in an idle state, sending a takeover request to the agent application program.
Optionally, the method further includes:
a second sending unit, configured to send a request for forwarding a message to the proxy application after the service application is restarted, so that the proxy application forwards all message requests received during taking over the service application to the service application according to the request for forwarding the message;
a third receiving unit, configured to receive all message requests forwarded by the proxy application;
and the first processing unit is used for processing all the message requests according to all the received message requests.
Optionally, the number of all the message requests is multiple, and the message requests include non-takeover message requests;
the first processing unit specifically includes:
a first judging subunit, configured to judge, according to all received message requests, whether a non-takeover message request is related to a message request other than the non-takeover message request in all the message requests; if yes, operating the first processing subunit; if not, operating a second processing subunit;
the first processing subunit is configured to process all message requests according to a receiving sequence;
the second processing subunit is configured to process the non-takeover message requests first, and then process the remaining message requests according to the receiving sequence;
wherein the non-takeover message request is the last message request of all received message requests; the receiving order refers to the order in which the agent application receives all message requests.
The present application further provides an application takeover device, which is applied to a proxy application, and includes:
a fourth receiving unit, configured to receive the takeover request sent by the service application;
a third sending unit, configured to send the message for determining takeover to the service application program, and send a port change request to the port mapping module, so that the port mapping module maps an access port of the service application program to the proxy application program according to the port change request, and sends a mapping completion message to the proxy application program;
a fifth receiving unit, configured to receive a mapping completion message sent by the port mapping module;
a fourth sending unit, configured to send the mapping completion message to the service application program, so that the service application program exits from running;
and the second processing unit is used for replacing the business application program to process the service request.
Optionally, the second processing unit specifically includes:
a third processing subunit, configured to perform processing according to the received service request and the registration information; the service request is a service request which is forwarded by the port mapping module and sent to the business application program by a user;
the first obtaining subunit is used for obtaining a processing result according to the type of the return message;
and the storage subunit is used for storing the processing result and the service request so as to obtain the processing result and the service request after the service application program is restarted.
Optionally, the third processing subunit specifically includes:
a first determining module, configured to determine that the service request is located in the deputyable service request list according to the received service request and registration information;
and the first processing module is used for processing the service request according to the running code.
Optionally, the third processing subunit further includes:
a second determining module, configured to determine, according to the received service request and the registration information, that the service request is not located in the deputyable service request list;
the first sending module is used for sending the request for starting the service application program to a scheduling module so that the scheduling module starts the service application program according to the received request for starting the service application program and feeds back a message for determining the start to the agent application program; wherein the request to enable the business application comprises: the start-up information; the start-up information includes: starting the resource requirement and the starting code of the business application program;
the second sending module is used for sending a message that the current system is busy to the user;
the first receiving module is used for receiving the message which is sent by the scheduling module and used for determining the starting of the service application program;
a third sending module, configured to send a port mapping cancellation request to the port mapping module, so that the port mapping module cancels the port mapping of the proxy application program to the service application program according to the port mapping cancellation request.
Optionally, the scheduling module starts the service application program according to the received request for starting the service application program, and specifically includes:
the scheduling module acquires a resource requirement for starting the service application program according to the received request for starting the service application program;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting message so as to start the service application program;
when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit operation so as to facilitate the scheduling module to judge whether the current system resource meets the resource requirement; the application to be exited is at least one business application running under the current system.
Optionally, when the current system resource does not meet the resource requirement, the scheduling module instructs the application program to be exited to exit from running, which specifically includes:
the scheduling module obtains a resource difference value between the current system resource and the resource demand;
the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value;
and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
The present application further provides an application takeover system, including: at least one first application program takeover device, a second application program takeover device and a port mapping module;
wherein, the first application program takeover device is the above-mentioned one;
the second application program takeover device is the application program takeover device provided by the above;
the port mapping module is configured to map the access port of the first application program takeover device to the second application program takeover device according to the port change request, and send a mapping completion message to the second application program takeover device; receiving a service request sent by a user to the first application program takeover device, and sending the service request to the second application program takeover device; according to a port mapping cancellation request sent by the second application program takeover device and to the first application program takeover device, cancelling port mapping of the second application program takeover device to the first application program takeover device; and forwarding the service request to the second application program takeover device according to the service request sent by the user to the first application program takeover device.
Optionally, the method further includes: a scheduling module;
the scheduling module is configured to start the first application program takeover device according to the received request for starting the first application program takeover device, and feed back a message for determining the start to the second application program takeover device.
Optionally, the scheduling module is configured to start the first application program takeover device according to the received request for enabling the first application program takeover device, and specifically includes:
acquiring a resource requirement for starting the first application program takeover device according to the received request for starting the first application program takeover device;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting message so as to start the first application program takeover device;
and when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit the operation so as to conveniently judge whether the current system resource meets the resource requirement.
Optionally, when the current system resource does not meet the resource requirement, the scheduling module instructs the application program to be exited to exit from running, which specifically includes:
obtaining a resource difference value between the current system resource and the resource demand;
according to the resource difference value, taking the first application program taking-over device which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted;
and commanding the application program to be quitted to quit operation.
Compared with the prior art, the method has the advantages that:
firstly, a service application program sends a takeover request to a proxy application program; secondly, the agent application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the agent application program according to the port change request, and returns a mapping completion message to the agent application program; then, the agent application program sends the mapping completion message to the service application program; and finally, the business application program quits running so that the agent application program replaces the business application program to process the service request. In the method, the agent application program can replace the business application program which is already quitted from running to process the service business, so that the service business can still be processed through the agent application program when the business application program is quitted from running. Therefore, the agent application program can take over the service business of the business application program with lower access frequency, so that the business application programs with lower access frequency quit running, and release the system resources occupied by the running business application programs, so that other business application programs can reuse the system resources, and the virtual machine resources are recycled, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of an application takeover method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an application takeover apparatus applied to a business application according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an application takeover apparatus applied to a proxy application according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an application takeover system according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to solve the technical problems described in the background section, an embodiment of the present application provides an application takeover system, which includes a service application, an agent application, a port mapping module, and a scheduling module.
The business application program is an application program used for receiving a service request sent by a user and processing according to the service request. For example, the business application may be a database.
And the proxy application program is used for replacing the business application program to process the application program of the user service request when the business application program exits from operation. Furthermore, the proxy application may process the corresponding user service request in place of the at least one business application.
The port mapping module is used for mapping the port of the service application program to the proxy application program when the service application program requests the proxy application program to take over; when the agent application program can not process the user service request and requests the service application program to recover processing the service request, the port mapping module is used for canceling the port mapping of the service application program on the agent application program so as to facilitate the service application program to recover processing the user service request.
And the scheduling module is used for commanding the business application program to exit or start according to the corresponding request.
Based on the application takeover system, an embodiment of the present application further provides an application takeover method, which will be specifically described below with reference to fig. 1.
Referring to fig. 1, this figure is a flowchart of an application takeover method according to an embodiment of the present application.
S101: the business application sends a takeover request to the proxy application.
A takeover request is a request by a business application to request that a proxy application take over its service.
And the proxy application program is used for taking over the service business of the business application program instead of the business application program when the business application program exits from operation.
In order to improve the efficiency of taking over the service related to the service application by the agent application, an embodiment of the present application provides another implementation manner, in which before executing S101, the following steps need to be further executed:
a business application registers with the proxy application such that the proxy application obtains registration information for the business application.
The registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
In addition, in order to further improve the efficiency of the proxy application taking over the service related to the service application, the embodiment of the present application provides another implementation manner, in which before executing S101, the following steps need to be executed:
the business application program judges whether the business application program is in an idle state or not;
if yes, executing S101; if not, the service application program is kept in the running state.
In this way, the agent application program will only replace the business application program in the idle state to perform the service business processing, so as to release the system resources occupied by the business application program in the idle state during the operation, thereby being beneficial to providing the resource utilization rate of the system.
S102: and the agent application program receives the takeover request sent by the service application program.
S103: and the agent application program sends the takeover determining message to the service application program, so that the service application program determines that the agent application program has received the takeover request sent by the agent application program according to the received takeover determining message.
S104: and the proxy application program sends a port change request to the port mapping module, so that the port mapping module maps the access port of the service application program to the proxy application program according to the port change request and returns a mapping completion message to the proxy application program.
The port change request is a request by the proxy application to request the port mapping module to map a port of the business application onto the proxy application.
The mapping complete message is a message that the port mapping module sends to notify the proxy application that the port change has been completed.
It should be noted that, S103 and S104 do not have a sequence, and S103 may be executed first, and then S104 may be executed; or executing S104 first and then executing S103; s103 and S104 may also be performed simultaneously.
S105: the proxy application sends the mapping completion message to the business application.
S106: the service application program receives the mapping completion message.
S107: the business application exits running.
S108: the proxy application performs the processing of the service request in place of the business application.
As an embodiment, S108 may specifically be:
s1081: the user sends a service request to the business application.
S1082: the port mapping module forwards the service request to the proxy application.
S1083: the agent application performs processing based on the received service request and registration information.
As an embodiment, S1083 may specifically be:
s1083 a: based on the received service request and registration information, the broker application confirms that the service request is in the proxiable service request list.
S1083 b: and processing the service request by the agent application program according to the running code.
The running code is located in the deputy service request list, and the running code may correspond to the corresponding service request one by one, so that the deputy application program executes different running codes for different service requests.
S1084: the agent application program obtains a processing result according to the type of the return message;
s1085: and the agent application program stores the processing result and the service request so as to obtain the processing result and the service request after the business application program is restarted.
As an embodiment, in order to ensure the security of storage and further improve the reliability of the system, S1085 may specifically be: and storing the processing result and the service request on at least one storage medium.
For example, the processing result and the service request are stored in a cloud service storage medium and an internal storage medium local to a company, respectively.
The above is a specific embodiment in which the proxy application processes a service request sent by a user instead of the business application.
However, since the proxy application can only process the service request in the deputy service request list in place of the service application, if the proxy application receives a service request that does not belong to the service request recorded in the service request in the deputy service request list, it is necessary that the proxy application should return the processing authority of the service request to the service application in order for the service application to process it.
Therefore, in view of the above situation, an embodiment of the present application further provides another implementation manner, in this implementation manner, when performing S108, if the proxy application confirms that the service request is not located in the brokerable service request list according to the received service request and the registration information, S108 may specifically be:
s108 a: the user sends a service request to the business application.
S108 b: the port mapping module forwards the service request to the proxy application.
S108 c: based on the received service request and registration information, the broker application confirms that the service request is not located in the proxiable service request list.
S108 d: and the agent application program sends a message that the current system is busy to the user.
Since the agent application program cannot take charge of the service request sent by the current user and needs to return the processing authority of the service request to the service application program, in the process, some time is spent, and therefore, the user cannot timely obtain the feedback result of the service request, so that in order to avoid the unintended waiting of the client, the current system can not quickly obtain the feedback result of the service request by sending a message that the current system is busy, and the user is informed to send the service request again after waiting for a period of time.
S108 e: and the agent application program sends the request for starting the service application program to a scheduling module.
Wherein the request to enable the business application comprises: the start-up information; the start-up information includes: resource requirements and a start code for starting the business application.
It should be noted that S108d and S108e do not have a sequence, and S108d may be executed first, and then S108e may be executed; or may be executed first in S108e and then in S108 d; s108d and S108e may also be performed simultaneously.
S108 f: and the scheduling module starts the service application program according to the received request for starting the service application program.
As an embodiment, S108f may specifically be:
s108f 1: and according to the received request for starting the service application program, the scheduling module acquires the resource requirement for starting the service application program.
S108f 2: judging whether the current system resource meets the resource requirement, if so, executing S108f 3; if not, go to S108f 4.
S108f 3: the scheduling module runs the start code of the start message to facilitate starting the business application.
S108f 4: and the scheduling module commands the application program to be quitted to quit running.
Wherein the application to be exited is at least one business application running under the current system.
As an embodiment, S108f4 may specifically be:
s108f4 a: and the scheduling module obtains a resource difference value between the current system resource and the resource demand.
S108f4 b: and the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value.
S108f4 c: and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
S108f 5: return is made to execution S108f 2.
S108 g: and the scheduling module feeds back a message for determining starting to the agent application program.
S108 h: the agent application program receives the message which is sent by the scheduling module and used for determining the starting of the service application program;
s108 i: and the agent application program sends a port mapping canceling request to the port mapping module so that the port mapping module cancels the port mapping of the agent application program to the service application program according to the port mapping canceling request.
S108 j: and after the service application program is restarted, the service application program sends a request for forwarding the message to the agent application program.
S108 k: the agent application program forwards all message requests received in the period of taking over the service application program to the service application program according to the request for forwarding the message;
s108 l: the service application program receives all message requests forwarded by the agent application program;
s108 m: the service application processes all message requests according to all received message requests.
The all-message requests are multiple and include non-takeover message requests. Wherein a non-takeover request is a request that is not on the proxiable service request list and a non-takeover message request is a last message request of all message requests received.
As an embodiment, S108m may specifically be:
judging whether a non-takeover message request is related to other message requests except the non-takeover message request in all the message requests according to all the received message requests;
if yes, processing all message requests according to a receiving sequence;
if not, processing the non-takeover message requests, and then processing the rest message requests according to the receiving sequence.
Wherein, the receiving sequence refers to the sequence of receiving all message requests by the agent application program.
The above is a specific embodiment in which the proxy application returns the right to process the service request to the business application.
In the application takeover method provided by the application, the proxy application can replace the business application which has quitted operation to process the service business, so that the service business can still be processed through the proxy application when the business application quits operation. Therefore, the agent application program can take over the service business of the business application program with lower access frequency, so that the business application programs with lower access frequency quit running, and release the system resources occupied by the running business application programs, so that other business application programs can reuse the system resources, and the virtual machine resources are recycled, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
Based on the method for taking over the application program provided by the foregoing embodiment, an application program taking over device applicable to the business application program is further provided in the embodiment of the present application, and the following explanation and description are provided with reference to fig. 2.
Referring to fig. 2, this figure is a schematic structural diagram of an application takeover apparatus applied to a business application according to an embodiment of the present application.
The application program takeover device provided by the embodiment of the application program is applied to a business application program and comprises the following components:
a first sending unit 201, configured to send a takeover request to an agent application program, so that the agent application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the agent application program according to the port change request, and returns a mapping completion message to the agent application program;
a first receiving unit 202, configured to receive a message sent by the agent application to determine take over;
a second receiving unit 203, configured to receive a mapping completion message sent by the proxy application; wherein the mapping completion message is a mapping completion message forwarded by the agent application;
and the exit unit 204 is configured to exit from running, so that the proxy application performs processing of the service request instead of the service application.
Optionally, the apparatus for taking over the application program further includes:
a registration unit, configured to register with the proxy application program, so that the proxy application program obtains registration information of the service application program; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
Optionally, the apparatus for taking over the application program further includes:
the first judging unit is used for judging whether the service application program is in an idle state or not;
the first sending unit 201 specifically includes: and when the business application program is determined to be in an idle state, sending a takeover request to the agent application program.
Optionally, the apparatus for taking over the application program further includes:
a second sending unit, configured to send a request for forwarding a message to the proxy application after the service application is restarted, so that the proxy application forwards all message requests received during taking over the service application to the service application according to the request for forwarding the message;
a third receiving unit, configured to receive all message requests forwarded by the proxy application;
and the first processing unit is used for processing all the message requests according to all the received message requests.
Optionally, the number of all the message requests is multiple, and the message requests include non-takeover message requests;
the first processing unit specifically includes:
a first judging subunit, configured to judge, according to all received message requests, whether a non-takeover message request is related to a message request other than the non-takeover message request in all the message requests; if yes, operating the first processing subunit; if not, operating a second processing subunit;
the first processing subunit is configured to process all message requests according to a receiving sequence;
the second processing subunit is configured to process the non-takeover message requests first, and then process the remaining message requests according to the receiving sequence;
wherein the non-takeover message request is the last message request of all received message requests; the receiving order refers to the order in which the agent application receives all message requests.
The application program takeover device provided by the embodiment of the application is applied to the application program takeover device and comprises: the device comprises a first sending unit 201, a first receiving unit 202, a second receiving unit 203 and an exiting unit 204, wherein the proxy application can take over the service of the device instead of the application which has exited from running, so that the service can still be processed by the proxy application when the device exits running. Therefore, the agent application program can take over the service business of the application program takeover device with the lower access frequency, so that the application program takeover devices with the lower access frequency quit operation, and release the occupied system resources during the operation, so that other application program takeover devices can reuse the system resources, and the virtual machine resources are recycled, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
Based on the application takeover method provided by the above embodiment, an application takeover device that can be applied to the proxy application is also provided by the embodiment of the present application, and will be explained and explained with reference to fig. 3.
Referring to fig. 3, this figure is a schematic structural diagram of an application takeover apparatus applied to a proxy application according to an embodiment of the present application.
The application program takeover device provided by the embodiment of the application program is applied to the proxy application program and comprises the following steps:
a fourth receiving unit 301, configured to receive the takeover request sent by the service application;
a third sending unit 302, configured to send the message for determining takeover to the service application, and send a port change request to the port mapping module, so that the port mapping module maps an access port of the service application to the proxy application according to the port change request, and sends a mapping completion message to the proxy application;
a fifth receiving unit 303, configured to receive a mapping completion message sent by the port mapping module;
a fourth sending unit 304, configured to send the mapping completion message to the service application program, so that the service application program exits from running;
a second processing unit 305 for performing the processing of the service request in place of the business application.
Optionally, the second processing unit 305 specifically includes:
a third processing subunit, configured to perform processing according to the received service request and the registration information; the service request is a service request which is forwarded by the port mapping module and sent to the business application program by a user;
the first obtaining subunit is used for obtaining a processing result according to the type of the return message;
and the storage subunit is used for storing the processing result so as to obtain the processing result after the service application program is restarted.
Optionally, the third processing subunit specifically includes:
a first determining module, configured to determine that the service request is located in the deputyable service request list according to the received service request and registration information;
and the first processing module is used for processing the service request according to the running code.
Optionally, the third processing subunit further includes:
a second determining module, configured to determine, according to the received service request and the registration information, that the service request is not located in the deputyable service request list;
the first sending module is used for sending the request for starting the service application program to a scheduling module so that the scheduling module starts the service application program according to the received request for starting the service application program and feeds back a message for determining the start to the agent application program; wherein the request to enable the business application comprises: the start-up information; the start-up information includes: starting the resource requirement and the starting code of the business application program;
the second sending module is used for sending a message that the current system is busy to the user;
the first receiving module is used for receiving the message which is sent by the scheduling module and used for determining the starting of the service application program;
a third sending module, configured to send a port mapping cancellation request to the port mapping module, so that the port mapping module cancels the port mapping of the proxy application program to the service application program according to the port mapping cancellation request.
Optionally, the scheduling module starts the service application program according to the received request for starting the service application program, and specifically includes:
the scheduling module acquires a resource requirement for starting the service application program according to the received request for starting the service application program;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting message so as to start the service application program;
when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit operation so as to facilitate the scheduling module to judge whether the current system resource meets the resource requirement; the application to be exited is at least one business application running under the current system.
Optionally, when the current system resource does not meet the resource requirement, the scheduling module instructs the application program to be exited to exit from running, which specifically includes:
the scheduling module obtains a resource difference value between the current system resource and the resource demand;
the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value;
and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
The application program takeover device provided by the embodiment of the application is applied to the application program takeover device and comprises: the fourth receiving unit 301, the third sending unit 302, the fifth receiving unit 303, the fourth sending unit 304, and the second processing unit 305, wherein the application takeover device can process the service instead of the service application that has already exited from operation, which ensures that when the service application exits from operation, the service can still be processed by the application takeover device. Therefore, the application program takeover device can take over the service business of the business application program with the lower access frequency, so that the business application programs with the lower access frequency quit running, and release the system resources occupied by the running business application programs, so that other business application programs can reuse the system resources, and the virtual machine resources are recycled, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
Based on the application takeover method, the application takeover device applicable to the proxy application, and the application takeover device applicable to the business application provided in the embodiments above, an application takeover system is also provided in the embodiments of the present application, which will be explained and explained below with reference to fig. 4.
Referring to fig. 4, this figure is a schematic structural diagram of an application takeover system according to an embodiment of the present application.
The application program takeover system provided by the embodiment of the application includes: at least one first application takeover device 401, a second application takeover device 402, and a port mapping module 403;
the first application takeover device 401 is an application takeover device that can be applied to the first application takeover device according to the foregoing embodiment;
the second application takeover device is an application takeover device that can be applied to the first application takeover device provided in the above embodiment;
the port mapping module is configured to map the access port of the first application program takeover device to the second application program takeover device according to the port change request, and send a mapping completion message to the second application program takeover device; receiving a service request sent by a user to the first application program takeover device, and sending the service request to the second application program takeover device; according to a port mapping cancellation request sent by the second application program takeover device and to the first application program takeover device, cancelling port mapping of the second application program takeover device to the first application program takeover device; and forwarding the service request to the second application program takeover device according to the service request sent by the user to the first application program takeover device.
Optionally, the application taking over system further includes: a scheduling module;
the scheduling module is configured to start the first application program takeover device according to the received request for starting the first application program takeover device, and feed back a message for determining the start to the second application program takeover device.
Optionally, the scheduling module is configured to start the first application program takeover device according to the received request for enabling the first application program takeover device, and specifically includes:
acquiring a resource requirement for starting the first application program takeover device according to the received request for starting the first application program takeover device;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting message so as to start the first application program takeover device;
and when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit the operation so as to conveniently judge whether the current system resource meets the resource requirement.
Optionally, when the current system resource does not meet the resource requirement, the scheduling module instructs the application program to be exited to exit from running, which specifically includes:
obtaining a resource difference value between the current system resource and the resource demand;
according to the resource difference value, taking the first application program taking-over device which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted;
and commanding the application program to be quitted to quit operation.
It should be noted that, the application takeover system provided in the embodiment of the present application includes: the system comprises at least one first application program takeover device 401, a second application program takeover device 402 and a port mapping module 403, wherein in the system, the second application program takeover device can replace a first application program takeover device which is already quitted to operate to process service, so that the service can still be processed by the second application program takeover device when the first application program takeover device is quitted to operate. Therefore, the second application program takeover device can take over the service business of the first application program takeover device with lower access frequency, so that the first application program takeover devices with lower access frequency quit operation, and release occupied system resources during the operation, so that other first application program takeover devices can reuse the system resources, and the repeated utilization of the virtual machine resources is realized, thereby avoiding the waste of the virtual machine resources, improving the utilization rate of the virtual machine resources, and further reducing the cost of the cloud business.
The foregoing is merely a preferred embodiment of the present application and is not intended to limit the present invention in any way. Although the present invention has been described with reference to the preferred embodiments, it is not intended to be limited thereto. Those skilled in the art can make numerous possible variations and modifications to the present teachings, or modify equivalent embodiments to equivalent variations, without departing from the scope of the present teachings, using the methods and techniques disclosed above. Therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention are still within the scope of the protection of the technical solution of the present invention, unless the contents of the technical solution of the present invention are departed.
Claims (27)
1. An application takeover method applied to a business application, the method comprising:
sending a takeover request to a proxy application program, so that the proxy application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the proxy application program according to the port change request, and returns a mapping completion message to the proxy application program;
receiving a message sent by the agent application program and used for determining take-over;
receiving a mapping completion message sent by the agent application program; wherein the mapping completion message is a mapping completion message forwarded by the agent application;
and exiting the operation so that the agent application program replaces the business application program to process the service request.
2. The application takeover method of claim 1 wherein prior to sending a takeover request to the proxy application, further comprising:
registering with the agent application to enable the agent application to obtain registration information of the business application; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
3. The application takeover method of claim 1 wherein prior to sending a takeover request to the proxy application, further comprising:
judging whether the service application program is in an idle state or not;
the sending of the takeover request to the agent application specifically includes:
and when the business application program is determined to be in an idle state, sending a takeover request to the agent application program.
4. The application takeover method of claim 1, wherein after exiting execution, the method further comprises:
after the service application program is restarted, sending a message forwarding request to the agent application program, so that the agent application program forwards all message requests received during the period of taking over the service application program to the service application program according to the message forwarding request;
receiving all message requests forwarded by the agent application program;
and processing all message requests according to all received message requests.
5. The application takeover method of claim 4 wherein the all-message requests are plural and include non-takeover message requests;
the processing all the message requests according to all the received message requests specifically includes:
judging whether a non-takeover message request is related to other message requests except the non-takeover message request in all the message requests according to all the received message requests;
if yes, processing all message requests according to a receiving sequence;
if not, processing the non-takeover message requests, and then processing the rest message requests according to the receiving sequence;
wherein the non-takeover message request is the last message request of all received message requests; the receiving order refers to the order in which the agent application receives all message requests.
6. An application takeover method applied to a proxy application, the method comprising:
receiving a takeover request sent by a service application program;
sending a message for determining take-over to the service application program, and sending a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the proxy application program according to the port change request, and sends a mapping completion message to the proxy application program;
receiving a mapping completion message sent by the port mapping module;
sending the mapping completion message to the service application program to enable the service application program to quit operation;
the service request is processed in place of the business application.
7. The method according to claim 6, wherein the processing of the service request in place of the business application specifically includes:
processing according to the received service request and the registration information; the service request is a service request which is forwarded by the port mapping module and sent to the business application program by a user; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list comprises proxypable service requests, running codes and types of return messages;
obtaining a processing result according to the type of the return message;
and storing the processing result and the service request so as to obtain the processing result and the service request after the business application program is restarted.
8. The method of claim 7, wherein the processing according to the received service request and the registration information specifically comprises:
determining that the service request is located in the proxiable service request list according to the received service request and the registration information;
and processing the service request according to the running code.
9. The method of claim 8, wherein the processing according to the received service request and registration information further comprises:
determining that the service request is not located in the proxiable service request list according to the received service request and the registration information;
sending a request for starting the service application program to a scheduling module, so that the scheduling module starts the service application program according to the received request for starting the service application program and feeds back a message for determining the start to the agent application program; wherein the request to enable the business application comprises: the start-up information; the start-up information includes: starting the resource requirement and the starting code of the business application program;
sending a message that the current system is busy to a user;
receiving a message which is sent by the scheduling module and used for determining the starting of the service application program;
and sending a port mapping canceling request to the port mapping module so that the port mapping module cancels the port mapping of the agent application program to the service application program according to the port mapping canceling request.
10. The method for taking over an application program according to claim 9, wherein the scheduling module starts the service application program according to the received request for starting the service application program, specifically comprising:
the scheduling module acquires a resource requirement for starting the service application program according to the received request for starting the service application program;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting information so as to start the service application program;
when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit operation so as to facilitate the scheduling module to judge whether the current system resource meets the resource requirement; the application to be exited is at least one business application running under the current system.
11. The application takeover method according to claim 10, wherein the step of instructing, by the scheduling module, the application to be exited to exit from running when the current system resource does not meet the resource requirement specifically includes:
the scheduling module obtains a resource difference value between the current system resource and the resource demand;
the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value;
and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
12. The method for application takeover according to any one of claims 7-11, wherein the saving of the processing result and the service request specifically includes:
and storing the processing result and the service request on at least one storage medium.
13. An application takeover device, applied to a business application, includes:
a first sending unit, configured to send a takeover request to an agent application program, so that the agent application program returns a message for determining takeover to the service application program according to the takeover request, and sends a port change request to a port mapping module, so that the port mapping module maps an access port of the service application program to the agent application program according to the port change request, and returns a mapping completion message to the agent application program;
the first receiving unit is used for receiving the message which is sent by the agent application program and used for determining take-over;
a second receiving unit, configured to receive a mapping completion message sent by the proxy application; wherein the mapping completion message is a mapping completion message forwarded by the agent application;
and the exit unit is used for exiting operation so as to enable the agent application program to replace the business application program to process the service request.
14. The application takeover apparatus of claim 13, further comprising:
a registration unit, configured to register with the proxy application program, so that the proxy application program obtains registration information of the service application program; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list includes proxypable service requests, run code, and types of return messages.
15. The application takeover apparatus of claim 13, further comprising:
the first judging unit is used for judging whether the service application program is in an idle state or not;
the first sending unit specifically includes: and when the business application program is determined to be in an idle state, sending a takeover request to the agent application program.
16. The application takeover apparatus of claim 13, further comprising:
a second sending unit, configured to send a request for forwarding a message to the proxy application after the service application is restarted, so that the proxy application forwards all message requests received during taking over the service application to the service application according to the request for forwarding the message;
a third receiving unit, configured to receive all message requests forwarded by the proxy application;
and the first processing unit is used for processing all the message requests according to all the received message requests.
17. The application takeover device of claim 16 wherein the all-message request is plural and comprises a non-takeover message request;
the first processing unit specifically includes:
a first judging subunit, configured to judge, according to all received message requests, whether a non-takeover message request is related to a message request other than the non-takeover message request in all the message requests; if yes, operating the first processing subunit; if not, operating a second processing subunit;
the first processing subunit is configured to process all message requests according to a receiving sequence;
the second processing subunit is configured to process the non-takeover message requests first, and then process the remaining message requests according to the receiving sequence;
wherein the non-takeover message request is the last message request of all received message requests; the receiving order refers to the order in which the agent application receives all message requests.
18. An application takeover apparatus, applied to a proxy application, comprising:
a fourth receiving unit, configured to receive a takeover request sent by a service application;
a third sending unit, configured to send a message for determining takeover to the service application, and send a port change request to a port mapping module, so that the port mapping module maps an access port of the service application to the proxy application according to the port change request, and sends a mapping completion message to the proxy application;
a fifth receiving unit, configured to receive a mapping completion message sent by the port mapping module;
a fourth sending unit, configured to send the mapping completion message to the service application program, so that the service application program exits from running;
and the second processing unit is used for replacing the business application program to process the service request.
19. The apparatus of claim 18, wherein the second processing unit specifically includes:
a third processing subunit, configured to perform processing according to the received service request and the registration information; the service request is a service request which is forwarded by the port mapping module and sent to the business application program by a user; the registration information comprises at least one of an access address and a port number of the business application program, a proxy service request list, starting information and a standard format of feedback information; the proxypable service request list comprises proxypable service requests, running codes and types of return messages;
the first obtaining subunit is used for obtaining a processing result according to the type of the return message;
and the storage subunit is used for storing the processing result and the service request so as to obtain the processing result and the service request after the service application program is restarted.
20. The apparatus according to claim 19, wherein the third processing subunit specifically includes:
a first determining module, configured to determine that the service request is located in the deputyable service request list according to the received service request and registration information;
and the first processing module is used for processing the service request according to the running code.
21. The application takeover apparatus of claim 20, wherein the third processing subunit further comprises:
a second determining module, configured to determine, according to the received service request and the registration information, that the service request is not located in the deputyable service request list;
the first sending module is used for sending a request for starting the service application program to the scheduling module so that the scheduling module starts the service application program according to the received request for starting the service application program and feeds back a message for determining the start to the agent application program; wherein the request to enable the business application comprises: the start-up information; the start-up information includes: starting the resource requirement and the starting code of the business application program;
the second sending module is used for sending a message that the current system is busy to the user;
the first receiving module is used for receiving the message which is sent by the scheduling module and used for determining the starting of the service application program;
a third sending module, configured to send a port mapping cancellation request to the port mapping module, so that the port mapping module cancels the port mapping of the proxy application program to the service application program according to the port mapping cancellation request.
22. The apparatus for taking over an application according to claim 21, wherein the scheduling module starts the service application according to the received request for starting the service application, specifically comprising:
the scheduling module acquires a resource requirement for starting the service application program according to the received request for starting the service application program;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting information so as to start the service application program;
when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit operation so as to facilitate the scheduling module to judge whether the current system resource meets the resource requirement; the application to be exited is at least one business application running under the current system.
23. The apparatus for taking over application program according to claim 22, wherein the scheduling module instructs the application program to be exited to exit from running when the current system resource does not meet the resource requirement, specifically comprising:
the scheduling module obtains a resource difference value between the current system resource and the resource demand;
the scheduling module takes the business application program which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted according to the resource difference value;
and the scheduling module commands the application program to be quitted to quit operation so as to make the application program to be quitted quit operation.
24. An application takeover system comprising: at least one first application program takeover device, a second application program takeover device and a port mapping module;
wherein the first application takeover device is the application takeover device of any one of claims 13-17;
the second application takeover device is the application takeover device of any one of claims 18-23;
the port mapping module is configured to map the access port of the first application program takeover device to the second application program takeover device according to the port change request, and send a mapping completion message to the second application program takeover device; receiving a service request sent by a user to the first application program takeover device, and sending the service request to the second application program takeover device; according to a port mapping cancellation request sent by the second application program takeover device and to the first application program takeover device, cancelling port mapping of the second application program takeover device to the first application program takeover device; and forwarding the service request to the second application program takeover device according to the service request sent by the user to the first application program takeover device.
25. The application takeover system of claim 24 further comprising: a scheduling module;
the scheduling module is configured to start the first application program takeover device according to the received request for starting the first application program takeover device, and feed back a message for determining the start to the second application program takeover device.
26. The system according to claim 25, wherein the scheduling module is configured to start the first application takeover device according to the received request for enabling the first application takeover device, and specifically includes:
acquiring a resource requirement for starting the first application program takeover device according to the received request for starting the first application program takeover device;
when the current system resource meets the resource requirement, the scheduling module runs the starting code of the starting information so as to start the first application program takeover device;
and when the current system resource does not meet the resource requirement, the scheduling module commands the application program to be quitted to quit the operation so as to conveniently judge whether the current system resource meets the resource requirement.
27. The system for taking over the application program according to claim 26, wherein the scheduling module instructs the application program to be exited to exit from running when the current system resource does not meet the resource requirement, specifically comprising:
obtaining a resource difference value between the current system resource and the resource demand;
according to the resource difference value, taking the first application program taking-over device which is in an idle state and has the resource occupation larger than the resource difference value as the application program to be quitted;
and commanding the application program to be quitted to quit operation.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811334290.8A CN109445925B (en) | 2018-11-09 | 2018-11-09 | Application program takeover method, device and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811334290.8A CN109445925B (en) | 2018-11-09 | 2018-11-09 | Application program takeover method, device and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN109445925A CN109445925A (en) | 2019-03-08 |
CN109445925B true CN109445925B (en) | 2022-02-18 |
Family
ID=65552467
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201811334290.8A Active CN109445925B (en) | 2018-11-09 | 2018-11-09 | Application program takeover method, device and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN109445925B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113778998A (en) * | 2021-09-28 | 2021-12-10 | 北京安华金和科技有限公司 | Database proxy fault prevention processing method and device |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1945533A (en) * | 2005-10-08 | 2007-04-11 | 腾讯科技(深圳)有限公司 | Method and device for starting sub module in application program |
CN102916995A (en) * | 2011-08-05 | 2013-02-06 | 南京中兴新软件有限责任公司 | Application hosting method and system |
CN103201724A (en) * | 2010-07-30 | 2013-07-10 | 赛门铁克公司 | Providing application high availability in highly-available virtual machine environments |
CN103607296A (en) * | 2013-11-01 | 2014-02-26 | 杭州华三通信技术有限公司 | Virtual machine fault processing method and equipment thereof |
CN103843418A (en) * | 2013-10-29 | 2014-06-04 | 华为终端有限公司 | Method of service agent, modem and terminal |
WO2015167592A1 (en) * | 2014-04-30 | 2015-11-05 | Hewlett-Packard Development Company, L.P. | Using a single deployer agent to deploy a plurality of programs on a server |
CN105072185A (en) * | 2015-08-12 | 2015-11-18 | 上海斐讯数据通信技术有限公司 | TR069 (Technical Report 069) remote monitoring method and system, and communication equipment |
WO2016114762A1 (en) * | 2015-01-13 | 2016-07-21 | Nokia Solutions And Networks Oy | Isolated e-utran operation |
CN105897869A (en) * | 2016-03-29 | 2016-08-24 | 杭州数梦工场科技有限公司 | APP sleep management method and apparatus |
CN106855823A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | The method and device of equipment room task adapter |
CN107707398A (en) * | 2017-09-29 | 2018-02-16 | 郑州云海信息技术有限公司 | The method and apparatus that physical host is managed in cloud computing system |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1715655A1 (en) * | 2005-04-18 | 2006-10-25 | Research In Motion Limited | System and method for data and message optimisation in wireless communications |
CN101867586B (en) * | 2010-06-29 | 2014-08-13 | 中兴通讯股份有限公司 | Method and system for realizing cross network segment signaling interworking of videoconference system |
US9721092B2 (en) * | 2014-03-27 | 2017-08-01 | International Busines Machines Corporation | Monitoring an application in a process virtual machine |
CN104731635B (en) * | 2014-12-17 | 2018-10-19 | 华为技术有限公司 | A kind of virtual machine access control method and virtual machine access control system |
US10122815B1 (en) * | 2016-08-05 | 2018-11-06 | Sprint Communications Company L.P. | Dynamic class mapping in messaging middleware |
-
2018
- 2018-11-09 CN CN201811334290.8A patent/CN109445925B/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1945533A (en) * | 2005-10-08 | 2007-04-11 | 腾讯科技(深圳)有限公司 | Method and device for starting sub module in application program |
CN103201724A (en) * | 2010-07-30 | 2013-07-10 | 赛门铁克公司 | Providing application high availability in highly-available virtual machine environments |
CN102916995A (en) * | 2011-08-05 | 2013-02-06 | 南京中兴新软件有限责任公司 | Application hosting method and system |
CN103843418A (en) * | 2013-10-29 | 2014-06-04 | 华为终端有限公司 | Method of service agent, modem and terminal |
CN103607296A (en) * | 2013-11-01 | 2014-02-26 | 杭州华三通信技术有限公司 | Virtual machine fault processing method and equipment thereof |
WO2015167592A1 (en) * | 2014-04-30 | 2015-11-05 | Hewlett-Packard Development Company, L.P. | Using a single deployer agent to deploy a plurality of programs on a server |
WO2016114762A1 (en) * | 2015-01-13 | 2016-07-21 | Nokia Solutions And Networks Oy | Isolated e-utran operation |
CN105072185A (en) * | 2015-08-12 | 2015-11-18 | 上海斐讯数据通信技术有限公司 | TR069 (Technical Report 069) remote monitoring method and system, and communication equipment |
CN106855823A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | The method and device of equipment room task adapter |
CN105897869A (en) * | 2016-03-29 | 2016-08-24 | 杭州数梦工场科技有限公司 | APP sleep management method and apparatus |
CN107707398A (en) * | 2017-09-29 | 2018-02-16 | 郑州云海信息技术有限公司 | The method and apparatus that physical host is managed in cloud computing system |
Non-Patent Citations (3)
Title |
---|
Exploration of application migration to cloud environment;Ahmed Kandil 等;《2016 6th International Conference - Cloud System and Big Data Engineering (Confluence)》;20161231;第109-114页 * |
云代理的移动消息推送服务;承骁 等;《小型微型计算机系统》;20160831;第37卷(第8期);第1661-1666页 * |
虚拟化环境中计算效能优化研究;陈华才;《万方数据库-学位论文库》;20120604;第1-116页 * |
Also Published As
Publication number | Publication date |
---|---|
CN109445925A (en) | 2019-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9864595B2 (en) | Software updating method, system, and device | |
CN109150572B (en) | Method, device and computer readable storage medium for realizing alarm association | |
CN101572710B (en) | Interprocess communication method and system | |
CN101217678B (en) | System upgrade method, system and device | |
US9600318B2 (en) | Method and system for closing application programs of an application system | |
CN106919452B (en) | Multi-core heterogeneous system and management method of hardware resources thereof | |
CN109062601A (en) | MES system client-side program update method, device, equipment and medium | |
CN111245634B (en) | Virtualization management method and device | |
CN111597061A (en) | Method and device for remote procedure call of client or server | |
CN114138500B (en) | Resource scheduling system and method | |
CN109858772A (en) | A kind of processing method of work order, device and system | |
CN109445925B (en) | Application program takeover method, device and system | |
CN106572137A (en) | Distributed service resource management method and apparatus | |
CN113992630B (en) | Network resource conflict processing method, device, equipment and storage medium | |
CN109787789B (en) | Compatibility management method, device and equipment for software upgrading and storage medium | |
CN111835809B (en) | Work order message distribution method, work order message distribution device, server and storage medium | |
CN114143905B (en) | Session establishing method, communication system, electronic device and storage medium | |
CN114338584B (en) | Message withdraw method and message transmission system | |
CN116743762A (en) | Service registration cluster flow switching method, flow switching device and storage medium | |
CN101247401B (en) | State machine processing method and device based on message driving | |
CN110266747B (en) | Method and device for switching machine room of service request | |
CN114143730A (en) | Signaling processing method, communication system, electronic device, and storage medium | |
CN113852669A (en) | Efficient container cluster deployment method suitable for various network environments | |
JP6003417B2 (en) | Data conversion apparatus and data conversion program | |
CN113515458A (en) | Method and system for reducing resource consumption of test environment based on Envoy plug-in |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |