CN102360308A - Distributed deployment system and method of components - Google Patents
Distributed deployment system and method of components Download PDFInfo
- Publication number
- CN102360308A CN102360308A CN2011102955812A CN201110295581A CN102360308A CN 102360308 A CN102360308 A CN 102360308A CN 2011102955812 A CN2011102955812 A CN 2011102955812A CN 201110295581 A CN201110295581 A CN 201110295581A CN 102360308 A CN102360308 A CN 102360308A
- Authority
- CN
- China
- Prior art keywords
- assembly
- component
- deployment
- assemblies
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention discloses a distributed deployment system and method of components. The method comprises the following steps of: step 202, generating a component deployment package by a configured component project, and storing deployment information, wherein the deployment information comprises the information of the component project, the information of at least one component in the component project, the association information of a plurality of components and the information of the component deployment package; and step 204, scanning the component deployment package and obtaining state attribute of the component in the component deployment package, if the state attribute is static, deploying the static component at a corresponding server node, and if the state attribute is dynamic, deploying the dynamic component at the corresponding server node, and storing the corresponding relation between the component and the server node. With the technical scheme of the invention, the components with complex dependence relation can be conveniently deployed and instances can be managed finely in a distributed environment, simultaneously, needs-based creation and startup can be realized, and influences on the entire system can be avoided.
Description
Technical field
The present invention relates to the deployment of components technology, in particular to the distributed deployment system and method for assembly.
Background technology
Based on component programming is an important method that strengthens software reusability, extendability, raising software development efficiency and quality always; But often need different component models for different language, different platform, the inter-module of different implementation models can't be directly mutual.The purpose of SCA is to use the family that a level of no longer directly facing concrete ins and outs is arranged when making up enterprise application, but makes up application through the mode of serviced component.This mode also makes client's enterprise application have good layer architecture, can be good at the service logic and the IT logic of separating application, not only is easy to the structure used, also is easy to the change and the deployment of using.SCA full name Service Component Architecture, i.e. serviced component framework.Serviced component architecture (SCA) is a standard, and it is described and is used to use SOA to make up the model of application program and system.SCA can simplify application development and the realization work of using SOA to carry out greatly, has become one of most important standard in the SOA architectural framework.
An assembly is usually by following attribute description: service: described the function that the assembly of the type can provide; Quote: the dependence of having described the assembly correlation function of the type; Attribute: defined configuration parameter, how the control program logic realizes for example, use which kind of currency in the payment services; Strategy: described the assembly behavioral strategy, mainly contained two kinds of strategies: implementation strategy: assembly is realized exerting one's influence, for example: affairs, supervision and daily record; Interactive tactics: how interactive definitions component is, for example: safety.
As shown in Figure 1, a typical assembly 100 comprises component property 102, assembly strategy, service 106 and quotes 108.The programming language that assembly can use Any user to want goes to realize, for example goes to realize operation flow control with BPEL, and XSLT realizes changing, and RUBY comes compile script, also can use pure JAVA.These serve, quote, how attribute and strategy go to define what defined an assembly is specifically to realize type.
Assembly is the most basic unit, in the actual enterprise application, seldom has so simple business can satisfy through a single assembly; But, form composite component through a plurality of component groups are fitted together, can also composite component and single component be continued combination; Through continuous assembling, reuse existing assembly; Form the more assembly of coarsegrain, satisfy higher level, complicated service demand more, playing with building blocks of realizing really that the software people pursues always equally makes up the dream of using.Along with the constantly assembling and multiplexing of assembly quilt, inter-module produces the dependence that becomes increasingly complex thereupon.The simplest deployment scheme is exactly to have the assembly of dependence all to be deployed on the server node these; But along with component count increase and the requirement of different assembly application server is had nothing in common with each other, concentrated deployment often can't guarantee the quality (high concurrency and high availability) of service that assembly provides.This moment, the scheme generally taked was according to the performance requirement of assembly to server, on the server that deployment of components is complementary to performance index, and can better server such as the assembly of doing the cost computing is compared the assembly of general web search with regard to desirability.A kind of in addition situation then is because assembled assembly belongs to different departments or tissue; Be in protection assembly copyright or for the ease of maintenance and management assembly nearby; And can be mutual with local data base and other Legacy Systems nearby for assembly, the assembly of all departments and tissue generally can be deployed on the local server.Based on above-mentioned analysis; The complicated assembly that dependence is arranged need distribute at specific business scenario and be deployed on the different server nodes, and this solves a sequence problem of assembly distributed deployment with regard to needs, like the component dependencies analysis; Transparent deployment, mistake recovery etc.
In the reference implementation Tuscany project of SCA standard through domain manager, Management Unit distributed deployment that can system.In the time of concrete configuration; Physics is disposed bag (contribution), assembly assembled configuration file (composite), operation node (Node), assembly assembled configuration file deployment configuration (Cloud) etc. and must be registered by hand; This has not only increased the O&M cost of software; Easy error also, i.e. the state of the real operation of server occurs inconsistent with configuration easily.In addition at the component instance management aspect; There is a problem in prior art, is exactly in case pass through domain manager assembly assembled configuration file registration to be arrived specific operation node, when then node starts; Corresponding component instance just is created; Rather than go dynamic creation and start corresponding component instance based on the dependence of inter-module, this just causes some basic assembly that just is not cited also can be created and start service, causes valuable server resource waste.Same when certain assembly is out of service, the component instance that its single line relies on can not stop service automatically and destroy instance, and those reverse assemblies that rely on this assembly also can't be done corresponding processing (such as the strategy of also taking to stop to serve).In this external distributed environment, can revise the configuration of server node sometimes according to safety and managerial demand, present technological frame is when handling this type problem; Remove to restart all component that is deployed on the server node that is modified configuration except requiring manual work; Also must be through manual work other assemblies of these assemblies of having restarted all references, these assemblies possibly be distributed on the different server nodes, when inter-module has complicated dependence; This is the very work of difficulty; Handling cost is very high, causes the keeper to tend to restart Servers-all, the service disruption that causes other normally to move.
Therefore, need a kind of new deployment of components technology, can be implemented under the distributed environment assembly that complicated dependence is arranged convenient disposed and to the fine-grained management of instance, realized simultaneously creating as required and starting, avoid influence total system.
Summary of the invention
The present invention just is being based on the problems referred to above; A kind of new deployment of components technology has been proposed; Can be implemented under the distributed environment assembly that complicated dependence is arranged convenient disposed and to the fine-grained management of instance, realized simultaneously creating as required and starting, avoid influence total system.
In view of this, the present invention proposes a kind of distributed deployment system of assembly, comprising: client, memory storage and server, wherein, said client comprises: first generation module, the component project formation component that utilizes configuration to accomplish is disposed bag; First communication module; Be connected to said memory storage; Be used for deployment information is sent to said memory storage, said deployment information comprises the information of information, the related information between a plurality of assembly and said deployment of components bag of information, at least one assembly in the said component project of said component project; Said memory storage is connected to said client and said server, stores said deployment information; Said server comprises: second communication module, be connected to said client, and be used to receive said deployment of components bag; Scan module scans the said deployment of components bag that said second communication module receives, and obtains the status attribute of the assembly in the said deployment of components bag; Deployment module; In said status attribute is that said assembly is a static component, and said static component is deployed in the corresponding server node under the situation of static state; In said status attribute is under the dynamic situation; Said assembly is a dynamic assembly, and said dynamic assembly is deployed in the corresponding server node, and the corresponding relation of said assembly and said server node is stored in the said memory storage; Create module, be the building component instance.In this technical scheme, client is after assembly generates the deployment bag, by server the assembly in the bag to be analyzed; If static component then can generate instance voluntarily, system there is not influence; If dynamic assembly; Then usually complex dependency relationship is arranged, need carry out record, store the corresponding relation between the two as the sign of assembly is carried out related back with the sign of the node of being disposed with other assemblies; Then follow-up can passing through inquired about this corresponding relation, on node corresponding, creates the corresponding dynamic component instance.Simultaneously, through the corresponding relation of assembly and node is stored, be convenient to go wrong in the time of maybe need detecting, restart etc. at assembly; Single component or part assembly are operated; And needn't total system be restarted, reduce influence to other assemblies, reduce the maintenance cost of system.
In technique scheme, preferably, the said first communication module of said client also is used for: said deployment of components bag is sent to server node.In this technical scheme; Client is after generating the deployment bag; Follow-up work is accomplished by server as disposing usually, and at first needs server to obtain the deployment bag of its generation from client, but also can be by client after generating the deployment bag; Directly will dispose bag and transfer to node or other prepositions that to be disposed, and make things convenient for server to carry out deployment operation.
In technique scheme, preferably, said server also comprises: second generation module, for dynamic assembly generates loader, said loader is used for loading the resource of said dynamic assembly.In this technical scheme, server can be after detecting dynamic assembly, and for it generates loader, so that it is loaded, loading procedure can accurately carry out under OSGI (Open Service Gateway Initiative) framework.
In technique scheme, preferably, said server also comprises: parsing module; The configuration file that is used for resolution component, and said assembly is carried out first judge, said first judgement comprises judges whether said assembly is made up of other assemblies; If judged result then is said building component instance for not, if said judged result is for being; Then carrying out second judges; Said second judges to comprise judging whether said other assemblies are positioned at this locality, if said other assemblies are positioned at this locality, then said other assemblies are carried out said first and judges; If said other assemblies are not positioned at this locality, then inquire about the deployment information of said other assemblies of storing in the said memory storage through enquiry module; Said enquiry module is used for the deployment information that is stored in said memory storage is inquired about; Detection module; The said deployment information that inquires according to said enquiry module; Obtain the server node that is deployed with said other assemblies; And test section is deployed on said other assemblies on the said server node whether by normal deployment, if be said other building component instances through said establishment module then.In this technical scheme, mainly be the process of creating instance for static component, this assembly is not if having dependence with other assemblies, the dependence here; Be meant mainly whether this assembly is made up of other assemblies,, then can directly create instance, if dependence is arranged if do not have; Together constituted assembly C like assembly A and assembly B, this moment, the establishment of the example need relate to assembly A and assembly B for assembly C; If the position that answer enquiring component A and assembly B this moment in this locality, then loads from this locality; Or be not, then from before search the node at its place the corresponding relation of assembly and node of storage, and it is inquired about.The processing mode here mainly is exactly in layer, and the assembly that will be in layer building is analyzed, and begins to create instance from the assembly of the bottom, and is quoted by upper component from level to level.In addition, the configuration file of resolving here is arranged in component project, and the corresponding configuration file of each assembly.
In technique scheme; Preferably; Before said establishment module was said other building component instances, also comprise: said server was connected to said server node through said second communication module, and obtained the sign of the instance that initiation is called on the said server node through said detection module; Be stored in the deployment information in the said memory storage through said enquiry module inquiry then corresponding to said other assemblies; And obtain the sign that has the invocation component of call relation with said other assemblies, and said server also comprises comparison module, said comparison module is used for the sign of more said instance and the sign of said invocation component; If there is not the sign of said invocation component in the sign of said instance, be that said invocation component is created instance then by said establishment module.In this technical scheme; The assembly that is positioned at bottom possibly used by a plurality of assemblies; Thereby some assemblies are when quoting, and this bottom assembly possibly be cited and create instance, and this moment, this instance can directly be quoted by assembly afterwards; And, then can by inquiry the time, carry out the establishment of instance for the bottom assembly of not creating instance as yet.Through this inquiry mode, the instance that can avoid having created experiences repetitive operation, simplifies the instance of upper component and creates.
According to another aspect of the invention; A kind of distributed deployment method of assembly has also been proposed; Comprise: step 202; The component project formation component that utilizes configuration to accomplish is disposed bag, and the storage deployment information, and said deployment information comprises the information of information, the related information between a plurality of assembly and said deployment of components bag of information, at least one assembly in the said component project of said component project; Step 204 scans said deployment of components bag, obtains the status attribute of the assembly in the said deployment of components bag; If said status attribute is static, said assembly is a static component, and said static component is deployed in the corresponding server node; If said status attribute is dynamic; Said assembly is a dynamic assembly, and said dynamic assembly is deployed in the corresponding server node, and stores the corresponding relation of said assembly and said server node.In this technical scheme, client is after assembly generates the deployment bag, by server the assembly in the bag to be analyzed; If static component then can generate instance voluntarily, system there is not influence; If dynamic assembly; Then usually complex dependency relationship is arranged, need carry out record, store the corresponding relation between the two as the sign of assembly is carried out related back with the sign of the node of being disposed with other assemblies; Then follow-up can passing through inquired about this corresponding relation, on node corresponding, creates the corresponding dynamic component instance.Simultaneously, through the corresponding relation of assembly and node is stored, be convenient to go wrong in the time of maybe need detecting, restart etc. at assembly; Single component or part assembly are operated; And needn't total system be restarted, reduce influence to other assemblies, reduce the maintenance cost of system.
In technique scheme, preferably, said step 202 also comprises: said deployment of components bag is sent on the server node.In this technical scheme; Client is after generating the deployment bag; Follow-up work is accomplished by server as disposing usually, and at first needs server to obtain the deployment bag of its generation from client, but also can be by client after generating the deployment bag; Directly will dispose bag and transfer to node or other prepositions that to be disposed, and make things convenient for server to carry out deployment operation.
In technique scheme, preferably, said step 204 also comprises: for dynamic assembly generates loader, said loader is used for loading the resource of said dynamic assembly.In this technical scheme, server can be after detecting dynamic assembly, and for it generates loader, so that it is loaded, loading procedure can accurately carry out under the OSGI framework.
In technique scheme, preferably, after said step 204, also comprise: step 206; The configuration file of resolution component, and said assembly is carried out first judge, said first judgement comprises judges whether said assembly is made up of other assemblies; If judged result then is said building component instance for not, if said judged result is for being; Then carry out second and judge, said second judges to comprise judging whether said other assemblies are positioned at this locality, if said other assemblies are positioned at this locality; Then said other assemblies are carried out said first and judge,, then inquire about the deployment information of said other assemblies of storage if said other assemblies are not positioned at this locality; Step 208, the said deployment information according to said other assemblies obtains the server node that is deployed with said other assemblies, and when detecting said other assemblies that are deployed on the said server node and normally disposed, is said other building component instances.In this technical scheme, mainly be the process of creating instance for static component, this assembly is not if having dependence with other assemblies, the dependence here; Be meant mainly whether this assembly is made up of other assemblies,, then can directly create instance, if dependence is arranged if do not have; Together constituted assembly C like assembly A and assembly B, this moment, the establishment of the example need relate to assembly A and assembly B for assembly C; If the position that answer enquiring component A and assembly B this moment in this locality, then loads from this locality; Or be not, then from before search the node at its place the corresponding relation of assembly and node of storage, and it is inquired about.The processing mode here mainly is exactly in layer, and the assembly that will be in layer building is analyzed, and begins to create instance from the assembly of the bottom, and is quoted by upper component from level to level.In addition, the configuration file of resolving here is arranged in component project, and the corresponding configuration file of each assembly.
In technique scheme, preferably, in said step 208; The process of said establishment instance also comprises: be connected to said server node; Write down the sign of the instance that initiation is called on the said server node, and the deployment information corresponding to said other assemblies of inquiry storage, the sign that has the invocation component of call relation with said other assemblies obtained; If there is not the sign of said invocation component in the sign of said instance, then be that said invocation component is created instance.In this technical scheme; The assembly that is positioned at bottom possibly used by a plurality of assemblies; Thereby some assemblies are when quoting, and this bottom assembly possibly be cited and create instance, and this moment, this instance can directly be quoted by assembly afterwards; And, then can by inquiry the time, carry out the establishment of instance for the bottom assembly of not creating instance as yet.Through this inquiry mode, the instance that can avoid having created experiences repetitive operation, simplifies the instance of upper component and creates.
Through above technical scheme, can be implemented under the distributed environment assembly that complicated dependence is arranged convenient disposed and to the fine-grained management of instance, realized simultaneously creating as required and starting, avoid influence to total system.
Description of drawings
Fig. 1 shows the formation synoptic diagram of the assembly of correlation technique;
Fig. 2 shows the block diagram of the distributed deployment system of assembly according to an embodiment of the invention;
Fig. 3 shows the process flow diagram of the distributed deployment method of assembly according to an embodiment of the invention;
Fig. 4 shows the synoptic diagram of the distributed deployment of assembly according to an embodiment of the invention;
Fig. 5 shows the process flow diagram of client running according to an embodiment of the invention;
Fig. 6 shows the process flow diagram of the distributed deployment of assembly according to an embodiment of the invention;
Fig. 7 shows the synoptic diagram of component dependencies according to an embodiment of the invention;
Fig. 8 shows the block diagram of server node communicator according to an embodiment of the invention;
Fig. 9 shows according to an embodiment of the invention and to be the process flow diagram of building component instance;
Figure 10 shows according to an embodiment of the invention and to be the process flow diagram of building component instance; And
Figure 11 shows according to an embodiment of the invention and to be the synoptic diagram of building component instance.
Embodiment
In order more to be expressly understood above-mentioned purpose of the present invention, feature and advantage, the present invention is further described in detail below in conjunction with accompanying drawing and embodiment.
Set forth a lot of details in the following description so that make much of the present invention, still, the present invention can also adopt other to be different from other modes described here and implement, and therefore, the present invention is not limited to the restriction of following disclosed specific embodiment.
Fig. 2 shows the block diagram of the distributed deployment system of assembly according to an embodiment of the invention.
As shown in Figure 2; The distributed deployment system 200 of assembly according to an embodiment of the invention comprises: client 202, memory storage 204 and server 206, wherein; Said client comprises: first generation module 208, and the component project formation component that utilizes configuration to accomplish is disposed bag; First communication module 210; Be connected to memory storage 204; Be used for deployment information is sent to memory storage 204, deployment information comprises the information of information, the related information between a plurality of assembly and deployment of components bag of information, at least one assembly in the component project of component project; Memory storage 204 is connected to client 202 and server 206, the storage deployment information; Server 206 comprises: second communication module 212, be connected to client 202, and be used for receiving unit and dispose bag; Scan module 214, the deployment of components bag that scanning second communication module 212 receives, and securing component is disposed the status attribute of the assembly in the bag; Deployment module 216; In status attribute is that assembly is a static component, and static component is deployed in the corresponding server node under the situation of static state; In status attribute is under the dynamic situation; Assembly is a dynamic assembly, and dynamic assembly is deployed in the corresponding server node, and the corresponding relation of assembly and server node is stored in the memory storage 204; Create module 218, be the building component instance; Second generation module 220, for dynamic assembly generates loader, loader is used for loading the resource of dynamic assembly; Parsing module 222 is used for the configuration file of resolution component, and assembly is carried out first judge; First judges to comprise whether determination component is made up of other assemblies, if judged result then is the building component instance for not; If judged result is then carried out second and judged for being, second judgement comprises judges whether other assemblies are positioned at this locality; If other assemblies are positioned at this locality; Then other assemblies are carried out first and judge,, then inquire about the deployment information of other assemblies of storage in the memory storages 204 through enquiry module 224 if other assemblies are not positioned at this locality; Enquiry module 224 is used for the deployment information that is stored in memory storage 204 is inquired about; Detection module 226; According to the deployment information that enquiry module 224 inquires, obtain the server node that is deployed with other assemblies, and whether test section is deployed on other assemblies on this server node by normal deployment; If be other building component instances then through creating module 218.In this technical scheme, client 202 is analyzed by the assembly in 206 pairs of bags of server after disposing bag for assembly generates; If static component then can generate instance voluntarily, system there is not influence; If dynamic assembly; Then usually complex dependency relationship is arranged, need carry out record, store the corresponding relation between the two as the sign of assembly is carried out related back with the sign of the node of being disposed with other assemblies; Then follow-up can passing through inquired about this corresponding relation, on node corresponding, creates the corresponding dynamic component instance.Simultaneously; Through the corresponding relation of assembly and node is stored; Be convenient to go wrong in the time of maybe need detecting, restart etc., single component or part assembly operated, and needn't total system 200 be restarted at assembly; Minimizing reduces the maintenance cost of system to the influence of other assemblies.
In technique scheme, the first communication module 208 of client 202 also is used for: the deployment of components bag is sent to server node.In this technical scheme; Client 202 is after generating the deployment bag; Follow-up work is accomplished by server 206 as disposing usually, and at first needs server 206 to obtain the deployment bag of its generation from client 202, but also can be by client 202 after generating the deployment bag; Directly will dispose bag and transfer to node or other prepositions that to be disposed, and make things convenient for server 206 to carry out deployment operation.
In technique scheme, server 206 can be after detecting dynamic assembly, and for it generates loader, so that it is loaded, loading procedure can accurately carry out under OSGI (Open Service Gateway Initiative) framework.
In technique scheme, in the process of creating instance for static component, this assembly is not if having dependence with other assemblies, the dependence here; Be meant mainly whether this assembly is made up of other assemblies,, then can directly create instance, if dependence is arranged if do not have; Together constituted assembly C like assembly A and assembly B, this moment, the establishment of the example need relate to assembly A and assembly B for assembly C; If the position that answer enquiring component A and assembly B this moment in this locality, then loads from this locality; Or be not, then from before search the node at its place the corresponding relation of assembly and node of storage, and it is inquired about.The processing mode here mainly is exactly in layer, and the assembly that will be in layer building is analyzed, and begins to create instance from the assembly of the bottom, and is quoted by upper component from level to level.
In technique scheme; Before establishment module 218 is other building component instances; Also comprise: server 206 is connected to server node through second communication module 212; And obtain the sign of the instance that initiation is called on the server node through detection module 226, be stored in the deployment information in the memory storage 204 through enquiry module 224 inquiries then, and obtain the sign that has the invocation component of call relation with other assemblies corresponding to other assemblies; And server 202 also comprises comparison module 228; Be used for the sign of comparative example and the sign of invocation component,, then create instance for invocation component by creating module 218 if there is not the sign of invocation component in the sign of instance.In this technical scheme; The assembly that is positioned at bottom possibly used by a plurality of assemblies; Thereby some assemblies are when quoting, and this bottom assembly possibly be cited and create instance, and this moment, this instance can directly be quoted by assembly afterwards; And, then can by inquiry the time, carry out the establishment of instance for the bottom assembly of not creating instance as yet.Through this inquiry mode, the instance that can avoid having created experiences repetitive operation, simplifies the instance of upper component and creates.
Fig. 3 shows the process flow diagram of the distributed deployment method of assembly according to an embodiment of the invention.
As shown in Figure 3; The distributed deployment method of assembly according to an embodiment of the invention; Comprise: step 302; The component project formation component that utilizes configuration to accomplish is disposed bag, and the storage deployment information, and deployment information comprises the information of information, the related information between a plurality of assembly and deployment of components bag of information, at least one assembly in the component project of said component project; Step 304, scan components is disposed bag, and securing component is disposed the status attribute of the assembly in the bag; If status attribute is static, then assembly is a static component, and static component is deployed in the corresponding server node; If status attribute is dynamic; Then assembly is a dynamic assembly, and dynamic assembly is deployed in the corresponding server node, and the corresponding relation of memory module and server node.In this technical scheme, client is after assembly generates the deployment bag, by server the assembly in the bag to be analyzed; If static component then can generate instance voluntarily, system there is not influence; If dynamic assembly; Then usually complex dependency relationship is arranged, need carry out record, store the corresponding relation between the two as the sign of assembly is carried out related back with the sign of the node of being disposed with other assemblies; Then follow-up can passing through inquired about this corresponding relation, on node corresponding, creates the corresponding dynamic component instance.Simultaneously, through the corresponding relation of assembly and node is stored, be convenient to go wrong in the time of maybe need detecting, restart etc. at assembly; Single component or part assembly are operated; And needn't total system be restarted, reduce influence to other assemblies, reduce the maintenance cost of system.
In technique scheme, step 302 also comprises: the deployment of components bag is sent on the server node.In this technical scheme; Client is after generating the deployment bag; Follow-up work is accomplished by server as disposing usually, and at first needs server to obtain the deployment bag of its generation from client, but also can be by client after generating the deployment bag; Directly will dispose bag and transfer to node or other prepositions that to be disposed, and make things convenient for server to carry out deployment operation.
In technique scheme, step 304 also comprises: for dynamic assembly generates loader, loader is used for loading the resource of dynamic assembly.In this technical scheme, server can be after detecting dynamic assembly, and for it generates loader, so that it is loaded, loading procedure can accurately carry out under the OSGI framework.
In technique scheme, after step 304, also comprise: step 306; The configuration file of resolution component, and assembly is carried out first judge, first judgement comprises whether determination component is made up of other assemblies; If judged result then is the building component instance for not, if judged result is for being; Then carry out second and judge, second judges to comprise judging whether other assemblies are positioned at this locality, if other assemblies are positioned at this locality; Then other assemblies are carried out said first and judge,, then inquire about the deployment information of other assemblies of storage if other assemblies are not positioned at this locality; Step 308 according to the deployment information of other assemblies, is obtained the server node that is deployed with other assemblies, and when detecting other assemblies that are deployed on the server node and normally disposed, is other building component instances.In this technical scheme, mainly be the process of creating instance for static component, this assembly is not if having dependence with other assemblies, the dependence here; Be meant mainly whether this assembly is made up of other assemblies,, then can directly create instance, if dependence is arranged if do not have; Together constituted assembly C like assembly A and assembly B, this moment, the establishment of the example need relate to assembly A and assembly B for assembly C; If the position that answer enquiring component A and assembly B this moment in this locality, then loads from this locality; Or be not, then from before search the node at its place the corresponding relation of assembly and node of storage, and it is inquired about.The processing mode here mainly is exactly in layer, and the assembly that will be in layer building is analyzed, and begins to create instance from the assembly of the bottom, and is quoted by upper component from level to level.
In technique scheme; In step 208, the process of creating instance also comprises: be connected to server node, the sign of the instance that initiation is called on the record server node; And the deployment information corresponding to other assemblies of inquiry storage; Obtain the sign that has the invocation component of call relation with other assemblies,, then create instance for invocation component if there is not the sign of invocation component in the sign of instance.In this technical scheme; The assembly that is positioned at bottom possibly used by a plurality of assemblies; Thereby some assemblies are when quoting, and this bottom assembly possibly be cited and create instance, and this moment, this instance can directly be quoted by assembly afterwards; And, then can by inquiry the time, carry out the establishment of instance for the bottom assembly of not creating instance as yet.Through this inquiry mode, the instance that can avoid having created experiences repetitive operation, simplifies the instance of upper component and creates.
Fig. 4 shows the synoptic diagram of the distributed deployment of assembly according to an embodiment of the invention.
As shown in Figure 4; The distributed deployment of assembly mainly constitutes by disposing managing customer end device 402, deployment management service end device 404 and deploy resources registration center 406 according to an embodiment of the invention; Wherein, dispose managing customer end device 402 and be used for the component project that the exploitation configuration is accomplished is exported as the discernible deployment of components bag of running environment (the present invention adopts OSGI Bundle form), this deployment of components bag can directly be sent on the server node that need be mounted by disposing managing customer end device 402; Also can only generate; Obtain and dispose by disposing management service end device 404 afterwards, simultaneously, dispose managing customer end device 402 and also first deployment information is sent to deploy resources registration center 406; Wherein, Comprise in first deployment information and dispose bag essential information and the contained module information of deployment of components bag, and when deployment managing customer end device 402 directly is sent to node with the deployment of components bag, also comprise server node information in first deployment information.Then; Disposing management service end device 404 is used for the deployment of components bag is deployed in server node; In deployment; For the dynamic assembly of disposing in the bag; The signal that also needs to comprise this dynamic assembly and its server node of being disposed is sent to deploy resources registration center 406 as second deployment information, and when the static component with dependence is carried out the establishment of instance, also need be by disposing management service end device 404 inquiry first deployment information and second deployment information in deploy resources registration center 406.
Fig. 5 shows the process flow diagram of client running according to an embodiment of the invention.
As shown in Figure 5, when carrying out the distributed deployment of assembly, the flow process of client running is following:
Server node information: mainly comprise server node numbering, host node whether, node
Configuration (like the HTTP serve port), information such as management port;
The deployment of components package informatin: essential record is disposed the identification name of bundle, bag version, bag path etc.;
Module configuration information: comprise component identification, bag is disposed in the assembly path under the assembly, component type, and assembly is realized type etc.;
Deployment of components bag and server node related information: comprise deployment of components bag sign, server node sign.
Fig. 6 shows the process flow diagram of the distributed deployment of assembly according to an embodiment of the invention.
As shown in Figure 6, dispose the management service end device when the deployment of components bag is disposed, concrete steps are following:
Step 604 is according to the status attribute of the scanning result determination component of step 602, if static component; Then get into step 606, if dynamic assembly then gets into step 618; Wherein, static component is meant those directly configurable concrete binding informations, directly is activated the assembly that service externally is provided after the deployment; And dynamic assembly is meant that those can't directly dispose binding information, can not create the assembly of instance and startup if the deployment back is not cited.Simultaneously, static component and dynamic assembly are divided into composite component and atom component respectively again.So assembly has following four types altogether: static atom component, set its configuration file expansion scomp by name; Static composite component is set its configuration file expansion icomp by name; Dynamically atom component is set its configuration file expansion comp by name; The dynamic complex assembly is set its configuration file expansion ccomp by name.In addition, dynamically atom component and dynamic complex assembly have only just can create instance accordingly and start when directly or indirectly being used by static composite component and serve.
Step 606 adds OSGI service scan path with component profile.
Inner at composite component A702, dynamically atom component B704 respectively through specific service call dynamic atom component C706 and dynamic complex assembly D708, claim that here dynamic atom component B704 has relied on dynamic atom component C706 and dynamic complex assembly D708.When composite component A702 starts, can start the corresponding service of all component that relies on through analysis to dependence.
In addition, the configuration file of assembly adopts the XML formal definition among the present invention, and the dynamic assembly with first kind of dependence imports through < import>element in configuration file, such as for above-mentioned composite component A702, quotes the part definition as follows:
<import?resource＝″classpath:com/ufida/eip/test/componentB.comp″/>
<import?resource＝″classpath:com/ufida/eip/test/componentC.comp″/>
<import?resource＝″classpath:com/ufida/eip/test/componentD.ccomp″/>
Wherein classpath path " classpath:com/ufida/eip/test/componentB.comp " is the uniqueness path of B assembly 704; Can think the id of B assembly 704; Just can be through this path from the enquiring component configuration of deploy resources registration center, the information such as server node at deployment of components place.
Second kind of dependence then defines through the wire mode, and be same for above-mentioned composite component A702, and calling of 704 pairs of C assemblies 706 of B assembly relies on definition as follows:
Can find out from top definition, the calling of assembly rely on to be through on the related assembly quote with another assembly on service set up.
It is different according to component type to call dependence, can be divided into dynamic-static and call dependence and dynamic-dynamic call dependence, and B704 and C706 are dynamic assembly in the top definition, is dynamic-dynamic call dependence type so B704 relies on calling of C706.
After clear and definite definitions component relied on type and specifically relies on definition, the analysis of component dependencies can adopt current techique to realize, such as the XML analytic technique, Spring IOC technology or the like repeats no more here.The processing of dependence relates to the component instance establishment and starts management, further specifies so be put among Fig. 9.
Step 612 when step 610 is judged as existence dependence assembly, is analyzed the remote component that obtains relying on.
Step 614 is created or is started this remote component instance, and the remote component that obtains for step 612 possibly be dynamic assembly or static component; If dynamic assembly then can directly be created or starts instance, and for static component; The process of its establishment or startup instance will just descend the parsing of one deck, and each static component that occurs afterwards will be handled so all from step 610 beginning again; With the mode of resolving layer by layer, until the assembly that obtains the bottom.
Step 616 if step 610 judges when static component does not have long-range dependence assembly, starts former static component.
Step 618 is registered to deploy resources registration center with the dynamic assembly of judging in the step 604, the server node at registration component place, this be for after by other component call the time, conveniently search.
Fig. 8 shows the block diagram of server node communicator according to an embodiment of the invention.
As shown in Figure 8, server node communicator 800 main charge server inter-node communications are when machine and network break detection; Can support to carry out instance management by assembly.
When server node such as node A startup; Can be through node A contact manager 806 of server node communicator 800 registrations; The contact manager 806 of this node A in case and the contact manager 812 of other nodes such as Node B connect; Needing only Node B or other nodes then occurs when machine or network anomaly; Cross the node communication manager that is connected with it such as the contact manager 806 of node A will obtain notification event, and carry out the cleaning of component instance according to this notification event by other parts such as component instance manager.
When each dynamic assembly starts; The capital is used for the component manager that remote component is managed through the server node communicator to its of server node of disposing registration; Obtain assembly 1 manager 808 and assembly 2 managers 810 as registering respectively with assembly 2 for the assembly 1 at node A place; Obtain assembly 3 managers 814 and assembly 4 managers 816 and understand registration respectively with assembly 4 for the assembly 3 at Node B place; Then as assembly 1 can be through node A contact manager 806 remote access nodes B places assembly 3, through utilization to component manager, thus can establishment, initialization and stop the remote component instance.
Fig. 9 shows according to an embodiment of the invention and to be the process flow diagram of building component instance.
As shown in Figure 9, for the flow process of building component instance following:
Step 902, resolution component configuration file, the formation of analytic unit; Mention static component among Fig. 6 and can be triggered and create instance, and start service, dynamic assembly then can not; Dynamic assembly is only when being relied on by the static component assembling; Just can create corresponding instance, thus the component instance visioning procedure from the most at first, reception be the static component configuration file.
Step 904 judges whether this assembly is made up of other assemblies, that is to say whether this assembly of analysis and other assemblies exist first kind of above-mentioned dependence, then get into step 912 if exist, otherwise, get into step 906.
Step 906 judges whether this assembly is static component, if then get into step 908, otherwise get into step 910.
Step 908 is for this static component is created instance and started static component.
Step 910 is for this dynamic assembly is created the dynamic assembly instance, in Fig. 6; Just carry out information registration etc. for dynamic assembly, also do not start service and neither create instance, and here; Judged that it does not have dependence, and obtained, then directly created instance by the configuration file parsing.
Step 912 to step 928 all is the operation that each the assembly path in the component list that imports is carried out, and wherein, the component list is to judge in the step 904 when being made up of other assemblies, and the identification record of the assembly of participating in constituting is obtained in the component list.
Step 912 loads the assembly that imports through the path in this locality, here owing to the assembly that needs to rely on other, so the assembly that system is relied on can be present in this locality.
Step 914 judges whether this assembly is present in this locality, if, then return step 902, to the status attribute of this assembly with whether depend on other assemblies and resolve, otherwise get into step 916.
Step 916; Judge whether dispose the resource registering center exists relevant information, after generating the deployment bag, dispose the managing customer end device and can send first deployment information to deploy resources registration center; And disposing the management service end device can be when disposing above-mentioned deployment bag; Send second deployment information to deploy resources registration center, thereby can obtain the information of assembly through inquiry to deploy resources registration center.Be being judged as, get into step 920, otherwise get into step 918.
Step 918, the assembly that prompting relies on is issue not, finishes then.
Step 920 to step 926 is for to be deployed with the operation of the server node of this assembly to each.
Step 920, through the remote component manager query aim server node in the server communication device, the communication process here specifies through Fig. 8.
Step 922, whether determination component normally disposes, if normal, then gets into step 926, otherwise gets into step 924.
Step 924, undesired through charging to daily record with the deployment of components on alert management person's server node.
Step 926 is charged to the tabulation of active element deployment information, is meant the assembly that relies on inquiring here, and this assembly is carried out record with the sign of this assembly, and forms effective deployment of components information list by normal deployment.
Step 928 generates remote component instance agency, will combine Figure 10 that the constructive process of remote component instance is analyzed here, and detailed process is following:
Step 930 is created compound static component instance and startup.
Figure 11 shows according to an embodiment of the invention and to be the synoptic diagram of building component instance.
Shown in figure 11, what the component instance visioning procedure mainly utilized is above-mentioned first kind of dependence, solution be the problem of creating component instance as required, do not explain how the binding service on the dynamic assembly instance is activated.Remote component instance management device can effectively solve as required and bind the problem of serving on the start assembly instance based on the type that the calls dependence of assembly forward; Based on assembly reverse call dependence; Problem is restarted in the manual work that causes but the settlement server node configuration changes; Also can solve because lost efficacy because of certain component instance in the whole assembly dependency chain, though other component instances normally move the problem that effective service can't be provided.Describe in detail based on forward and reverse based on Figure 11 below and call the principle of work that the type dependence overcomes the above problems:
Suppose that compound static component S 1102 has relied on dynamic complex assembly A 1104 through above-mentioned first kind of mode, based on the component instance visioning procedure, creates the instance Si of compound static component S 1102; Can create the component instance of composite component A 1104, dynamic atom component B 1106, dynamic atom component C1108 and dynamic complex assembly D 1110 accordingly; Be designated as Ai respectively, Bi, Ci and Di; Wherein
Ai has write down reverse assembling dependence, and { the Si assembling relies on Ai};
Bi has write down reverse assembling dependence, and { the Ai assembling relies on Bi};
Ci has write down reverse assembling dependence, and { the Ai assembling relies on Ci}, and { the Bi assembling relies on Ci} to have write down the reverse calling dependence simultaneously;
Di has write down reverse assembling dependence, and { the Ai assembling relies on Di}, and { the Bi assembling relies on Di} to have write down the reverse calling dependence simultaneously.
Component scans and starter gear start the service S on the Si
S1, service S
S1In fact by service A
S1Provide, claim in the SCA that this service of service implementing really is not provided self is upgrade service (Promoting Service), same A
S1By B
S1Provide, so start S
S1The time can be according to service dependence deactivation B
S1When service started, through the analysis that component call is relied on, i.e. B was quoted in inquiry
R1With quote B
R2The service C that connects respectively
S1And service D
S1, and start C
S1And D
S1If assembly C1108 and assembly D 1110 call equally and rely on to exist, then get final product by handling with the quadrat method recurrence, can effectively separate the problem that the service that never is cited also is activated by this method.
Through above method, effectively the settlement server node configuration changes and problem is restarted in the manual work that causes.If because certain component instance lost efficacy, also be that the analysis through same reverse calling dependence realizes that principle of work is identical in the whole in addition assembly dependency chain, repeat no more here.
More than be described with reference to the accompanying drawings technical scheme of the present invention; Consider in the correlation technique, cause valuable server resource waste easily, and when certain assembly is out of service; Often cause the keeper can restart Servers-all, the service disruption that causes other normally to move.Therefore; The present invention is through having proposed a kind of deployment of components system and a kind of deployment of components method; Can be implemented under the distributed environment assembly that complicated dependence is arranged convenient disposed and to the fine-grained management of instance, realized simultaneously creating as required and starting, avoid influence total system.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. the distributed deployment system of an assembly is characterized in that,
Comprise: client, memory storage and server, wherein,
Said client comprises:
First generation module, the component project formation component that utilizes configuration to accomplish is disposed bag;
First communication module; Be connected to said memory storage; Be used for deployment information is sent to said memory storage, said deployment information comprises the information of information, the related information between a plurality of assembly and said deployment of components bag of information, at least one assembly in the said component project of said component project;
Said memory storage is connected to said client and said server, stores said deployment information;
Said server comprises:
Second communication module is connected to said client, is used to receive said deployment of components bag;
Scan module scans the said deployment of components bag that said second communication module receives, and obtains the status attribute of the assembly in the said deployment of components bag;
Deployment module; In said status attribute is that said assembly is a static component, and said static component is deployed in the corresponding server node under the situation of static state; In said status attribute is under the dynamic situation; Said assembly is a dynamic assembly, and said dynamic assembly is deployed in the corresponding server node, and the corresponding relation of said assembly and said server node is stored in the said memory storage;
Create module, be the building component instance.
2. the distributed deployment system of assembly according to claim 1 is characterized in that, the said first communication module of said client also is used for: said deployment of components bag is sent to server node.
3. the distributed deployment system of assembly according to claim 1 is characterized in that, said server also comprises:
Second generation module, for dynamic assembly generates loader, said loader is used for loading the resource of said dynamic assembly.
4. according to the distributed deployment system of each described assembly in the claim 1 to 3, it is characterized in that said server also comprises:
Parsing module is used for the configuration file of resolution component, and said assembly is carried out first judge; Said first judges to comprise judging whether said assembly is made up of other assemblies, if judged result then is said building component instance for not; If said judged result is then carried out second and judged for being, said second judgement comprises judges whether said other assemblies are positioned at this locality; If said other assemblies are positioned at this locality; Then said other assemblies are carried out said first and judge,, then inquire about the deployment information of said other assemblies of storing in the said memory storage through enquiry module if said other assemblies are not positioned at this locality;
Said enquiry module is used for the deployment information that is stored in said memory storage is inquired about;
Detection module; The said deployment information that inquires according to said enquiry module; Obtain the server node that is deployed with said other assemblies; And test section is deployed on said other assemblies on the said server node whether by normal deployment, if be said other building component instances through said establishment module then.
5. the distributed deployment system of assembly according to claim 4 is characterized in that, before said establishment module is said other building component instances, also comprises:
Said server is connected to said server node through said second communication module; And obtain the sign of the instance that initiation is called on the said server node through said detection module; Be stored in the deployment information in the said memory storage through said enquiry module inquiry then corresponding to said other assemblies; And obtain the sign that has the invocation component of call relation with said other assemblies, and
Said server also comprises comparison module; Said comparison module is used for the sign of more said instance and the sign of said invocation component; If there is not the sign of said invocation component in the sign of said instance, be that said invocation component is created instance then by said establishment module.
6. the distributed deployment method of an assembly is characterized in that, comprising:
Step 202; The component project formation component that utilizes configuration to accomplish is disposed bag; And the storage deployment information, said deployment information comprises the information of information, the related information between a plurality of assembly and said deployment of components bag of information, at least one assembly in the said component project of said component project;
Step 204 scans said deployment of components bag, obtains the status attribute of the assembly in the said deployment of components bag; If said status attribute is static, then said assembly is a static component, and said static component is deployed in the corresponding server node; If said status attribute is dynamic; Then said assembly is a dynamic assembly, and said dynamic assembly is deployed in the corresponding server node, and stores the corresponding relation of said assembly and said server node.
7. the distributed deployment method of assembly according to claim 6 is characterized in that, said step 202 also comprises:
Said deployment of components bag is sent on the server node.
8. the distributed deployment method of assembly according to claim 6 is characterized in that, said step 204 also comprises:
For dynamic assembly generates loader, said loader is used for loading the resource of said dynamic assembly.
9. according to the distributed deployment method of each described assembly in the claim 6 to 8, it is characterized in that, after said step 204, also comprise:
Step 206, the configuration file of resolution component, and said assembly is carried out first judge; Said first judges to comprise judging whether said assembly is made up of other assemblies, if judged result then is said building component instance for not; If said judged result is then carried out second and judged for being, said second judgement comprises judges whether said other assemblies are positioned at this locality; If said other assemblies are positioned at this locality; Then said other assemblies are carried out said first and judge,, then inquire about the deployment information of said other assemblies of storage if said other assemblies are not positioned at this locality;
Step 208, the said deployment information according to said other assemblies obtains the server node that is deployed with said other assemblies, and when detecting said other assemblies that are deployed on the said server node and normally disposed, is said other building component instances.
10. the distributed deployment method of assembly according to claim 9 is characterized in that, in said step 208, the process of said establishment instance also comprises:
Be connected to said server node; Write down the sign of the instance that initiation is called on the said server node; And the deployment information corresponding to said other assemblies of inquiry storage; Obtaining the sign that has the invocation component of call relation with said other assemblies, if there is not the sign of said invocation component in the sign of said instance, then is that said invocation component is created instance.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110295581 CN102360308B (en) | 2011-09-29 | 2011-09-29 | Distributed deployment system and method of components |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110295581 CN102360308B (en) | 2011-09-29 | 2011-09-29 | Distributed deployment system and method of components |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102360308A true CN102360308A (en) | 2012-02-22 |
| CN102360308B CN102360308B (en) | 2013-06-12 |
Family
ID=45585640
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110295581 Active CN102360308B (en) | 2011-09-29 | 2011-09-29 | Distributed deployment system and method of components |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102360308B (en) |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103401900A (en) * | 2013-07-16 | 2013-11-20 | 福建富士通信息软件有限公司 | Rapid deployment application method based on service-oriented architecture |
| CN104036162A (en) * | 2013-03-06 | 2014-09-10 | 株式会社理光 | Delegate access in distributed scan system |
| CN104301167A (en) * | 2013-07-19 | 2015-01-21 | 方正宽带网络服务股份有限公司 | Monitoring device and method |
| CN104615466A (en) * | 2015-02-05 | 2015-05-13 | 广州亦云信息技术有限公司 | Cloud platform deployment method and system |
| CN104765621A (en) * | 2014-01-02 | 2015-07-08 | 国际商业机器公司 | Method and system for deploying program on cluster node |
| CN104765620A (en) * | 2014-01-02 | 2015-07-08 | 国际商业机器公司 | Programming module deploying method and system |
| CN104915185A (en) * | 2014-03-11 | 2015-09-16 | 腾讯科技（深圳）有限公司 | Coupling processing method for program components and related device |
| CN105022626A (en) * | 2015-05-29 | 2015-11-04 | 克拉玛依红有软件有限责任公司 | Model driving based dynamic interaction system and method utilizing reflection mechanism |
| CN105431823A (en) * | 2013-05-31 | 2016-03-23 | 沃德尔有限公司 | Environmentalization technique for promotion of application programming interface (api) server in lifecycle succession of deployments |
| CN105933155A (en) * | 2016-05-26 | 2016-09-07 | 华为软件技术有限公司 | Device and method for controlling server upgrade |
| CN106547600A (en) * | 2016-11-22 | 2017-03-29 | 郑州云海信息技术有限公司 | A kind of remote auto installs the method and system of whole machine cabinet host operating system |
| CN106888233A (en) * | 2015-12-15 | 2017-06-23 | 北京新媒传信科技有限公司 | Data update system and method |
| CN107391528A (en) * | 2016-03-30 | 2017-11-24 | 阿里巴巴集团控股有限公司 | Front end assemblies Dependency Specification searching method and equipment |
| CN107438107A (en) * | 2017-09-05 | 2017-12-05 | 深圳乐信软件技术有限公司 | The call method and device of background service in a kind of micro services framework |
| CN107885501A (en) * | 2017-11-03 | 2018-04-06 | 武汉斗鱼网络科技有限公司 | Obtain the method and device of the mutual adduction relationship of component in Android |
| CN109086051A (en) * | 2018-06-29 | 2018-12-25 | 平安科技（深圳）有限公司 | Application component dispositions method, device and computer storage medium |
| CN109088774A (en) * | 2018-08-28 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method and device of distributed system deployment |
| CN109933406A (en) * | 2019-02-11 | 2019-06-25 | 平安科技（深圳）有限公司 | Method and relevant device based on compatibility adjustment Docker deployment of components |
| CN110413286A (en) * | 2019-07-31 | 2019-11-05 | 阿里巴巴集团控股有限公司 | A kind of application dispositions method, device and equipment |
| CN110764883A (en) * | 2018-07-26 | 2020-02-07 | 浙江宇视科技有限公司 | Start-stop control method and device for service group |
| CN111240739A (en) * | 2020-01-21 | 2020-06-05 | 烽火通信科技股份有限公司 | Dynamic concurrent distribution method and system for associated attributes of objects |
| CN111309474A (en) * | 2020-01-19 | 2020-06-19 | 北京恒华伟业科技股份有限公司 | Communication method, communication device and distributed service registration center |
| CN111596898A (en) * | 2020-05-08 | 2020-08-28 | 湖南智领通信科技有限公司 | SCA subassembly and server based on CORBA subassembly |
| CN111913721A (en) * | 2020-07-16 | 2020-11-10 | 中国民航信息网络股份有限公司 | Automatic deployment method, device, equipment and storage medium |
| CN112558949A (en) * | 2020-12-21 | 2021-03-26 | 长沙树根互联技术有限公司 | Program construction method, program construction device, electronic device, and storage medium |
| CN113127271A (en) * | 2021-04-01 | 2021-07-16 | 深圳华锐金融技术股份有限公司 | Transaction system deployment method and device, computer equipment and storage medium |
| CN115543546A (en) * | 2022-11-25 | 2022-12-30 | 金现代信息产业股份有限公司 | Spring-based module heat deployment method and system |
| WO2024021467A1 (en) * | 2022-07-26 | 2024-02-01 | 天翼云科技有限公司 | Cluster resource planning method, device, apparatus, and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001065422A2 (en) * | 2000-02-28 | 2001-09-07 | Cadence Design Systems, Inc. | Method and system for facilitating electronic circuit and chip design using remotely located resources |
| WO2001095100A1 (en) * | 2000-06-06 | 2001-12-13 | Emware, Inc. | Service provider for providing data, applications and services to embedded devices and for facilitating control |
| WO2003007092A2 (en) * | 2001-07-13 | 2003-01-23 | Siemens Aktiengesellschaft | Data capture for electronically delivered automation services |
| WO2004027608A2 (en) * | 2002-09-16 | 2004-04-01 | Siemens Aktiengesellschaft | System for preparing a standard framework for automation appliances |
| EP1416400A2 (en) * | 2002-11-04 | 2004-05-06 | Siemens Aktiengesellschaft | System and method for providing data and services to devices over public networks, and device using said provided data and services |
-
2011
- 2011-09-29 CN CN 201110295581 patent/CN102360308B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001065422A2 (en) * | 2000-02-28 | 2001-09-07 | Cadence Design Systems, Inc. | Method and system for facilitating electronic circuit and chip design using remotely located resources |
| WO2001095100A1 (en) * | 2000-06-06 | 2001-12-13 | Emware, Inc. | Service provider for providing data, applications and services to embedded devices and for facilitating control |
| WO2003007092A2 (en) * | 2001-07-13 | 2003-01-23 | Siemens Aktiengesellschaft | Data capture for electronically delivered automation services |
| WO2004027608A2 (en) * | 2002-09-16 | 2004-04-01 | Siemens Aktiengesellschaft | System for preparing a standard framework for automation appliances |
| EP1416400A2 (en) * | 2002-11-04 | 2004-05-06 | Siemens Aktiengesellschaft | System and method for providing data and services to devices over public networks, and device using said provided data and services |
Cited By (48)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104036162A (en) * | 2013-03-06 | 2014-09-10 | 株式会社理光 | Delegate access in distributed scan system |
| CN104036162B (en) * | 2013-03-06 | 2016-09-14 | 株式会社理光 | A kind of scanning means |
| CN105431823A (en) * | 2013-05-31 | 2016-03-23 | 沃德尔有限公司 | Environmentalization technique for promotion of application programming interface (api) server in lifecycle succession of deployments |
| CN105431823B (en) * | 2013-05-31 | 2021-06-29 | 沃德尔有限公司 | Managing a series of deployments of an Application Programming Interface (API) server configuration in a software lifecycle deployment |
| CN103401900A (en) * | 2013-07-16 | 2013-11-20 | 福建富士通信息软件有限公司 | Rapid deployment application method based on service-oriented architecture |
| CN104301167A (en) * | 2013-07-19 | 2015-01-21 | 方正宽带网络服务股份有限公司 | Monitoring device and method |
| CN104301167B (en) * | 2013-07-19 | 2018-09-04 | 方正宽带网络服务股份有限公司 | A kind of monitoring device and method |
| CN104765621A (en) * | 2014-01-02 | 2015-07-08 | 国际商业机器公司 | Method and system for deploying program on cluster node |
| CN104765620A (en) * | 2014-01-02 | 2015-07-08 | 国际商业机器公司 | Programming module deploying method and system |
| CN104765620B (en) * | 2014-01-02 | 2018-01-26 | 国际商业机器公司 | A kind of method and system of program module deployment |
| CN104765621B (en) * | 2014-01-02 | 2018-05-01 | 国际商业机器公司 | A kind of method and system of the deployment program in clustered node |
| CN104915185A (en) * | 2014-03-11 | 2015-09-16 | 腾讯科技（深圳）有限公司 | Coupling processing method for program components and related device |
| CN104915185B (en) * | 2014-03-11 | 2019-04-02 | 腾讯科技（深圳）有限公司 | Program assembly coupled processing method and relevant apparatus |
| CN104615466B (en) * | 2015-02-05 | 2017-08-25 | 广州亦云信息技术有限公司 | A kind of cloud platform dispositions method and system |
| CN104615466A (en) * | 2015-02-05 | 2015-05-13 | 广州亦云信息技术有限公司 | Cloud platform deployment method and system |
| CN105022626A (en) * | 2015-05-29 | 2015-11-04 | 克拉玛依红有软件有限责任公司 | Model driving based dynamic interaction system and method utilizing reflection mechanism |
| CN105022626B (en) * | 2015-05-29 | 2018-08-03 | 克拉玛依红有软件有限责任公司 | The system and method that dynamic interaction is carried out using reflex mechanism based on model-driven |
| CN106888233A (en) * | 2015-12-15 | 2017-06-23 | 北京新媒传信科技有限公司 | Data update system and method |
| CN106888233B (en) * | 2015-12-15 | 2019-12-24 | 北京新媒传信科技有限公司 | Data updating system and method |
| CN107391528B (en) * | 2016-03-30 | 2021-04-20 | 阿里巴巴集团控股有限公司 | Front-end component dependent information searching method and equipment |
| CN107391528A (en) * | 2016-03-30 | 2017-11-24 | 阿里巴巴集团控股有限公司 | Front end assemblies Dependency Specification searching method and equipment |
| CN105933155B (en) * | 2016-05-26 | 2019-06-11 | 华为软件技术有限公司 | The device and method of control server upgrading |
| CN105933155A (en) * | 2016-05-26 | 2016-09-07 | 华为软件技术有限公司 | Device and method for controlling server upgrade |
| CN106547600A (en) * | 2016-11-22 | 2017-03-29 | 郑州云海信息技术有限公司 | A kind of remote auto installs the method and system of whole machine cabinet host operating system |
| CN107438107B (en) * | 2017-09-05 | 2021-07-27 | 深圳乐信软件技术有限公司 | Method and device for calling background service in micro-service architecture |
| CN107438107A (en) * | 2017-09-05 | 2017-12-05 | 深圳乐信软件技术有限公司 | The call method and device of background service in a kind of micro services framework |
| CN107885501B (en) * | 2017-11-03 | 2020-09-08 | 武汉斗鱼网络科技有限公司 | Method and device for obtaining mutual reference relationship of components in Android |
| CN107885501A (en) * | 2017-11-03 | 2018-04-06 | 武汉斗鱼网络科技有限公司 | Obtain the method and device of the mutual adduction relationship of component in Android |
| CN109086051B (en) * | 2018-06-29 | 2022-03-25 | 平安科技（深圳）有限公司 | Application component deployment method and device and computer storage medium |
| CN109086051A (en) * | 2018-06-29 | 2018-12-25 | 平安科技（深圳）有限公司 | Application component dispositions method, device and computer storage medium |
| WO2020000811A1 (en) * | 2018-06-29 | 2020-01-02 | 平安科技（深圳）有限公司 | Application component deployment method and apparatus, and computer storage medium |
| CN110764883A (en) * | 2018-07-26 | 2020-02-07 | 浙江宇视科技有限公司 | Start-stop control method and device for service group |
| CN109088774A (en) * | 2018-08-28 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method and device of distributed system deployment |
| CN109933406A (en) * | 2019-02-11 | 2019-06-25 | 平安科技（深圳）有限公司 | Method and relevant device based on compatibility adjustment Docker deployment of components |
| CN109933406B (en) * | 2019-02-11 | 2021-07-16 | 平安科技（深圳）有限公司 | Method for adjusting Docker component deployment based on affinity and related equipment |
| CN110413286A (en) * | 2019-07-31 | 2019-11-05 | 阿里巴巴集团控股有限公司 | A kind of application dispositions method, device and equipment |
| CN110413286B (en) * | 2019-07-31 | 2023-08-22 | 创新先进技术有限公司 | Application deployment method, device and equipment |
| CN111309474A (en) * | 2020-01-19 | 2020-06-19 | 北京恒华伟业科技股份有限公司 | Communication method, communication device and distributed service registration center |
| CN111309474B (en) * | 2020-01-19 | 2023-05-12 | 北京恒华伟业科技股份有限公司 | Communication method, communication device and distributed service registration center |
| CN111240739A (en) * | 2020-01-21 | 2020-06-05 | 烽火通信科技股份有限公司 | Dynamic concurrent distribution method and system for associated attributes of objects |
| CN111240739B (en) * | 2020-01-21 | 2022-04-15 | 烽火通信科技股份有限公司 | Dynamic concurrent distribution method and system for associated attributes of objects |
| CN111596898A (en) * | 2020-05-08 | 2020-08-28 | 湖南智领通信科技有限公司 | SCA subassembly and server based on CORBA subassembly |
| CN111596898B (en) * | 2020-05-08 | 2024-01-30 | 湖南智领通信科技有限公司 | SCA component based on CORBA component and server |
| CN111913721A (en) * | 2020-07-16 | 2020-11-10 | 中国民航信息网络股份有限公司 | Automatic deployment method, device, equipment and storage medium |
| CN112558949A (en) * | 2020-12-21 | 2021-03-26 | 长沙树根互联技术有限公司 | Program construction method, program construction device, electronic device, and storage medium |
| CN113127271A (en) * | 2021-04-01 | 2021-07-16 | 深圳华锐金融技术股份有限公司 | Transaction system deployment method and device, computer equipment and storage medium |
| WO2024021467A1 (en) * | 2022-07-26 | 2024-02-01 | 天翼云科技有限公司 | Cluster resource planning method, device, apparatus, and medium |
| CN115543546A (en) * | 2022-11-25 | 2022-12-30 | 金现代信息产业股份有限公司 | Spring-based module heat deployment method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102360308B (en) | 2013-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102360308B (en) | Distributed deployment system and method of components | |
| CN101192937B (en) | A hot deployable method and its system | |
| Wohed et al. | Pattern based analysis of BPEL4WS | |
| EP1526457B1 (en) | Context-aware automatic service discovery and execution engine in mobile ad-hoc networks | |
| CN101051977B (en) | Active intervention in service-to-device mapping for smart items | |
| US8661410B2 (en) | Managed enterprise software components as dynamic services | |
| JP4461109B2 (en) | Dynamic component management | |
| CN100442233C (en) | Method and system for implementing dynamic upgrade of application system | |
| CN102436373B (en) | Method for realizing resource loading and resource hot-updating in distributed enterprise application system | |
| US8856734B2 (en) | Type-safe dependency injection of services into enterprise components | |
| JP2007157133A (en) | Hierarchical, multi-tiered mapping and monitoring architecture for smart items | |
| CN102037677B (en) | Computer readable medium, northbound interface uniform platform and starting method thereof | |
| US20080059940A1 (en) | System and method for implementing a safe framework | |
| CN101427220A (en) | Componentized automatic provisioning and management of computing environments for computing utilities | |
| CN110196731A (en) | A kind of operational system, method and storage medium | |
| CN103942055A (en) | Development system and method for fusion network mixing service process programming language | |
| US6658644B1 (en) | Services-based architecture for a telecommunications enterprise | |
| CN102375734A (en) | Application product development system, method and device and operation system, method and device | |
| CN100596139C (en) | System and method for building component applications using metadata defined mapping between message and data domains | |
| Ketfi et al. | Automatic adaptation of component-based software | |
| CN111736809A (en) | Distributed robot cluster network management framework and implementation method thereof | |
| Rademacher et al. | Specific model-driven microservice development with interlinked modeling languages | |
| US20080059949A1 (en) | System and method for implementing a safe framework | |
| CN102272720A (en) | Service providing device, service providing system, service providing method, and storage medium | |
| CN110069276B (en) | Micro-service demand driving method oriented to open dynamic Internet environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee |
Owner name: YONYOU NETWORK TECHNOLOGY CO., LTD. Free format text: FORMER NAME: UFIDA SOFTWARE CO., LTD. |
|
| CP03 | Change of name, title or address |
Address after: 100094 Haidian District North Road, Beijing, No. 68 Patentee after: Yonyou Network Technology Co., Ltd. Address before: 100094 Beijing city Haidian District North Road No. 68, UFIDA Software Park Patentee before: UFIDA Software Co., Ltd. |