CN106708547B - Service plug-in management method and system - Google Patents
Service plug-in management method and system Download PDFInfo
- Publication number
- CN106708547B CN106708547B CN201510778675.3A CN201510778675A CN106708547B CN 106708547 B CN106708547 B CN 106708547B CN 201510778675 A CN201510778675 A CN 201510778675A CN 106708547 B CN106708547 B CN 106708547B
- Authority
- CN
- China
- Prior art keywords
- service
- object instance
- plug
- service object
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a service plug-in management method and a service plug-in management system. The service plug-in management method comprises the following steps: s1, monitoring the configuration file of the service plug-in and the update state of the service plug-in implementation file; s2, when the configuration file and/or the implementation file of the service plug-in are found to be updated, loading the configuration file information and the implementation file information of the service plug-in needing to be updated to create a new service object instance and add the new service object instance into the service object instance pool; s3, updating the service plug-in information in the service registry by the newly created service object instance; s4, when the original service object instance of the updated service plug-in the service object instance pool is idle, deleting the original service object instance from the service object instance pool. The service plug-in management method and the system can realize automatic and seamless update of the service plug-in, and can not interrupt the execution of the existing service.
Description
Technical Field
The present invention relates to computer technologies, and in particular, to a service plug-in management method and system.
Background
An application service container is a collective tool used to manage component behaviors, manage the behaviors of all components in the container, interact with the external environment, the life cycle of the components, the cooperative dependencies between the components, and the like. In the existing application service container management system, service components for container management are generally managed in a plug-in mode. In the management process of the plug-ins, dynamic management of the service plug-ins is supported, and management operations such as loading and unloading of the plug-ins are included.
For an application system with high requirements on real-time performance, availability and maintainability, the application system has high requirements on management of service components of a container, but in the existing container management system, a system-loaded plugin generally configures plugin list information loaded by the system through a plugin configuration file, and when a plugin needs to be added or deleted or an original plugin version needs to be modified, the problem is solved by manually modifying the plugin configuration file and restarting the system or triggering an instruction, and the dynamic management process of the plugin generally has the following problems:
1. semi-automated (manual intervention): the conventional dynamic plug-in management process generally modifies a plug-in configuration file or a plug-in implementation file through a manual background or a maintenance management interface, and then completes the dynamic update process of the plug-in a manner of restarting an application service or restarting a maintenance management interface through the manual background, so that complete automatic recording and updating cannot be realized.
2. Service interruption: in the conventional dynamic plug-in management process, the conventional service is interrupted in the dynamic update process of the plug-in by manually restarting an application service in a background or restarting a maintenance management interface, and the normal service cannot be provided in the update process, so that the service cannot be used temporarily; even in a multi-machine cluster state, the interruption of the currently processed service is also caused.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a service plug-in management method and system capable of automatically and seamlessly updating a service plug-in, in view of the above-mentioned defects in the prior art.
In order to solve the technical problem, the present invention provides a service plug-in management method in a first aspect, including the following steps:
s1, monitoring the configuration file of the service plug-in and the update state of the service plug-in implementation file;
s2, when the configuration file and/or the implementation file of the service plug-in are found to be updated, loading the configuration file information and the implementation file information of the service plug-in needing to be updated to create a new service object instance and add the new service object instance into the service object instance pool;
s3, updating the service plug-in information in the service registry by the newly created service object instance;
s4, when the original service object instance of the updated service plug-in the service object instance pool is idle, deleting the original service object instance from the service object instance pool.
In an embodiment according to the first aspect of the present invention, the step S1 further includes: and checking whether the service plug-in is updated according to the service plug-in configuration file and the last updating time of the service plug-in implementation file in real time or periodically.
In an embodiment according to the first aspect of the present invention, the step S2 further includes:
s21, comparing and checking the updated service plug-in configuration file and the service plug-in realization file information with the original file information, and acquiring a service plug-in list needing to be updated;
s22, according to the service plug-in list needing to be updated, loading corresponding service plug-in configuration file information and implementation file information to create a specified number of service object instances;
and S23, adding the newly created service object instance to the corresponding service plug-in name in the service object instance pool.
In an embodiment according to the first aspect of the present invention, the step S4 further includes:
s41, marking the original service object instance of the updated service plug-in the service object instance pool as an invalid state;
and S42, deleting the service object instances which are idle and in the failure state in the service object instance pool at regular time.
In an embodiment according to the first aspect of the invention, the method further comprises:
and inquiring a service registry based on the service call request to obtain service object instance information corresponding to the specified service plug-in, acquiring a corresponding service object instance from a service object instance pool to execute service call, marking the service object instance in the service object instance pool as an occupied state, and marking the service object instance in an idle state after the service call is completed.
In order to solve the technical problem, a second aspect of the present invention provides a service plug-in management system, including:
the service object instance pool is used for storing service object instances of all the service plug-ins currently running;
the service registry module is used for storing a service registry for maintaining information of all currently operated service plug-ins, wherein the information at least comprises service names of the service plug-ins and corresponding service object instance information;
and the service management engine is used for monitoring the update state of the service plug-in configuration file and the service plug-in implementation file, loading configuration file information and implementation file information of the service plug-in to be updated to create a new service object instance to be added into the service object instance pool when the service plug-in configuration file and/or the service plug-in implementation file are found to be updated, updating the service plug-in information in the service registry by the newly created service object instance, and deleting the original service object instance from the service object instance pool when the original service object instance of the updated service plug-in the service object instance pool is idle.
In an embodiment according to the second aspect of the present invention, the service management engine further checks whether it has an update according to the service plug-in configuration file and the last update time of the service plug-in implementation file in real time or periodically.
In an embodiment of the second aspect of the present invention, the creating, by the service management engine, a new service object instance to be added to the service object instance pool when the service plug-in configuration file and/or the service plug-in implementation file are/is updated further includes: the service management engine compares and checks the difference between the updated service plug-in configuration file and the service plug-in implementation file information with the original file information to obtain a service plug-in list needing to be updated, loads corresponding service plug-in configuration file information and implementation file information according to the service plug-in list needing to be updated to create a specified number of service object instances, and adds the created service object instances to the corresponding service plug-in names in the service object instance pool.
In an embodiment of the second aspect of the present invention, the deleting, by the service management engine, the original service object instance from the service object instance pool when the original service object instance of the updated service plug-in the service object instance pool is idle further includes: and the service management engine marks the original service object instance of the updated service plug-in the service object instance pool as a failure state, and deletes the idle service object instance in the service object instance pool and in the failure state at regular time.
In one embodiment according to the second aspect of the invention, the system further comprises:
the service interface module is used for inquiring the service registry based on the service calling request to obtain the service object instance information corresponding to the specified service plug-in and obtaining the corresponding service object instance from the service object instance pool to execute the service calling;
and the service object instance pool marks the service object instance as an occupied state when the service interface module calls the corresponding service object instance, and marks the service object instance as an idle state after the service calling is finished.
The service plug-in management method and the system can fully automatically load, update and unload the service plug-ins by configuring the files of the service plug-ins and monitoring the update state of the files; in the updating process of the service plug-in, the seamless switching of the service is ensured by the simultaneous existence of the new service object instance and the old service object instance and the state control mode, the original service object instance is released and deleted after being called, and all calling after the service plug-in is updated can not use the original service object instance.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
FIG. 1 is a flow diagram of a service plug-in management method of one embodiment of the invention;
FIG. 2 is a logical block diagram of a service plug-in management system according to one embodiment of the invention;
FIG. 3 is a diagram illustrating an interaction process of a service plug-in management system initiating loading of a service plug-in one embodiment of the invention;
FIG. 4 is a diagram illustrating the interaction process of the service plug-in management system to update service plug-ins in one embodiment of the present invention;
FIG. 5 is a diagram illustrating an interaction process of a service plug-in management system executing a service call in an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
FIG. 1 shows a flow diagram of a service plug-in management method 100 according to one embodiment of the invention. As shown in fig. 1, the service plug-in management method 100 includes the following steps:
in step S110, the service plug-in configuration file and the update state of the service plug-in implementation file are monitored. The application service container loads and creates the corresponding service plug-in by reading the service plug-in file. The service plug-in file comprises a service plug-in configuration file and a service plug-in implementation file, wherein the configuration file configures plug-in configuration information loaded by the application service container, and the configuration information comprises the name, the number of instances, the entry class name, the position and the name of the implementation file and the like of the service plug-in; implementation files, i.e. jar packages of Java, for example. In step S110, whether the service plug-in update information exists can be checked by monitoring the update status of the service plug-in configuration file and the implementation file in real time or periodically, for example, whether the service plug-in update information exists can be checked according to the last update time of the service plug-in configuration file and the implementation file.
Subsequently, in step S120, when the service plug-in configuration file and/or the service plug-in implementation file are found to be updated, the configuration file information and the implementation file information of the service plug-in that needs to be updated are loaded to create a new service object instance and add the new service object instance to the service object instance pool. Specifically, in step S120, the difference between the updated service plug-in configuration file and the service plug-in implementation file information and the original file information is checked by comparison, a service plug-in list needing to be updated is obtained, then the corresponding service plug-in configuration file information and implementation file information are loaded according to the service plug-in list needing to be updated to create a specified number of service object instances, and the newly created service object instances are added to the corresponding service names in the service object instance pool.
In step S130, the service plug-in information in the service registry is updated with the newly created service object instance, i.e. the newly created service object instance information is added to the service registry.
In step S140, when the original service object instance of the updated service plug-in the service object instance pool is idle, the original service object instance is deleted from the service object instance pool. The service plug-in management method 100 of the present invention allows new and old service object instances to exist simultaneously, ensures that all service calls use the new service object instances by maintaining the service registry and state control, and ensures that the original service object instances are called and deleted after finishing the call. Specifically, in step S140, the original service object instance of the updated service plug-in the service object instance pool may be marked as a failure state, and when the service object instance marked as the failure state is released and in a free state, the service plug-in may be deleted from the service object instance pool, so that the existing service may not be interrupted due to the update of the plug-in.
Based on the service plug-in management method 100, the invention can automatically monitor the update state of the service plug-in and dynamically and seamlessly update the service plug-in to the application service container.
Based on the service plug-in management method introduced above, the invention also provides a service plug-in management system. FIG. 2 illustrates a logical block diagram of a service plug-in management system 200 according to one embodiment of the invention. As shown in fig. 2, the service plug-in management system 200 is mainly composed of a service object instance pool 210, a service registry module 220, a service management engine 230, and a service interface module 240. The service object instance pool 210 is used to store the service object instances 211 of all the service plug-ins currently running. The service registry module 220 is configured to store a service registry for maintaining information of all currently running service plugins, where the information of the service plugins at least includes service names of the service plugins and corresponding service object instance information, and may further include state information (including physical states and running states) of all the service plugins. The service management engine 230 is configured to monitor an update status of a service plug-in file (i.e., a service plug-in configuration file and a service plug-in implementation file) in real time or periodically, and when the service plug-in configuration file and/or the service plug-in implementation file is found to be updated, load configuration file information and implementation file information of a service plug-in to be updated to create a new service object instance, add the new service object instance to the service object instance pool 210, and update the service plug-in information in the service registry module 220 with the newly created service object instance. Service management engine 230 also deletes an original service object instance of the updated service plug-in from service object instance pool 210 when the original service object instance is free in service object instance pool 210. Specifically, after adding a new service object instance to the service object instance pool 210, the service management engine 220 may mark the original service object instance of the service plug-in the service object instance pool as a failure state, and periodically delete the service object instance that is idle and in the failure state in the service object instance pool 210. The service interface module 240 is a unified entry for all service calls. The service interface module 240 is configured to query the service registry in the service registry module 220 based on the service call request to obtain service object instance information corresponding to the specified service plug-in, and then obtain a corresponding service object instance from the service object instance pool 210 to execute the service call. The service object instance pool 210 marks the service object instance 211 as an occupied state when the service interface module 240 calls the corresponding service object instance 211, and marks the service object instance 211 as an idle state after the service interface module 240 completes the service call, so that the service management engine 230 maintains the service object instance in the service object instance pool 210. For example, as previously described, service management engine 230 may periodically delete service object instances in service object instance pool 210 that are free and in a failed state.
FIG. 3 is a diagram illustrating an interaction process of the service plug-in management system to start loading the service plug-in according to an embodiment of the present invention. As shown in fig. 3, when the system is started, the service management engine loads the service plug-in configuration file and the service plug-in implementation file, and performs the following processing for each service plug-in:
in step S301, the service management engine loads configuration file information and implementation file information of the service plug-in, where the information includes, for example, a name of the service plug-in, an entry implementation class, a location of the implementation file, a number of object instances, and the like.
Step S302, the service management engine creates a specified number of service object instances according to the number of the entry implementation classes and the object instances in the service plug-in configuration information.
Step S303, the service management engine adds the created service object instance to the service object instance pool. The service management pool can store the service object instances in a classified manner according to the service names, and the service management engine adds the created service object instances to the service names appointed in the service object instance pool.
Step S304, the service management engine updates the service registry and adds the service object instance information of the service plug-in.
And the dynamic updating process of the service plug-in comprises the processes of deleting, adding and updating the service plug-in. The service plug-in management system of the invention realizes the update state of the file to check the update type of the service plug-in according to the configuration file of the service plug-in, and dynamically updates the service plug-in according to different types. FIG. 4 is a diagram illustrating an interaction process of the service plug-in management system to update the service plug-in according to an embodiment of the present invention. As shown in fig. 4, the update process of the service plug-in is as follows:
in step S401, the service management engine monitors the update status of the service plug-in configuration file and the implementation file in real time or periodically, for example, whether the file is updated or not can be checked according to the last update time of the file.
In step S402, the service management engine acquires updated file information after checking that there is an update.
Step S403, the service management engine compares and checks the updated service plug-in configuration file and the difference between the service plug-in implementation file information and the original file information, and obtains a list of service plug-ins that need to be updated.
Step S404, the service management engine loads corresponding service plug-in configuration file information and implementation file information according to the service plug-in list needing to be updated.
Step S405, the service management engine creates a specified number of new service object instances according to the service configuration entry implementation class and the number of the object instances.
In step S406, the service management engine adds the newly created service object instance to the service name specified in the service object instance pool.
Step S407, the service management engine updates the service registry and adds the new service object instance information of the service plug-in.
Step S408, the service management engine marks the original service object instance of the service plug-in the service object instance pool as an invalid state.
Step S409, the service management engine deletes the service object instance that is idle and in the failure state in the service object instance pool at regular time.
Based on the service plug-in management method and system introduced by the present invention, the service plug-in calling process in the application service container is as described in fig. 5, and includes:
step S501, the service interface receives the service calling request, and searches the service object instance information of the service plug-in appointed to be called through the service registry.
Step S502, the service interface obtains the idle and effective service object instance in the specified service from the service object instance pool.
In step S503, the service object instance pool marks the service object instance to be called by the service interface as an occupied state, so as to ensure that one service object instance can only be called by mutual exclusion.
Step S504, the service object instance pool returns the service game instance to be called by the service interface to the service interface.
Step S505, the service interface calls the acquired service object instance to execute the service logic according to the parameter and calling specification of the request calling, and the service calling is completed.
Step S506, after completing the service call, the service interface initiates an occupation release request of the service object instance to the service object instance pool to release the occupation of the service object instance.
Step S507, the service object instance pool marks the corresponding service object instance as an idle state.
The service plug-in management method and the system can fully automatically load, update and unload the service plug-ins by configuring the files of the service plug-ins and monitoring the update state of the files; in the updating process of the service plug-in, the new service object instance and the old service object instance are allowed to exist at the same time, the seamless switching of the service is ensured through state control, the original service object instance is released and deleted after being called, the execution of the service is not influenced, and all calling after the service plug-in is updated does not use the original service object instance.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (10)
1. A service plug-in management method is characterized by comprising the following steps:
s1, monitoring the configuration file of the service plug-in and the update state of the service plug-in implementation file;
s2, when the configuration file and/or the implementation file of the service plug-in are found to be updated, loading the configuration file information and the implementation file information of the service plug-in needing to be updated to create a new service object instance and add the new service object instance into the service object instance pool;
s3, updating the service plug-in information in the service registry by the newly created service object instance;
s4, marking the original service object instance of the updated service plug-in the service object instance pool as a failure state, and deleting the original service object instance from the service object instance pool when the service object instance marked as the failure state is released and is in an idle state.
2. The service plug-in management method according to claim 1, wherein the step S1 further comprises: and checking whether the service plug-in is updated according to the service plug-in configuration file and the last updating time of the service plug-in implementation file in real time or periodically.
3. The service plug-in management method according to claim 1, wherein the step S2 further comprises:
s21, comparing and checking the updated service plug-in configuration file and the service plug-in realization file information with the original file information, and acquiring a service plug-in list needing to be updated;
s22, according to the service plug-in list needing to be updated, loading corresponding service plug-in configuration file information and implementation file information to create a specified number of service object instances;
and S23, adding the newly created service object instance to the corresponding service plug-in name in the service object instance pool.
4. The service plug-in management method according to claim 1, wherein the step S4 further comprises:
s41, marking the original service object instance of the updated service plug-in the service object instance pool as an invalid state;
and S42, deleting the service object instances which are idle and in the failure state in the service object instance pool at regular time.
5. The service plug-in management method according to claim 1, wherein the method further comprises:
and inquiring a service registry based on the service call request to obtain service object instance information corresponding to the specified service plug-in, acquiring a corresponding service object instance from a service object instance pool to execute service call, marking the service object instance in the service object instance pool as an occupied state, and marking the service object instance in an idle state after the service call is completed.
6. A service plug-in management system, comprising:
the service object instance pool is used for storing service object instances of all the service plug-ins currently running;
the service registry module is used for storing a service registry for maintaining information of all currently operated service plug-ins, wherein the information at least comprises service names of the service plug-ins and corresponding service object instance information;
the service management engine is used for monitoring the update state of the service plug-in configuration file and the service plug-in implementation file, loading configuration file information and implementation file information of the service plug-in needing to be updated to create a new service object instance to be added into the service object instance pool when the service plug-in configuration file and/or the service plug-in implementation file are found to be updated, updating the service plug-in information in the service registry with the newly created service object instance, marking the original service object instance of the updated service plug-in the service object instance pool as a failure state, and deleting the original service object instance from the service object instance pool when the service object instance marked as the failure state is released to be in an idle state.
7. The service plugin management system according to claim 6, wherein the service management engine further checks whether the service plugin is updated according to the last update time of the service plugin configuration file and the service plugin implementation file in real time or periodically.
8. The service plugin management system of claim 6, wherein the service management engine, upon discovering an update to a service plugin configuration file and/or a service plugin implementation file, creates a new service object instance to join a service object instance pool further comprises: the service management engine compares and checks the difference between the updated service plug-in configuration file and the service plug-in implementation file information with the original file information to obtain a service plug-in list needing to be updated, loads corresponding service plug-in configuration file information and implementation file information according to the service plug-in list needing to be updated to create a specified number of service object instances, and adds the created service object instances to the corresponding service plug-in names in the service object instance pool.
9. The service plug-in management system according to claim 6, wherein the service management engine deletes the original service object instance from the service object instance pool when the original service object instance of the updated service plug-in the service object instance pool is idle, further comprising: and the service management engine marks the original service object instance of the updated service plug-in the service object instance pool as a failure state, and deletes the idle service object instance in the service object instance pool and in the failure state at regular time.
10. The service plugin management system of claim 6, further comprising:
the service interface module is used for inquiring the service registry based on the service calling request to obtain the service object instance information corresponding to the specified service plug-in and obtaining the corresponding service object instance from the service object instance pool to execute the service calling;
and the service object instance pool marks the service object instance as an occupied state when the service interface module calls the corresponding service object instance, and marks the service object instance as an idle state after the service calling is finished.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510778675.3A CN106708547B (en) | 2015-11-12 | 2015-11-12 | Service plug-in management method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510778675.3A CN106708547B (en) | 2015-11-12 | 2015-11-12 | Service plug-in management method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106708547A CN106708547A (en) | 2017-05-24 |
CN106708547B true CN106708547B (en) | 2020-10-27 |
Family
ID=58931271
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201510778675.3A Active CN106708547B (en) | 2015-11-12 | 2015-11-12 | Service plug-in management method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106708547B (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109992374A (en) * | 2017-12-29 | 2019-07-09 | 中移互联网有限公司 | A kind of management method of application example, device and computer readable storage medium |
CN110730197B (en) * | 2018-07-17 | 2023-08-08 | 北京京东尚科信息技术有限公司 | Service discovery method and system |
CN111381856A (en) * | 2020-03-26 | 2020-07-07 | 北京东方国信科技股份有限公司 | Method and device for hot updating of Java software |
CN111736922B (en) * | 2020-07-23 | 2020-11-13 | 平安国际智慧城市科技股份有限公司 | Plug-in calling method and device, electronic equipment and storage medium |
CN115599355B (en) * | 2022-12-12 | 2023-03-14 | 卓望数码技术(深圳)有限公司 | Object-oriented big data processing method |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090150898A1 (en) * | 2007-12-11 | 2009-06-11 | Electronics And Telecommunications Research Institute | Multithreading framework supporting dynamic load balancing and multithread processing method using the same |
CN102591659A (en) * | 2011-12-28 | 2012-07-18 | 中标软件有限公司 | Implementation method for widget on main interface of mobile terminal and management method for widget |
CN102819438A (en) * | 2011-06-08 | 2012-12-12 | 金蝶软件(中国)有限公司 | Hot-load method and device and information system |
CN102843342A (en) * | 2011-06-22 | 2012-12-26 | 华为软件技术有限公司 | Method and system for dynamically upgrading resource |
CN103197952A (en) * | 2012-01-09 | 2013-07-10 | 华为技术有限公司 | Management system and method aiming at maintenance and deployment of application system based on cloud infrastructure |
CN103218220A (en) * | 2013-02-25 | 2013-07-24 | 上海谐宇网络科技有限公司 | Dynamic pluggable component based-Internet of things middleware system |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7398381B2 (en) * | 2004-12-10 | 2008-07-08 | Intel Corporation | Utilizing paging to support dynamic code updates |
CN100492290C (en) * | 2007-11-22 | 2009-05-27 | 上海交通大学 | Method for acquiring and converting the state of component in the time of operation during software dynamic evolvement |
CN101236503A (en) * | 2008-02-27 | 2008-08-06 | 鞠京佳 | Hot-deployment entity component |
CN101393528B (en) * | 2008-10-30 | 2011-11-16 | 上海交通大学 | Method and system for determining instance object conversion order in dynamic update of software |
CN101739297B (en) * | 2010-01-21 | 2012-10-03 | 上海交通大学 | Service object state transfer system in pervasive service trend update and method thereof |
CN102270179B (en) * | 2010-06-03 | 2015-12-02 | 苏州浩辰软件股份有限公司 | For the data Storage and Processing method based on sheet unit and the system thereof of CAD system |
CN103488645A (en) * | 2012-06-13 | 2014-01-01 | 镇江华扬信息科技有限公司 | Structural designing method for updating data of internet of things |
CN104599319B (en) * | 2014-12-26 | 2017-05-31 | 福建工程学院 | A kind of Real-time Generation of 3D scenes |
-
2015
- 2015-11-12 CN CN201510778675.3A patent/CN106708547B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090150898A1 (en) * | 2007-12-11 | 2009-06-11 | Electronics And Telecommunications Research Institute | Multithreading framework supporting dynamic load balancing and multithread processing method using the same |
CN102819438A (en) * | 2011-06-08 | 2012-12-12 | 金蝶软件(中国)有限公司 | Hot-load method and device and information system |
CN102843342A (en) * | 2011-06-22 | 2012-12-26 | 华为软件技术有限公司 | Method and system for dynamically upgrading resource |
CN102591659A (en) * | 2011-12-28 | 2012-07-18 | 中标软件有限公司 | Implementation method for widget on main interface of mobile terminal and management method for widget |
CN103197952A (en) * | 2012-01-09 | 2013-07-10 | 华为技术有限公司 | Management system and method aiming at maintenance and deployment of application system based on cloud infrastructure |
CN103218220A (en) * | 2013-02-25 | 2013-07-24 | 上海谐宇网络科技有限公司 | Dynamic pluggable component based-Internet of things middleware system |
Also Published As
Publication number | Publication date |
---|---|
CN106708547A (en) | 2017-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106708547B (en) | Service plug-in management method and system | |
US10511506B2 (en) | Method and device for managing virtualized network function | |
JP6025136B2 (en) | Method and computer program for dynamic software version selection | |
US9253265B2 (en) | Hot pluggable extensions for access management system | |
CN109788068B (en) | Heartbeat state information reporting method, device and equipment and computer storage medium | |
CN109656742B (en) | Node exception handling method and device and storage medium | |
CN107453932B (en) | Distributed storage system management method and device | |
CN107479984B (en) | Distributed spatial data processing system based on message | |
CN109639818B (en) | Service discovery method and device under cloud environment, server and storage medium | |
CN109697078B (en) | Repairing method of non-high-availability component, big data cluster and container service platform | |
CN108319492B (en) | Method, device and system for resetting physical machine | |
CN104572394A (en) | Process monitoring method and device | |
CN113037881A (en) | Cloud native service uninterrupted IP replacement method based on Kubernetes | |
CN109067562A (en) | Dynamic configuration update method and system, server and medium based on intelligent pointer | |
CN115543429A (en) | Project environment building method, electronic equipment and computer readable storage medium | |
CN113434180B (en) | Data processing method and device for application, server and storage medium | |
US20160321057A1 (en) | Electronic apparatus | |
CN112905306A (en) | Multi-cluster container management method and device, electronic equipment and storage medium | |
CN108536541B (en) | Process engine object processing method and device | |
CN107544813B (en) | Switching method and system for static library configuration | |
CN111538738B (en) | Service upgrading method and device, electronic equipment and storage medium | |
CN107085514B (en) | Shared library upgrading method and device | |
CN107431636B (en) | Control of ad hoc network functions | |
EP3255542A1 (en) | Service management method and the device | |
CN113608831A (en) | Plug-in instance management method, system, storage medium and equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |