CN102486725A - Distributed platform and method for managing life cycle of functional module in platform - Google Patents
Distributed platform and method for managing life cycle of functional module in platform Download PDFInfo
- Publication number
- CN102486725A CN102486725A CN2010105709976A CN201010570997A CN102486725A CN 102486725 A CN102486725 A CN 102486725A CN 2010105709976 A CN2010105709976 A CN 2010105709976A CN 201010570997 A CN201010570997 A CN 201010570997A CN 102486725 A CN102486725 A CN 102486725A
- Authority
- CN
- China
- Prior art keywords
- module
- functional module
- title
- distributed platform
- registration table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a distributed platform and a method for managing a life cycle of a functional module in the platform. The method comprises the following steps: performing register searching by a service register module when a new functional module (plug-in) is loaded in the distributed platform; detecting if the new functional module is as same as a present functional module; and if yes, removing the present functional module from a registry and loading the new functional module into the registry. A correct functional module can be accessed by an access terminal according to the information of the registry, and the confliction of module access cannot be caused even if an original functional module is not unloaded temporarily, so that the immediate shutdown for unloading the original functional module is unnecessary after the functional module (plug-in) in the distributed platform is updated or upgraded, and the normal running of the distributed platform during an upgrading process is ensured.
Description
Technical field
The present invention relates to a kind of software life cycle management technology
Background technology
Distributed platform is a technology based on middleware, and middleware is a kind of independently system software or service routine, and distributed platform is through this technology shared resource between different servers, and unified management is distributed in the service and the resource of different server.When the user uses service or resource at needs; Send the request of required service/resource to distributed platform through client; And by distributed platform user institute requested service/resource is positioned, find the server at this service/resource place, this request is sent to corresponding server handles; After server process finished, the result that draws still fed back to this client through this distributed platform.
Distributed platform generally comprises functional modules such as Registering modules, search module, authentication module, resource locating module, log pattern and purview certification module; As shown in Figure 1; Each module all has its function separately; And orderly assigning on this distributed platform, make distributed platform can effectively reach user's primary demand.In order to ensure the normal operation of distributed platform, need carry out life cycle management to each functional module on the platform, comprise each module installation, open, close, upgrade, upgrade and unload.There is more weak point in existing module life period managing method.
Upgrade, upgrade to example with module; Each module of distributed platform needs regularly or carries out content update or edition upgrading according to user's different demands; In the prior art; Need close corresponding server to module renewal or upgrading, reload the corresponding old module of new module and removal, and could normally use after restarting this server.But distributed system has the cohesion and the transparency of height, closes arbitrarily or restarts server and all can bring the work delays progress, and is more serious even can generation systems paralysis problem.At this moment, then need carry out effective life cycle management to each module.
Summary of the invention
The technical matters that the present invention mainly solves provides the functional module life cycle management method in a kind of distributed platform and the platform; Make functional module in the distributed platform (plug-in unit) is upgraded or when upgrading; When new and old module can be carried on the platform simultaneously; Need not shutdown unloading original module, and can the generation module access conflict.
In order to solve the problems of the technologies described above, the invention provides the functional module life cycle management method in a kind of distributed platform, comprise following steps:
When in distributed platform, moving into new functional module; The service registry module of this distributed platform is registered search; If the new functional module title of said immigration is identical with existing capability module title; Then in registration table, remove said existing capability module of the same name, said new functional module is loaded in this registration table;
The functional module that access end is corresponding according to said registry access.
Said new functional module title is identical with existing capability module title, can comprise following situation:
Title is identical, does not comprise version number in the title;
Version number is different in the title, and other are identical;
Title is identical, and comprises version number in the title.
As the improvement of technique scheme, after definite functional module title is identical, in registration table, remove said existing capability module of the same name, be loaded into said new functional module in this registration table before, can also comprise following steps:
If the version number that comprises in the said functional module title is different; Then said service registry module is further judged release level; When the version number of judging the new functional module that moves into is superior to the version number of existing capability module of the same name; Carry out the said said existing capability module of the same name that in registration table, removes, said new functional module is loaded into the step in this registration table.
As the improvement of technique scheme, when said distributed platform equipment shuts down naturally or restarts naturally, unload the functional module that removes the said registration table from this distributed platform.
The present invention also provides a kind of distributed platform, comprises:
Registering modules is used for loading or remove functional module at registration table;
Search module; Be used for when distributed platform moves into new functional module; Register search; If the new functional module title of said immigration is identical with existing capability module title, then indicate said Registering modules in registration table, to remove said existing capability module of the same name, said new functional module is loaded in this registration table.
Said search module judges that in following situation new functional module title is identical with existing capability module title:
Title is identical, does not comprise version number in the title;
Version number is different in the title, and other are identical;
Title is identical, and comprises version number in the title.
Improvement as technique scheme; Said search module can also be used for that functional module title in said new immigration comprises version number and with the existing capability module release when number inequality; Further judge release level; When the version number of judging the new functional module that moves into is superior to the version number of existing capability module of the same name, indicate said Registering modules in registration table, to remove said existing capability module of the same name, said new functional module is loaded in this registration table.
Embodiment of the present invention compared with prior art; The key distinction and effect thereof are: when in distributed platform, loading new functional module (plug-in unit); The service registry module is all registered search; Detect this functional module and whether repeat,, new functional module is loaded in this registration table if repeat then in registration table, remove the existing capability module with the existing capability module; Make access end to have access to correct functional module according to registry information; Even if temporarily do not unload original functional module; Can not cause the conflict of module accesses yet; Thereby after need not functional module in distributed platform (plug-in unit) and upgrading or upgrade, the original module of shutdown unloading immediately guarantees that distributed platform still can operate as normal in escalation process.
Description of drawings
Below in conjunction with accompanying drawing and embodiment the present invention is done further explain.
Fig. 1 is the structural representation of distributed system;
Fig. 2 is the update method process flow diagram of functional module in the distributed platform in the first embodiment of the invention;
Fig. 3 is that the distributed platform upper module in the first embodiment of the invention upgrades synoptic diagram;
Fig. 4 is the distributed platform upper module upgrading synoptic diagram in the first embodiment of the invention;
Fig. 5 is the registration table synoptic diagram in the first embodiment of the invention.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, will combine accompanying drawing that embodiment of the present invention is done to describe in detail further below.
First embodiment of the invention relates to the functional module life cycle management method in a kind of distributed platform, life management cycle method in this embodiment, and it improves main content update and version updating in module.And the installation of module in the life cycle management method, open, close and discharging method, do not have significant difference with prior art, be not described in detail at this.
The update method flow process of functional module is as shown in Figure 2 in the concrete distributed platform, and in step 201, the software developer moves into the new functional module after content update or the version updating on the distributed platform according to user's different demands.
In the step 202, the service registry module is registered search to existing module on the distributed platform, finds new functional module.
If new functional module title does not comprise version number; Then get into step 203; Contrast original module title in new module title that moves into and the service registry module one by one; Whether inspection has duplication of name, if original module title has duplication of name in new module title that moves into and the service registry module, then gets into step 205; If do not bear the same name, then get into step 206.
If new functional module title comprises version number; Then get into step 204; Contrast original module title and version number in new module title that moves into and the service registry module one by one; Whether inspection bears the same name and edition upgrading, if duplication of name and version number are higher than this duplication of name module, then gets into step 205; Otherwise then get into step 206.
In the step 205, in registration table, remove said existing capability module of the same name.
In the step 206, the functional module that newly moves into is loaded in the registration table.The user just can be according to the functional module of registry access correspondence.
Specifically, suppose to have existed on the distributed platform modules A and module B v1.0.According to user's a certain demand, need modules A has been carried out the renewal on the content, module B v1.0 has been carried out the renewal on the version.Modules A and module B v2.0 have been generated thus.When moving into distributed platform to these 2 new functional modules, the service registry module then can be searched for existing module, simultaneously existing module title in the title of new module and the service registry module is compared one by one.At this moment, can realize that then modules A and module B v1.0 have been present in the service registry module.Identical with the modules A name of new immigration, different with module B v2.0 version, and be higher than existing version.So, replace original modules A with the new module A of content update, as shown in Figure 3; The new module B v2.0 of version updating replaces original module B v1.0, and is as shown in Figure 4.Registration table after the renewal is as shown in Figure 5.
In sum; When in distributed platform, loading new functional module (plug-in unit); The service registry module is all registered search; Detect this functional module and whether repeat,, new functional module is loaded in this registration table if repeat then in registration table, remove the existing capability module with the existing capability module; Make access end to have access to correct functional module according to registry information; Even if temporarily do not unload original functional module; Can not cause the conflict of module accesses yet; Thereby after need not functional module in distributed platform (plug-in unit) and upgrading or upgrade, the original module of shutdown unloading immediately guarantees that distributed platform still can operate as normal in escalation process.
Second embodiment of the invention relates to a kind of distributed platform, comprises: Registering modules is used for loading or remove functional module at registration table; Search module; Be used for when distributed platform moves into new functional module; Register search; If the new functional module title that moves into is identical with existing capability module title, then indicate Registering modules in registration table, to remove existing capability module of the same name, new functional module is loaded in this registration table.
As further improvement, search module is in following situation, and judge that new functional module title is identical with existing capability module title: title is identical, does not comprise version number in the title; Version number is different in the title, and other are identical; Title is identical, and comprises version number in the title.
As further improvement; Search module also is used for comprising version number and with the existing capability module release when number inequality in the new functional module title that moves into; Further judge release level; When the version number of judging the new functional module that moves into was superior to the version number of existing capability module of the same name, the indication Registering modules removed existing capability module of the same name in registration table, new functional module is loaded in this registration table.
In the prior art, this server need be restarted and the new functional module that moves into could be used.Now; Only need through the running between Registering modules on this distributed platform and the search module; Need not to restart server, just can directly use new functional module, brought more facility to distributed system; Not only avoided also having prevented to cause thus simultaneously a series of problems such as systemic breakdown owing to restart the reduction of the work efficiency that server brings.In addition, when new and old module can be carried on the platform simultaneously, need not shutdown unloading original module, and can the generation module access conflict.Old module only needs when next distributed platform equipment shuts down naturally or restarts naturally, just can from the functional module that this distributed platform removes.
Though through reference some preferred implementation of the present invention; The present invention is illustrated and describes; But those of ordinary skill in the art should be understood that and can do various changes to it in form with on the details, and without departing from the spirit and scope of the present invention.
Claims (7)
1. the functional module life cycle management method in the distributed platform is characterized in that, comprises following steps:
When in distributed platform, moving into new functional module; The service registry module of this distributed platform is registered search; If the new functional module title of said immigration is identical with existing capability module title; Then in registration table, remove said existing capability module of the same name, said new functional module is loaded in this registration table;
The functional module that access end is corresponding according to said registry access.
2. the life cycle management method of functional module is characterized in that in the distributed platform according to claim 1, and said new functional module title is identical with existing capability module title, comprises following situation:
Title is identical, does not comprise version number in the title;
Version number is different in the title, and other are identical;
Title is identical, and comprises version number in the title.
3. the life cycle management method of functional module in the distributed platform according to claim 2; It is characterized in that; After definite functional module title is identical; In registration table, remove said existing capability module of the same name, be loaded into said new functional module in this registration table before, also comprise following steps:
If the version number that comprises in the said functional module title is different; Then said service registry module is further judged release level; When the version number of judging the new functional module that moves into is superior to the version number of existing capability module of the same name; Carry out the said said existing capability module of the same name that in registration table, removes, said new functional module is loaded into the step in this registration table.
4. the life cycle management method of functional module is characterized in that in the distributed platform according to claim 1, when said distributed platform equipment shuts down naturally or restarts naturally, unloads the functional module that removes the said registration table from this distributed platform.
5. a distributed platform is characterized in that, comprises:
Registering modules is used for loading or remove functional module at registration table;
Search module; Be used for when distributed platform moves into new functional module; Register search; If the new functional module title of said immigration is identical with existing capability module title, then indicate said Registering modules in registration table, to remove said existing capability module of the same name, said new functional module is loaded in this registration table.
6. distributed platform according to claim 5 is characterized in that, said search module judges that in following situation new functional module title is identical with existing capability module title:
Title is identical, does not comprise version number in the title;
Version number is different in the title, and other are identical;
Title is identical, and comprises version number in the title.
7. distributed platform according to claim 6; It is characterized in that; Said search module is used for also that functional module title in said new immigration comprises version number and with the existing capability module release when number inequality; Further judge release level; When the version number of judging the new functional module that moves into is superior to the version number of existing capability module of the same name, indicate said Registering modules in registration table, to remove said existing capability module of the same name, said new functional module is loaded in this registration table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105709976A CN102486725A (en) | 2010-12-02 | 2010-12-02 | Distributed platform and method for managing life cycle of functional module in platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105709976A CN102486725A (en) | 2010-12-02 | 2010-12-02 | Distributed platform and method for managing life cycle of functional module in platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102486725A true CN102486725A (en) | 2012-06-06 |
Family
ID=46152224
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010105709976A Pending CN102486725A (en) | 2010-12-02 | 2010-12-02 | Distributed platform and method for managing life cycle of functional module in platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102486725A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970554A (en) * | 2013-01-30 | 2014-08-06 | 广东美的制冷设备有限公司 | Control method for function upgrading of household appliance product |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1739103A (en) * | 2002-12-20 | 2006-02-22 | 高通股份有限公司 | System for registry-based automatic installation and component handling on a device |
| CN1839381A (en) * | 2003-08-15 | 2006-09-27 | 微软公司 | Servicing a component-based software product |
| CN101014045A (en) * | 2007-02-02 | 2007-08-08 | 清华大学 | Distributed method of service management in service loading network |
| CN101207517A (en) * | 2007-12-12 | 2008-06-25 | 浙江大学 | Method for reliability maintenance of distributed enterprise service bus node |
| CN101499931A (en) * | 2009-03-13 | 2009-08-05 | 中兴通讯股份有限公司 | Function expansion method and system based on distributed environment |
| CN101794222A (en) * | 2010-01-13 | 2010-08-04 | 腾讯科技（深圳）有限公司 | Software version collecting method, management system and software upgrading detection method and system |
-
2010
- 2010-12-02 CN CN2010105709976A patent/CN102486725A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1739103A (en) * | 2002-12-20 | 2006-02-22 | 高通股份有限公司 | System for registry-based automatic installation and component handling on a device |
| CN1839381A (en) * | 2003-08-15 | 2006-09-27 | 微软公司 | Servicing a component-based software product |
| CN101014045A (en) * | 2007-02-02 | 2007-08-08 | 清华大学 | Distributed method of service management in service loading network |
| CN101207517A (en) * | 2007-12-12 | 2008-06-25 | 浙江大学 | Method for reliability maintenance of distributed enterprise service bus node |
| CN101499931A (en) * | 2009-03-13 | 2009-08-05 | 中兴通讯股份有限公司 | Function expansion method and system based on distributed environment |
| CN101794222A (en) * | 2010-01-13 | 2010-08-04 | 腾讯科技（深圳）有限公司 | Software version collecting method, management system and software upgrading detection method and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970554A (en) * | 2013-01-30 | 2014-08-06 | 广东美的制冷设备有限公司 | Control method for function upgrading of household appliance product |
| CN103970554B (en) * | 2013-01-30 | 2017-07-18 | 广东美的制冷设备有限公司 | A kind of control method of household appliances function upgrading |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2580065C2 (en) | Method and system for software update | |
| US8032880B2 (en) | Multi-branch management for updating software | |
| CN102238093B (en) | Service interruption prevention method and device | |
| CN105320527A (en) | Configuration file renewing method, device and system based on zookeeper distributed type search engine | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| CN105653329A (en) | Application management method, apparatus and system | |
| US10824441B2 (en) | Application program management method for multiple hardware platforms | |
| CN104360878A (en) | Method and device for deploying application software | |
| CN103530150A (en) | Remote updating method for Linux operating system | |
| CN104657158A (en) | Method and device for processing business in business system | |
| CN103164247B (en) | The method and device that system application is repaired automatically | |
| CN111897558A (en) | Kubernets upgrading method and device for container cluster management system | |
| CN105260209A (en) | Hot-update solution of program | |
| CN103246534A (en) | Method and device for migrating operating system | |
| CN102486732A (en) | Distributed type platform and control method for starting priorities of functional modules in platform | |
| CN109992450A (en) | System upgrade backing method, terminal, server and storage medium | |
| CN112596771A (en) | Method and system for uninterrupted service upgrade | |
| CN103186400A (en) | Web application program upgrading method and system | |
| CN103761131A (en) | Multi-board-card automatic updating method and system based on internal storage sharing | |
| CN103984585A (en) | Method for upgrading Linux kernel in running process of kernel module capable of being plugged in thermal mode | |
| CN111475172A (en) | Bare machine deployment method and device | |
| CN117056115B (en) | Application program repairing method and device, storage medium and electronic equipment | |
| CN103455750A (en) | High-security verification method and high-security verification system for embedded devices | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| CN105447382A (en) | Sandbox based software registry redirection method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20120606 |