CN101179414A - Method of integrating lower network management function in higher network management - Google Patents
Method of integrating lower network management function in higher network management Download PDFInfo
- Publication number
- CN101179414A CN101179414A CNA200610063558XA CN200610063558A CN101179414A CN 101179414 A CN101179414 A CN 101179414A CN A200610063558X A CNA200610063558X A CN A200610063558XA CN 200610063558 A CN200610063558 A CN 200610063558A CN 101179414 A CN101179414 A CN 101179414A
- Authority
- CN
- China
- Prior art keywords
- plug
- unit
- space
- network management
- subordinate
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The invention relates to a method for integrating the function of a lower network management system in an upper network management system. The independent plug-ins which the functional modules on the client of the lower network management system are made into one by one are deployed on the client of the upper network management system so as to result in that the plug-ins are contained in the spaces which are each independent. Various plug-ins in the space are loaded into the Java process by adopting an independent class loader in each independent space and the function management interface for configuring the plug-ins is opened to carry out the management operation on the function management interface for plug-ins; the sent command calling request is forwarded to a lower network management server through an upper network management server after being processed. The invention can deliver the support for running the lower network management functioning parts of different versions on the upper network management system and implement the centralized operation and maintenance in the upper network management system, and the upper network management system can implement the function of the lower network management system without needing to increase the development workload.
Description
Technical field
The present invention relates to a kind of management method of the network equipment, relate in particular to a kind of in Upper NM Station the method for integrating lower network management function.
Background technology
The telecommunication network management technology is the complicated distributed system, and Java technology particularly J2EE has also obtained considerable application in telecommunicatioin network management.For whole network equipment is managed, the general method that webmaster is carried out differentiated control that adopts: subordinate's webmaster (OMM) is managed network element directly, finishes the single point of management to network element; Upper NM Station (EMS) is realized the centralized management to each OMM, sees that 1, one Upper NM Station EMS of accompanying drawing has managed three webmaster OMM of subordinate, so just can check and monitors at the equipment to following three webmasters that the Upper NM Station client can be concentrated.
Development along with telecommunications industry, Carrier Requirements provides the integrated management ability to the network equipment to become more and more important, management function on the EMS no longer has been confined to and can only have checked and monitor what the OMM of each subordinate concentrated, but require the various operational administrative functions on the OMM webmaster to wait and can both on EMS, have as configuration, to reach the purpose that function does not lack on EMS.
Therefore, concentrating on original higher level EMS webmaster on the basis check with monitoring function, if the direct function of integrating lower OMM webmaster in Upper NM Station, so as can direct control on higher level EMS webmaster, the management equipment of configuration subordinate webmaster, more can satisfy the needs of the network management that becomes increasingly complex.
Traditional solution mainly is following two kinds:
1, developing the function of a cover on the OMM on the EMS again, comprising that client functionality and server capability all will develop again.
2, need not code newly developed, just the client full release of each OMM is all deposited portion on EMS, when needs carry out operative configuration to certain OMM, just start this OMM clients corresponding version process, this process oneself is linked this OMM server, and all operating functions are all finished on the interface of this process.
There is following problem in these two kinds of solutions:
If 1 function on OMM newly developed on the EMS, owing to will adapt to different types of OMM, the development amount is huge incomparable, and along with OMM self edition upgrading and increased functionality, also need EMS to go up code newly developed and also write and revise new code, cause the version coupling of EMS and OMM too tight along with OMM.Main problem be exactly the construction cycle long, maintenance cost is big, far can not adapt to the purpose in the quick release market of Carrier Requirements.
If 2 all start an independently method of client process in the EMS client to each OMM that will connect, each independently process to login, process such as initialization, toggle speed is slow, and need the user between the operation interface of different processes, to switch, make user's impression have a greatly reduced quality; And the operation interface of each client process is independently, and this basic goal that runs counter to EMS is the Operation and Maintenance and the management of concentrating; Also have, IP path between the superior and the subordinate's network management system is subjected to special control, can only be that special passage is arranged between the superior and the subordinate's server, and often can't be directly with the communication of the OMM of subordinate NM server at parent customer terminal device, therefore unacceptable on engineering is disposed.
In the present invention, Upper NM Station (EMS) has comprised Upper NM Station client and Upper NM Station server; Subordinate's webmaster (OMM) comprises subordinate's NM client and subordinate's NM server.The user directly brings in the client of higher level or subordinate's webmaster the equipment operation situation is monitored.Present trend is, customer requirements can directly just can be monitored the equipment that subordinate's webmaster is managed on the Upper NM Station client, and the user on provincial webmaster (be concentrate EMS Upper NM Station) can directly manage and operate the equipment that is distributed in each local city-level webmaster (being the OMM webmaster).
Summary of the invention
The technical problem to be solved in the present invention is, a kind of method that increases subordinate's network management function in Upper NM Station is proposed, be implemented in the function that integrated each subordinate's webmaster on the Upper NM Station client has been realized, make it in the same Java process of Upper NM Station client, be disposed and to move.
The present invention includes following steps:
Step 1, make one by one independently that plug-in unit is deployed on Upper NM Station (EMS) client to the functional module on subordinate's webmaster (OMM) client;
Step 2, described plug-in unit is included in one by one independently in the space, each independently the space all adopt one independently Classloader each plug-in unit in this space is loaded in the Java process;
Step 3, the function management interface of opening configuration plug-in;
Step 4, the function management interface of plug-in unit is managed operation;
Step 5, to send command calls request processing back by Upper NM Station (EMS) server forwards to subordinate's webmaster (OMM) server.
In the such scheme, described plug-in unit exists with the form of compressed package or exists with the form of catalogue.
The location mode that interposer lies in the described step 1 is deployed to Upper NM Station (EMS) client is: ready-made plug-in unit is put under the specific directory finds this plug-in unit automatically by system; Or the plug-in unit placement anywhere, and write a plug-in unit threaded file to describe the particular location of this plug-in unit, read described threaded file by system and find this plug-in unit.
Separate space in the described step 2 comprises the principal space and domain space, can load one or more plug-in units in each domain space, and corresponding to subordinate's webmaster (OMM), is separate between the domain space.The principal space is used for management domain space life cycle, and it provides infrastructural support for the operation of domain space, comprises load domain space and unloading domain space.
Described Classloader is the method that each plug-in unit in this space is loaded in the Java process that when needs loaded the bytecode of a class, whether inquiry had such bytecode in domain space earlier, just uses this bytecode if having; Otherwise just use the default Classloader of the principal space to load.
The function management interface of opening configuration plug-in in the described step 3 is meant each plug-in unit that is comprised in the load domain space, and implementation method may further comprise the steps: an example creating the domain space Classloader; Read the domain space descriptor file and obtain all plug-in units that this space comprises; Use the example of this domain space Classloader to load class in these plug-in units; Various resource files in the scanning plug-in unit are just composed it when plug-in unit will read resource file and are given plug-in unit.
When not re-using domain space, it is stopped, discharging shared memory source.
Described step 4 is carried out the bookkeeping of data configuration, may further comprise the steps: order that issues and parameter are packaged into byte stream; Byte stream is delivered to the Upper NM Station server; After receiving, the Upper NM Station server is forwarded to subordinate's NM server; On subordinate's NM server, again byte stream is reduced into original data or order is handled; Subordinate's NM server is handled the data that the back is returned needs, the form that also is processed into byte stream returns to the Upper NM Station server, return to again at last in Upper NM Station (EMS) client process in the corresponding domain space, present to the user being shown to after the reduction of result's bytes of stream data on the interface that domain space opens.
By such scheme, can reach following beneficial effect:
1, higher level EMS webmaster is to the zero development amount of the OMM of subordinate function.The function that has had on the OMM of the subordinate webmaster need not developed a cover again on EMS, these functions that had only need be made independently plug-in unit and be deployed to EMS and go up and get final product, and this can farthest utilize existing development, releases market fast.
2, the decoupling zero of higher level EMS webmaster version and the OMM of subordinate webmaster version.Move because the function of the OMM of subordinate is integrated among the higher level EMS by plug-in unit, which type of function EMS provides needn't understand fully for OMM, has removed the dependence of version between EMS and the OMM.
3, higher level EMS webmaster has been realized the Operation and Maintenance of concentrating.Because the plug-in unit of each OMM subordinate webmaster correspondence is to be integrated in the same Java process of EMS to move, toggle speed is fast, avoided the user between different process interfaces, to switch back and forth, realize the target of the centralized operation maintenance that EMS must reach, promoted the impression of operating user interface greatly.
4, support moves the OMM function of different editions simultaneously on the higher level EMS.The OMM function of these different editions, their class name, bag name all are identical, obviously adopt traditional class load mode can not accomplish to be loaded simultaneously in same process; But in the present invention, these OMM functional modules are respectively by different plug-in unit carryings, each plug-in unit all by one independently Classloader load, this makes them be in after being loaded independently in the space, influence without any association each other, therefore accomplished the process that in same JVM (JavaVirtual Machine, i.e. Java virtual machine) process, is loaded.
Description of drawings:
Fig. 1 is the higher level EMS management OMM of a subordinate schematic diagram;
Fig. 2 is the order diversion treatments flow chart in the domain space among the present invention.
Embodiment:
Basic design philosophy of the present invention is to make one by one independently that plug-in unit is deployed on the EMS client to the functional module on the OMM client, these plug-in units are included in one by one independently in the space, each independently the space all adopt one independently Classloader each plug-in unit in this space be loaded in the Java process move; These plug-in units send the command calls request and tackle when moving, pass through the EMS server forwards to the OMM of subordinate server through the processing back.
" plug-in unit " among the present invention is meant the physics realization of finishing one or more network management functions, the set that organizes together according to the principle of Module Division.This physics realization comprises: the .class file that this function code compiles out, and generally the form of wrapping with jar exists; The used various data resources of this function, for example XML file resource, property file resource, picture file resource, audio files resource etc.Plug-in unit is self-described, and promptly this plug-in unit itself is with describing the resource of this plug-in unit self information, and for example the XML descriptor is described the jar bag that oneself comprises those Java, had which resource etc., the information of description to comprise title, version information, plug-in unit supplier etc.Plug-in unit can be loaded dynamically and be activated.Plug-in unit can exist with the form of compressed package, also can exist with the form of catalogue.
" domain space " among the present invention, " principal space ": owing to may manage the relevant function interface of a plurality of OMM of subordinate webmasters on the EMS client simultaneously, must be separate between these functions, can not influence each other.Therefore, must allow these functions operate in separately independently in the environment, this environment just is called " domain space ".Domain space is the container that plug-in unit loads and moves, and a domain space can load one or more plug-in units, and corresponding to the OMM of a subordinate webmaster.Domain space has the process of life cycle: after having loaded domain space, just can use the function of each plug-in unit in this domain space; After having unloaded domain space, the function of each plug-in unit in this domain space of also just having stopped using." principal space " is exactly to be used for management domain space life cycle, and it provides infrastructural support for the operation of domain space.The principal space and domain space all operate in the same Java process.
Below the present invention is further introduced:
See also shown in Figure 2:
The first step generates plug-in unit
All relevant physics realizations of the configuration feature on the OMM, comprise that jar, picture resource and configuration file etc. after the code compiling are combined under the catalogue, again this catalogue being compressed into one is in the file of suffix with .par, and the file of this compression is exactly a plug-in unit.Each function that is integrated into higher level EMS client according to the OMM of subordinate client needs generates a plurality of independently plug-in units.Wherein, a plug-in unit is finished a function.
The existence form of plug-in unit can be compressed file, also can be catalogue.In this embodiment, plug-in unit mainly exists with the form of catalogue, the time of the cost of can avoiding like this decompressing when loading of plug-in, improves toggle speed.Plug-in unit is named in the mode of standard usually, and this plug-in unit must be that the mode of suffix is named with .par in this embodiment, and this plug-in unit is an example with the plug-in unit of configuration feature, names into zte-cdyjs-cm.par.
Second step: dispose plug-in unit
Ready-made plug-in unit is put into the machine at EMS client place.Deposited dual mode, the one, ready-made plug-in unit is put under the specific directory, system will find this plug-in unit automatically; Another kind is that plug-in unit is placed anywhere, and writes a plug-in unit threaded file to describe the particular location of this plug-in unit, and system will read this file and find this plug-in unit.In the present embodiment, this configuration feature plug-in unit is left under the EMS client fixed schedule c:/zte/ums-clnt.
The 3rd step: spatialization plug-in unit.
Each OMM of the subordinate webmaster that will manage all uses an independently domain space, and the plug-in unit of the OMM of this subordinate network management function is covered in this domain space, and each domain space uses a descriptor file to describe the plug-in unit that will comprise.In concrete enforcement, can name a domain space " zxom01-ss ", and adopt text editor or XML instrument to write a domain space descriptor file, top configuration feature plug-in unit is included in this domain space.
The key of spatialization is to use an independently Classloader in each domain space, is called the domain space Classloader, the bytecode of each java class in the special load domain space.The Key Implementation method that class loads is: when needs loaded the bytecode of a class, whether inquiry had such bytecode in domain space earlier, just uses this bytecode if having; Otherwise just use the default Classloader of the principal space to load.
In this example, have only this configuration feature plug-in unit in the domain space, this Classloader just is responsible for loading the bytecode of all classes in this plug-in unit.And the class of some other public function has existed in the principal space, and does not have its bytecode in plug-in unit, so these classes are shared use.
The 4th step: start domain space
The result who starts domain space in the present embodiment is exactly the network management function interface of opening the configuration management plug-in unit, and implementation step is:
1, creates an example of domain space Classloader;
2, read the domain space descriptor file and obtain the configuration feature plug-in unit that this domain space comprises;
3, use the example of this domain space Classloader to load class in the configuration feature plug-in unit;
4, the various resource files in the scanning configuration feature plug-in unit, and be saved in a results list;
5, the configuration feature plug-in unit will read the picture resource file in being loaded process, just obtains from the scanning result tabulation.
If the user closes this configuration management interface, then this domain space is stopped, the memory source of this domain space release busy this moment.
Relation between above-mentioned the 3rd step and the 4th step is that third step is finished the establishment of domain space Classloader; The 4th step was carried out loading procedure.
The 5th step: order diversion treatments
After the function interface of the configuration management of the OMM of subordinate is opened, promptly at the interface operation that carries out data configuration, for the order of data configuration and parameter are issued on the OMM of the subordinate server, need carry out as the diversion treatments of issuing orders the command calls process, flow process as shown in Figure 2:
1, domain space issues the order and the parameter of data configuration;
2, the EMS client converts this data configuration order and parameter to byte stream, and the mode of conversion generally adopts the mode of Java serializing according to the type of order and parameter.
3, this byte stream is passed to the EMS server;
4, the EMS server is forwarded to former state the OMM of subordinate server after receiving this byte stream again;
5, this OMM server is reduced into initial data configure order and parameter with this byte stream;
6, the OMM server is given the configuration feature module with the order of this data configuration and parameter and is handled, and concurrent parameter is issued on the network element.
7, the data of after the OMM server will be handled needs being returned are as disposing back network element object, and the form that is processed into byte stream returns to the EMS server;
8, the EMS server with this as a result byte stream return to the EMS client,
9, this EMS client with this as a result byte stream pass in the process in the corresponding domain space;
10, this domain space is shown to after with the reduction of this result's bytes of stream data on the interface that domain space opens and presents to the user.
In above-mentioned introduction, the result of order and parameter and processing is converted to byte stream, be because they may be the objects of java class, owing to will carry out transfer by the EMS server, can cause can not find the java class of correspondence on the EMS server and failing if directly issue object.
Claims (8)
1. method that increases subordinate's network management function in Upper NM Station may further comprise the steps:
Step 1, make one by one independently that plug-in unit is deployed on Upper NM Station (EMS) client to the functional module on subordinate's webmaster (OMM) client;
Step 2, described plug-in unit is included in one by one independently in the space, each independently the space all adopt one independently Classloader each plug-in unit in this space is loaded in the Java process;
Step 3, the function management interface of opening configuration plug-in;
Step 4, the function management interface of plug-in unit is managed operation;
Step 5, to send command calls request processing back by Upper NM Station (EMS) server forwards to subordinate's webmaster (OMM) server.
2. the described method that increases subordinate's network management function in Upper NM Station of claim 1 is characterized in that, described plug-in unit exists with the form of compressed package or exists with the form of catalogue.
3. the described method that in Upper NM Station, increases subordinate's network management function of claim 1, it is characterized in that the location mode that described interposer lies is deployed to Upper NM Station (EMS) client is: ready-made plug-in unit is put under the specific directory finds this plug-in unit automatically by system; Or the plug-in unit placement anywhere, and write a plug-in unit threaded file to describe the particular location of this plug-in unit, read described threaded file by system and find this plug-in unit.
4. the described method that in Upper NM Station, increases subordinate's network management function of claim 1, it is characterized in that, separate space in the described step 2 comprises the principal space and domain space, can load one or more plug-in units in each domain space, and, be separate between the domain space corresponding to subordinate's webmaster (OMM).The principal space is used for management domain space life cycle, and it provides infrastructural support for the operation of domain space, comprises load domain space and unloading domain space.
5. the described method that in Upper NM Station, increases subordinate's network management function of claim 4, it is characterized in that, Classloader is the method that each plug-in unit in this space is loaded in the Java process, when needs load the bytecode of a class, whether inquiry has such bytecode in domain space earlier, just uses this bytecode if having; Otherwise just use the default Classloader of the principal space to load.
6. the described method that increases subordinate's network management function in Upper NM Station of claim 5 is characterized in that the function management interface of opening configuration plug-in in the described step 3 is meant each plug-in unit that is comprised in the load domain space, and implementation method may further comprise the steps:
Create an example of domain space Classloader;
Read the domain space descriptor file and obtain all plug-in units that this space comprises;
Use the example of this domain space Classloader to load class in these plug-in units;
Various resource files in the scanning plug-in unit are just composed it when plug-in unit will read resource file and are given plug-in unit.
7. the described method that increases subordinate's network management function in Upper NM Station of claim 6 is characterized in that, when not re-using domain space it is stopped, and discharges shared memory source.
8. the described method that increases subordinate's network management function in Upper NM Station of the arbitrary claim of claim 1 to 7 is characterized in that described step 4 is carried out the bookkeeping of data configuration, may further comprise the steps:
Order that issues and parameter are packaged into byte stream;
Byte stream is delivered to the Upper NM Station server;
After receiving, the Upper NM Station server is forwarded to subordinate's NM server;
On subordinate's NM server, again byte stream is reduced into original data or order is handled;
Subordinate's NM server is handled the data that the back is returned needs, the form that also is processed into byte stream returns to the Upper NM Station server, return to again at last in Upper NM Station (EMS) client process in the corresponding domain space, present to the user being shown to after the reduction of result's bytes of stream data on the interface that domain space opens.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610063558XA CN100571156C (en) | 2006-11-09 | 2006-11-09 | A kind of in Upper NM Station the method for integrating lower network management function |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610063558XA CN100571156C (en) | 2006-11-09 | 2006-11-09 | A kind of in Upper NM Station the method for integrating lower network management function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101179414A true CN101179414A (en) | 2008-05-14 |
| CN100571156C CN100571156C (en) | 2009-12-16 |
Family
ID=39405514
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200610063558XA Expired - Fee Related CN100571156C (en) | 2006-11-09 | 2006-11-09 | A kind of in Upper NM Station the method for integrating lower network management function |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100571156C (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826985A (en) * | 2010-04-20 | 2010-09-08 | 中兴通讯股份有限公司 | Plugin-based centralized signaling tracing method and system |
| CN101938376A (en) * | 2010-09-08 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for realizing function use of administrator client |
| WO2012024819A1 (en) * | 2010-08-26 | 2012-03-01 | 广州客多软件科技有限公司 | User information sharing method and system for client ends |
| CN102421113A (en) * | 2011-11-28 | 2012-04-18 | 中兴通讯股份有限公司 | Method and device for realizing multi-site operation by embedding multiple LMTs (Local Maintenance Terminals) into centralized network manager |
| CN102752517A (en) * | 2011-05-16 | 2012-10-24 | 新奥特（北京）视频技术有限公司 | Integrated management method and device for plugins of subtitle system |
| CN104468172A (en) * | 2013-09-25 | 2015-03-25 | 中兴通讯股份有限公司 | Acquisition adapter management method and system |
| CN106406834A (en) * | 2015-07-30 | 2017-02-15 | 中兴通讯股份有限公司 | Method, device and system for managing application system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6349333B1 (en) * | 1998-12-04 | 2002-02-19 | Sun Microsystems, Inc. | Platform independent alarm service for manipulating managed objects in a distributed network management system |
| CN100365568C (en) * | 2004-01-06 | 2008-01-30 | 英业达股份有限公司 | Method for realizing Java small-application plug board function |
| CN1787449A (en) * | 2004-12-08 | 2006-06-14 | 中兴通讯股份有限公司 | Integrated network managing system of telecommunication management network and method for realizing integrated network management |
-
2006
- 2006-11-09 CN CNB200610063558XA patent/CN100571156C/en not_active Expired - Fee Related
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826985A (en) * | 2010-04-20 | 2010-09-08 | 中兴通讯股份有限公司 | Plugin-based centralized signaling tracing method and system |
| CN101826985B (en) * | 2010-04-20 | 2014-08-13 | 中兴通讯股份有限公司 | Plugin-based centralized signaling tracing method and system |
| WO2012024819A1 (en) * | 2010-08-26 | 2012-03-01 | 广州客多软件科技有限公司 | User information sharing method and system for client ends |
| CN101938376A (en) * | 2010-09-08 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for realizing function use of administrator client |
| WO2012031471A1 (en) * | 2010-09-08 | 2012-03-15 | 中兴通讯股份有限公司 | Method and system for achieving use of element management client functions |
| CN102752517A (en) * | 2011-05-16 | 2012-10-24 | 新奥特（北京）视频技术有限公司 | Integrated management method and device for plugins of subtitle system |
| CN102421113A (en) * | 2011-11-28 | 2012-04-18 | 中兴通讯股份有限公司 | Method and device for realizing multi-site operation by embedding multiple LMTs (Local Maintenance Terminals) into centralized network manager |
| CN102421113B (en) * | 2011-11-28 | 2018-05-04 | 中兴通讯股份有限公司 | Embedded multiple LMT realize the method and device of multi-site operation in centralized network management |
| CN104468172A (en) * | 2013-09-25 | 2015-03-25 | 中兴通讯股份有限公司 | Acquisition adapter management method and system |
| WO2015043251A1 (en) * | 2013-09-25 | 2015-04-02 | 中兴通讯股份有限公司 | Collection adaptor management method and system |
| CN104468172B (en) * | 2013-09-25 | 2019-11-05 | 南京中兴软件有限责任公司 | Acquire adapter management method and system |
| CN106406834A (en) * | 2015-07-30 | 2017-02-15 | 中兴通讯股份有限公司 | Method, device and system for managing application system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100571156C (en) | 2009-12-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100571156C (en) | A kind of in Upper NM Station the method for integrating lower network management function | |
| US8347318B2 (en) | Application component communication apparatus of SCA-based system and method thereof | |
| US8010973B2 (en) | Class loader for managing a network | |
| US7707240B2 (en) | Proxy for application server | |
| US20060242598A1 (en) | Visual designer for telephony applications | |
| CN101192937B (en) | A hot deployable method and its system | |
| CN101833465B (en) | Embedded system supporting dynamic loading operation of application programs | |
| CN106339237B (en) | For the plug-in unit loading frame and method of the field JavaEE WEB application | |
| US10033790B2 (en) | Method for a connector providing transactional interoperability to multiple messaging providers to multiple application servers using the same implementation | |
| CN101631033A (en) | Method, system, server and client for calling remote component | |
| CN108363612A (en) | The J2EE modules heat deployment and recalls information statistical method realized based on class loaders | |
| EP1198102B1 (en) | Extendable provisioning mechanism for a service gateway | |
| CN115543546B (en) | Spring-based module hot deployment method and system | |
| CN102033741A (en) | North interface system and realization method thereof | |
| EP2216962B1 (en) | A method for deploying and managing the sip servlet application and the osgi service platform thereof | |
| CN101944033A (en) | Device and method for dynamically supporting multiple protocols in embedded system | |
| KR100590730B1 (en) | file system based on SCA system and method for arranging and managing software component file thereof | |
| CN102843342A (en) | Method and system for dynamically upgrading resource | |
| CN101997873A (en) | Capability accessing method and accessing platform | |
| CN109783132B (en) | Method and device for realizing system singleization and distribution | |
| CN113064737B (en) | Method for enabling components of software communication architecture to run in parallel on multi-core processor | |
| CN108694048A (en) | A kind of implementation method of batch issuing service | |
| Abdellatif | Enhancing the management of a j2ee application server using a component-based architecture | |
| Hermansson et al. | A distributed component architecture for a large telecommunication application | |
| CN113157251B (en) | Resource servitization and customization method for man-machine-object fusion 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 | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20091216 Termination date: 20151109 |
|
| EXPY | Termination of patent right or utility model |