CN102546718A - Software configuration method for functional modules in distributed platform - Google Patents
Software configuration method for functional modules in distributed platform Download PDFInfo
- Publication number
- CN102546718A CN102546718A CN2010106192967A CN201010619296A CN102546718A CN 102546718 A CN102546718 A CN 102546718A CN 2010106192967 A CN2010106192967 A CN 2010106192967A CN 201010619296 A CN201010619296 A CN 201010619296A CN 102546718 A CN102546718 A CN 102546718A
- Authority
- CN
- China
- Prior art keywords
- software
- functional module
- module
- distributed platform
- upgraded
- 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
Abstract
The invention discloses a software configuration method for functional modules in a distributed platform; the software configuration method comprises the following steps of: determining software packages needing to be used by the functional modules in the distributed platform; setting the software packages shared by the at least two functional modules in a public software package module; storing the path of a public software package to which public domain software needed by each functional module corresponds in each functional module, wherein each the functional module calls the corresponding software package from the corresponding public software package module according to the path to realize needed functions. By adopting the software configuration method, the same software packages are ensured to need to be packed once, and the repeated packaging and loading is not needed, thereby greatly saving disk space; and when software updates or upgrades, the corresponding functional modules do not need to be compiled one by one.
Description
Technical field
The present invention relates to a kind of software arrangements technology
Background technology
Distributed platform is a technology based on middleware, and middleware is a kind of independently systems soft ware 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.
On distributed platform, add and carry into hundred and even thousands of functional modules.In order to make the in order reasonably operation of each module, must guarantee the required software kit of use that each functional module can be accurately and timely.Therefore, the engineer will be kept at this software kit in the corresponding function module, and this functional module is called local software stored bag, realizes required function.If perhaps during version updating, the engineer only needed find corresponding software and carry out associative operation through this path in this module needed.
And in the prior art, in this software kit needs, perhaps during the renewal of version, need the engineer to close this distributed platform, and one by one all modules that use this software kit are upgraded, and could normally use after restarting this distributed platform.Yet; Huge in functional module quantity, concern under the complicated situation; If the upgrading of software kit must rely on the engineer that the functional module that comprises these software kits is upgraded one by one, then can therefore expend more manpower and material resources, even more serious even can the work delays progress.And in practical application, disparate modules possibly need to use identical software kit, according to above-mentioned prior art, need same software kit repeated to be carried in each functional module that need use this software kit, has wasted the space of disk greatly.This shows, be the task of top priority for distributed platform provides a kind of more efficiently functional module software layout method.
Summary of the invention
The technical problem that the present invention mainly solves provides functional module software layout method in a kind of distributed platform, makes that package update is easier in the distributed platform, and has practiced thrift the distributed platform disk space.
In order to solve the problems of the technologies described above, the invention provides functional module software layout method in a kind of distributed platform, comprise following steps: confirm the software kit that each functional module need be used in the distributed platform;
At least two shared common software packings of functional module are downloaded in the common software bag module;
Preserve the path of the corresponding common software bag of its required common software in each functional module, this functional module is called corresponding software kit based on this path from the common software bag module of correspondence, realizes required function.
As the improvement of technique scheme, this method can also comprise following steps:
The independent software setting of using of each functional module in the distributed platform in a privately owned software kit, is kept in the corresponding function module, and this functional module is called local software stored bag, realizes required function.
As the improvement of technique scheme, this method can also comprise following steps:
When needs upgrade software or upgrade,, then separately this common software bag module is upgraded or upgraded if this software is stored in the common software bag module; If this software is stored in the privately owned software kit, the functional module that then this privately owned software kit is belonged to is upgraded or is upgraded.
As the improvement of technique scheme, the functional module that in the following manner privately owned software kit is belonged to is upgraded or is upgraded:
Directly in distributed platform, move into upgrade or upgrading after functional module;
The service registry module of this distributed platform is registered search; If the new functional module title that moves into is identical with existing capability module title; Then in registration table, remove existing capability module of the same name, the functional module of this new immigration is loaded in this registration table;
The functional module that access end is corresponding according to registry access.
As the improvement of technique scheme, when distributed platform equipment shuts down naturally or restarts naturally, the old functional module that from this this registration table of distributed platform unloading, removes.
Embodiment of the present invention compared with prior art, the main distinction and effect thereof are: confirm the software kit that each functional module need be used in the distributed platform; At least two shared software kits of functional module are set in the common software bag module; Preserve the path of the corresponding common software bag of its required common software in each functional module, each functional module is called corresponding software kit according to the path from the common software bag module of correspondence, realizes required function.Thereby guarantee that identical software kit only need pack once, need not to repeat packing and load, practiced thrift disk space greatly, and take place to upgrade or during upgrading, need not one by one each functional module of correspondence is compiled at software.
Description of drawings
Below in conjunction with accompanying drawing and embodiment the present invention is done further explain.
Fig. 1 is each functional module software arrangements flow chart in the distributed platform in the present invention's one preferred embodiments;
Embodiment
For making the object of the invention, technical scheme and advantage clearer, embodiment of the present invention is done to describe in detail further below in conjunction with accompanying drawing.
The present invention's one preferred embodiments relates to functional module software layout method in a kind of distributed platform.In this execution mode; Under the software kit prerequisite that each functional module need be used in confirming distributed platform; At least two shared software kits of functional module are arranged in the common software bag module, and the software kit that each functional module is used separately then is placed in the functional module of using this software kit.If need upgrade or when upgrade, then only need taked corresponding operation to this software kit module to software.
Each functional module software arrangements flow process is as shown in Figure 1 in the concrete distributed platform, in step 101, confirms the software kit that each functional module need be used in the distributed platform.
For example, comprise functional module A, B, C, D in this distributed platform, modules A, B, D need the character string process software; Module B needs matrix operation software; Modules A, C need the integer process software; Module B, D need the floating number process software, and be as shown in table 1.
| Sequence number | The module title | The software kit that needs |
| 0 | Modules A | Character string process software, integer process software |
| 1 | Module B | Character string process software, matrix operation software, floating number process software |
| 2 | Module C | The integer process software |
| 3 | Module D | The floating number process software |
Table 1
In the step 102, the software kit required according to each functional module is in order to check whether have 2 or the shared software kit of above functional module.If have 2 or the shared software kit of above functional module, then get in the step 103; If do not exist, represent that then this software kit is a privately owned software kit, get into step 104.
In the step 103; The software packaging that this is shared is downloaded in the common software bag module; And each functional module is preserved the corresponding common software bag path of its required common software; Each functional module only needs from the common software bag module of correspondence, to call corresponding software kit according to this path, realizes required function.
Visible according to above-mentioned example, character string process software, integer process software and floating number process software all exist 2 or above functional module to share, so all can be loaded into respectively in the common software bag module.
In the step 104, the software kit that each functional module is used separately is kept in the corresponding functional module as privately owned software kit, and this functional module is called local software stored bag, realizes required function.
Visible according to above-mentioned example, matrix operation software is the privately owned software kit that module B uses separately, then is kept among the module B.
When needs upgrade software or upgrade,, then separately this common software bag module is upgraded or upgraded if this software is stored in the common software bag module; If this software is stored in the privately owned software kit, the functional module that then this privately owned software kit is belonged to is upgraded or is upgraded.Specifically, only need the directly module (comprising software kit module or functional module) after immigration renewal or the upgrading in distributed platform.The service registry module of this distributed platform is with registering search earlier afterwards; If the new module title that moves into is identical with existing module title; Then this service registry module can remove existing module of the same name in registration table, and the module loading that will newly move into is in this registration table.By the way, make module in the distributed platform is upgraded or when upgrade, when new and old module can be carried on the platform simultaneously, need not shutdown and unload original module, and can the generation module access conflict.
Visible based on above-mentioned example, character string process software, integer process software and floating number process software be as total software kit, only needs its corresponding common software bag module is upgraded or upgraded; And matrix operation software only need upgrade or upgrade and just can as the privately owned software kit of module B module B.
In sum; This execution mode is set to two shared software kits of functional module in the common software bag module at least; And the path of preserving the corresponding common software bag of its required common software in each functional module; Each functional module is called corresponding software kit according to the path from the common software bag module of correspondence, realize required function.Practiced thrift disk space greatly, and take place to have upgraded or during upgrading, need not one by one each functional module of correspondence is compiled at software.Moreover, if need to unload the old functional module that removes in the registration table, can, distributed platform equipment promptly make things convenient for to save time again when shutting down naturally or restart naturally.
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 (5)
1. functional module software layout method in the distributed platform is characterized in that, comprises following steps:
Confirm the software kit that each functional module need be used in the distributed platform;
At least two shared common software packings of functional module are downloaded in the common software bag module;
Preserve the path of the corresponding common software bag of its required common software in each functional module, said functional module is called corresponding software kit according to this path from the common software bag module of correspondence, realizes required function.
2. functional module software layout method in the distributed platform according to claim 1 is characterized in that, also comprises following steps:
The independent software setting of using of each functional module in the said distributed platform in a privately owned software kit, is kept in the corresponding function module, and this functional module is called local software stored bag, realizes required function.
3. functional module software layout method in the distributed platform according to claim 2 is characterized in that, also comprises following steps:
When needs upgrade software or upgrade,, then separately this common software bag module is upgraded or upgraded if this software is stored in the common software bag module; If this software is stored in the privately owned software kit, the functional module that then this privately owned software kit is belonged to is upgraded or is upgraded.
4. functional module software layout method in the distributed platform according to claim 3 is characterized in that, the functional module that in the following manner privately owned software kit is belonged to is upgraded or upgraded:
Directly in distributed platform, move into upgrade or upgrading after 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, the functional module of said new immigration is loaded in this registration table;
The functional module that access end is corresponding according to said registry access.
5. functional module software layout method in the distributed platform according to claim 4 is characterized in that, when said distributed platform equipment shuts down naturally or restarts naturally, unloads the old functional module that removes the said registration table from this distributed platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010106192967A CN102546718A (en) | 2010-12-31 | 2010-12-31 | Software configuration method for functional modules in distributed platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010106192967A CN102546718A (en) | 2010-12-31 | 2010-12-31 | Software configuration method for functional modules in distributed platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102546718A true CN102546718A (en) | 2012-07-04 |
Family
ID=46352674
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010106192967A Pending CN102546718A (en) | 2010-12-31 | 2010-12-31 | Software configuration method for functional modules in distributed platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102546718A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103995752A (en) * | 2014-06-16 | 2014-08-20 | 上海斐讯数据通信技术有限公司 | Intermodule notification callback method and module interaction structure |
| CN107357529A (en) * | 2017-07-11 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of storage cluster online upgrading method and system |
| CN107479940A (en) * | 2017-08-23 | 2017-12-15 | 绵阳美菱软件技术有限公司 | A kind of method and device for realizing Internet of Things module |
| CN112131263A (en) * | 2020-09-14 | 2020-12-25 | 微医云(杭州)控股有限公司 | Software package obtaining method, system, device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060242631A1 (en) * | 2005-04-22 | 2006-10-26 | Andersen Jakob R | Process and system for sharing program fragments |
| CN1936840A (en) * | 2005-09-23 | 2007-03-28 | 联想(北京)有限公司 | Computer system not relying on operation system renewing software data and method |
| US7343596B1 (en) * | 2002-03-19 | 2008-03-11 | Dloo, Incorporated | Method and system for creating self-assembling components |
-
2010
- 2010-12-31 CN CN2010106192967A patent/CN102546718A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7343596B1 (en) * | 2002-03-19 | 2008-03-11 | Dloo, Incorporated | Method and system for creating self-assembling components |
| US20060242631A1 (en) * | 2005-04-22 | 2006-10-26 | Andersen Jakob R | Process and system for sharing program fragments |
| CN1936840A (en) * | 2005-09-23 | 2007-03-28 | 联想(北京)有限公司 | Computer system not relying on operation system renewing software data and method |
Non-Patent Citations (3)
| Title |
|---|
| 催方园: "支持分布式协同开发的软件配置管理系统研究", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
| 杜岩峰等: "《C++ Builder 5 实践与提高》", 《中国电力出版社》 * |
| 王吉军等: "《黑客大曝光》", 《清华大学出版社》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103995752A (en) * | 2014-06-16 | 2014-08-20 | 上海斐讯数据通信技术有限公司 | Intermodule notification callback method and module interaction structure |
| CN107357529A (en) * | 2017-07-11 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of storage cluster online upgrading method and system |
| CN107357529B (en) * | 2017-07-11 | 2020-03-31 | 郑州云海信息技术有限公司 | Storage cluster online upgrading method and system |
| CN107479940A (en) * | 2017-08-23 | 2017-12-15 | 绵阳美菱软件技术有限公司 | A kind of method and device for realizing Internet of Things module |
| CN112131263A (en) * | 2020-09-14 | 2020-12-25 | 微医云(杭州)控股有限公司 | Software package obtaining method, system, device, electronic equipment and storage medium |
| CN112131263B (en) * | 2020-09-14 | 2024-02-27 | 微医云(杭州)控股有限公司 | Software package acquisition method, system, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10496503B2 (en) | Healing cloud services during upgrades | |
| CN107515776B (en) | Method for upgrading service continuously, node to be upgraded and readable storage medium | |
| CN104158886B (en) | Flow-type performing method for applications | |
| CN102255752B (en) | Configuration management system and method of server cluster | |
| RU2653292C2 (en) | Service migration across cluster boundaries | |
| CN104317642A (en) | Method and device for configuring software in cloud calculation environment | |
| CN103024782B (en) | A kind of method and system of base station software version management | |
| CN104424002A (en) | Dynamic component loading method and system based on plug-in mechanism | |
| CN101895872A (en) | Method for conveniently downloading application program for mobile terminal | |
| CN102546718A (en) | Software configuration method for functional modules in distributed platform | |
| US10824441B2 (en) | Application program management method for multiple hardware platforms | |
| CN104375849A (en) | Core loading method and device | |
| AU2009207774A1 (en) | Method and system for deploying non-backward compatible server versions in a client/server computing environment | |
| CN105487881A (en) | Software installation package packaging method, device and system | |
| CN105487907A (en) | Difference package manufacturing method and device | |
| CN104239227A (en) | Virtualization storage management device and local virtualization storage management device and method | |
| CN105824688A (en) | Method for solving start concurrence bottleneck of docker container | |
| US20120166492A1 (en) | Database transfers using constraint free data | |
| CN103873534A (en) | Method and device for application cluster migration | |
| US11561812B2 (en) | Network policy and flow state save/restore for highly available servicing | |
| CN105656970A (en) | RAID (Redundant Array of Independent Disk) card configuring method and system and relevant device | |
| CN103873460B (en) | Service resources group implementation method and device | |
| CN101727496A (en) | Method for realizing load balancing cluster of MICROSOFT SQL SERVER database | |
| CN112860236A (en) | Single-spa-based micro front-end technology | |
| CN105302602A (en) | Smooth online upgrade method for cloud platform application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20120704 |
|
| WD01 | Invention patent application deemed withdrawn after publication |