WO2007019745A1 - Methode de fourniture de service d'un systeme distribue de service - Google Patents
Methode de fourniture de service d'un systeme distribue de service Download PDFInfo
- Publication number
- WO2007019745A1 WO2007019745A1 PCT/CN2005/001976 CN2005001976W WO2007019745A1 WO 2007019745 A1 WO2007019745 A1 WO 2007019745A1 CN 2005001976 W CN2005001976 W CN 2005001976W WO 2007019745 A1 WO2007019745 A1 WO 2007019745A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- implementation
- policy
- configuration file
- name
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Definitions
- the present invention relates to a computer data service providing method, and more particularly to a service providing method for a distributed service system. Background technique
- Distributed service system is to split the functions of the service system, put each function on several independent components, and cooperate with each other to complete the functions of the whole system.
- several independent components can refer to several independent CPUs, but more commonly refer to several computers on the network.
- the biggest advantage is in the processing speed of the system.
- the various functions of the system are placed on several separate components, and the components of each part complete their own function blocks and work together in parallel.
- Another advantage of the distributed service system is that the functional modules are separate and easy to manage, maintain and update. The management and maintenance of the server is also very important in the large service system.
- a typical distributed service system generally consists of the following parts:
- the presentation layer is mainly responsible for the communication interface and data transfer between the business layer and the user, and is the only part that directly deals with the user;
- the business layer is the heart of the distributed service system, and the most important data processing work and services are completed and provided by this part;
- the data source is mainly used to store data.
- the technical problem to be solved by the present invention is to provide a service providing method for a distributed service system to overcome the inconsistency of access in the prior art, difficulty in expansion, and large chain reaction due to addition or modification of services.
- the present invention provides a service providing method for a distributed service system, comprising the steps of: determining an extended interface to be used, a public management service, and a specific service to be provided; implementing the extended interface by the specific service, and determining each service
- the name is implemented by the service master; respectively, according to the name of each service and the service master implementation, respectively generating a configuration file describing each service; the system reads and parses the configuration file, respectively loading the main implementation of each service; Public management services, and the specific services to be provided are registered and published on public management services.
- the present invention further comprises the following steps:
- the public management service determines the specific service name that the user needs to obtain according to the user's instruction; the public management service obtains the specific service entity and provides it to the user according to the specific service name.
- the step of implementing the extended interface by a specific service, and determining the service name and the service main implementation further includes the steps of determining an implementation policy of the service, including the following steps:
- the generating a configuration file step describing each service, the configuration file further includes information: a policy name constituting the service, a policy implementation component, and a combination manner of the policy in the service implementation.
- the loading step further includes the following steps:
- the policy implementation is combined into the service master implementation based on how the policies are combined.
- the method provided by the present invention provides a distributed service providing method that is efficient, convenient, consistent, and easy to expand.
- the configuration file is convenient for the organization of the service, and the configuration of the service is not released.
- dynamic loading and Inversion of Control technology are used to separate the representation and implementation of the service, so that the service diversity can be easily realized.
- Using this approach can greatly reduce the time required for service development and can help the distributed service system build the underlying service management framework. Due to the introduction of control reversal, the application does not directly depend on the framework, and the testability of the service component is improved.
- the configuration mode and service access mode provided by the present invention can be extended according to actual needs, and the application scope is wider.
- the present invention can provide highly modular and dynamically and incrementally scalable services, and is particularly suitable for service provisioning between EMS (Network Element Management System) and NMS (Network Management System) in telecommunication equipment management.
- EMS Network Element Management System
- NMS Network Management System
- FIG. 1 is a schematic flowchart of a service providing method of a distributed service system according to the present invention
- FIG. 2 is a schematic diagram of a service implementation and a configuration file generating process according to the present invention
- FIG. 3 is a schematic diagram of a service loading and publishing process according to the present invention.
- FIG. 4 is a schematic flowchart of a user using a service according to the present invention. The best way to implement the invention
- FIG. 1 is a schematic flowchart diagram of a distributed service providing method according to the present invention.
- the extension interface to be used, the public management service, and the specific service to be provided (step 101); the extension interface is implemented by the specific service, and the name of each service and the service master implementation are determined (step 101).
- step 102 respectively, according to the name of each service and the service master implementation, respectively generating a configuration file describing each service (step 103); the system reads and parses the configuration file, respectively loading the main implementation of each service (step 104) Publishing the public management service and registering the specific service to be provided on the public management service (step 105).
- the present invention can further describe different policies and combinations thereof into the configuration file, and when the service is loaded, by reading and parsing the configuration file, dynamic Combine different strategies into the service master implementation.
- the extended interface used in the present invention is a common technique used in the framework. This technology makes the functionality of the interface scalable without affecting existing users. To achieve this goal, the extended interface technology provides a high-level, consistent abstract service interface that defines the methods needed for service extensions, such as service queries, etc., which are implemented by specific services.
- the public management service is a basic service of the system, which is loaded and released at startup, and all other services are released by registering with the public management service.
- the configuration file describing the service in the present invention adopts an XML format, wherein the information may specifically refer to a service name, a service implementation main implementation component, a policy name and a policy implementation component that constitute a service, and a combination manner of the policy in the service implementation.
- the system can dynamically load at runtime and flexibly assemble services based on policy names, combinations, etc., so that the content of the service can be extended and changed without any impact on other parts of the system.
- the specific service, policy implementation, and corresponding configuration file may be copied to a directory specified by the system to prepare for loading and starting the service.
- Control reversal is a technique that dynamically and flexibly establishes dependencies between components at runtime, without the components themselves having to know the details of the other components with which they are related. This allows the developer of the component to focus on the component itself.
- customers can use a unified access point to obtain common management services. Through this service, the customer can query the specific service that he or she is interested in through the service name. If the service exists, the service can be obtained and used.
- FIG. 2 is a schematic diagram of a service implementation and a configuration file generation process according to the present invention.
- the specific service implementation is used to extend the predefined extension interface, that is, to implement the service implementation, and determine the service name (step 201); then, determine whether the service needs to be decomposed into different implementation strategies (step 202), if the step The determination of 202 is false, and the process proceeds to step 206. If the determination of step 202 is true, the service implementation policy is described (step 203), that is, the problem domain is decomposed, and the policy component that needs to be implemented is parsed; and the service policy combination mode is described (step 204).
- ) is to determine the way of cooperation between the policy and the service; implementing the service implementation policy (step 205) is to implement the policy component that cooperates with the service; generating a configuration file for the service description (step 206), that is, the above analysis
- the service name, service implementation component, the policy name and policy implementation component that make up the service, and the combination of policies in the service implementation are described in the configuration file.
- FIG. 3 it is a schematic diagram of a service loading and publishing process according to the present invention.
- the service loading action is triggered (step 301); then, the service configuration file is read and parsed (step 302); the service main implementation is loaded, and the service main implementation component parsed from the file is dynamically loaded (step 303); Whether there is a policy configuration in the service configuration file is to see whether there is a policy component configuration implemented by the service master in the service configuration file (step 304); if the determination in step 304 is false, then go to step 307; if the determination in step 304 is true, then Analyzing and loading the policy implementation (step 305) is to parse out the policy combination mode in the configuration file and dynamically load the policy implementation component; then combine the policy implementation into the service implementation body (step 306), and parse the policy combination method according to step 305. , integrating the policy implementation into the service implementation principal; finally registering the service implementation into the public management service (step 307), public The co-management service is released at system
- FIG. 4 it is a schematic diagram of a process when a user uses a service according to the present invention.
- the client obtains the public management service (step 401); then, the client informs the public management service of the specific service name that he or she wants to obtain (step 402); then, the client uses the public management service to obtain the specific service entity (step 403); finally, the client Use a specific service (step 404).
- extension interface is a degraded interface:
- IDL is an interface definition language for the CORBA protocol. Similarly, if other protocols are used, other definition languages can be used to define the language.
- the system When the system loads the HelloWorld service, it reads and analyzes the configuration file of the HdloWorld service. Firstly, the main implementation of the service, HelloworldServicelmpl, is dynamically loaded, then the corresponding policies are analyzed and loaded, and the policies are combined into the service implementation according to the configured combination means, and the self is published by calling the registerService method of the public management service ServiceMnglmpl.
- the (Inversion of Control) technology separates the representation and implementation of services, making it easy to implement service diversity.
- Using this approach can greatly reduce the time required for service development and can help the distributed service system build the underlying service management framework. Due to the introduction of control reversal, the application does not directly depend on the framework, and the testability of the service component is improved.
- the configuration mode and service access mode provided by the present invention can be extended according to actual needs, and the application scope is wider. It achieves the scalability of services, the consistency of access, the diversity of service implementations, the ease of configuration and ease of addition of different types of services, and dynamic loading.
- the present invention can provide highly modular and dynamically and incrementally scalable services, and is particularly suitable for service provisioning between EMS (Network Element Management System) and NMS (Network Management System) in telecommunication equipment management.
- EMS Network Element Management System
- NMS Network Management System
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Stored Programmes (AREA)
Description
一种分布式服务系统的服务提供方法
技术领域
本发明涉及一种计算机数据服务提供方法,尤其涉及一种用于分布式服务 系统的服务提供方法。 背景技术
分布式服务系统就是将服务系统的功能拆分,将各个功能放在几个独立的 组件上, 通过这几个组件之间的相互协作, 来完成整个系统的功能。 在这里, 几个独立的组件可以是指几个独立的 CPU, 但更通常的是指网络上的几台计 算机。
采用分布式系统,最大的优点表现在系统的处理速度上。系统的各个功能 放在几个独立的组件上,各部分的组件完成自己的功能块, 以并行的方式协同 工作。分布式服务系统另外的优点还在于个功能模块分开, 便于管理、维护和 更新, 服务器的管理维护在大型的服务系统中也是相当重要的。
一个典型的分布式服务系统大致包括以下几部分:
表示层,主要负责业务层与用户之间的交流接口和数据传递工作,是唯一 一个直接与用户打交道的部分;
业务层,是分布式服务系统的心脏,最主要的数据处理工作和服务就由这 一部分完成和提供;
数据源, 主要用于存储数据。
然而,和运行在一台机器中的服务提供者和使用者相比,分布式系统在服 务提供方面具有大得多的复杂性。 造成这种复杂性的原因主要有以下几个方 面:
1、 由于系统分布, 服务器程序和客户程序很可能不是由同一个开发团队 开发, 这就造成服务提供者和客户之间的接口不规范, 导致互操作困难, 当涉 及多个服务提供者和客户时, 情况就会变得更加糟糕。
2、 正是由于上面所述的不规范性, 造成服务的扩展困难。 当由于需求的 变化需要增加新的服务或者对现有服务进行更改时, 就会造成严重的连锁反
应: 那些和改动无关的客户 (或者服务器) 也不得不进行重新的构建和部署。 当系统涉及隶属于多个不同公司的开发团队时,这种连锁反应会造成巨大的不 必要的浪费。
3、 部署是分布式服务中的一项重要工作, 这项工作的难度直接影响到分 布式服务发布和升级的工作量。遗憾的是,现在有很多服务提供者在需要升级 或者提供新的服务时,都不得不重新构建并重启整个系统,这不仅严重影响了 服务的可用性, 并且也给升级工作带来了很大的工作量。
正是由于上面的这些原因,使得当前很多分布式系统在服务提供方面非常 的不一致、难以扩展和部署。而开发这些系统的公司和团体也不得不耗费大量 的不必要的资金和精力。 发明公开
本发明所要解决的技术问题在于提供一种分布式服务系统的服务提供方 法, 以克服现有技术中存在的访问不一致, 难于扩展, 以及由于服务的添加或 者更改造成的巨大连锁反应等问题。
本发明提供一种分布式服务系统的服务提供方法, 包括如下步骤: 确定要使用的扩展接口、 公共管理服务以及要提供的具体服务; 由所述具体服务实现所述扩展接口, 并确定各服务的名称与服务主实现; 根据所述各服务的名称与服务主实现, 分别生成描述各服务的配置文件; 系统通过读取并解析所述配置文件, 分别加载各服务的主实现; 发布所述公共管理服务,并将要提供的具体服务在公共管理服务上进行注 册发布。
优选的, 本发明进一步包括如下步骤:
公共管理服务根据用户指示确定用户需要获取的具体服务名称; 公共管理服务根据具体服务名称获取该具体服务实体提供给用户使用。 其中,所述由具体服务实现所述扩展接口,并确定服务名称与服务主实现 的步骤, 进一步包括确定该服务的实现策略的步骤, 包括如下步骤:
判断并确定该服务需要分解为不同的实现策略;
分解问题领域, 解析出需要实现的策略组件;
确定策略与服务之间的协作方式;
实现出与服务相协作的策略组件。
其中,所述生成描述各服务的配置文件步骤,所述配置文件进一步包括信 息:组成服务的策略名称、策略实现组件,以及策略在服务实现中的组合方式。
其中, 所述加载步骤, 进一步包括如下步骤:
判断并确定所述配置文件中含有策略配置信息;
解析出配置文件中的策略实现及其组合方式, 并对其进行加载;
根据策略的组合方式, 将策略实现组合到服务主实现中。
采用本发明所述方法, 与现有技术相比, 提供了一种高效, 便捷, 一致, 并且易于扩展的分布式服务提供方法, 采用配置文件的方式方便对服务的组 织, 服务的配置发布不再采用硬编码的方式, 而是采用动态加载和控制反转 (Inversion of Control)技术使得服务的表示和实现分离, 从而可以很方便地 实现服务的多样性。运用这种方法, 可以极大地节省服务开发的时间, 可以帮 助分布式服务系统构建底层服务管理框架。由于控制反转的引入,应用对框架 不存在直接依赖,提高了服务组件的可测试性,本发明提供的配置文件组织方 式和服务访问方式还可以根据实际需要去进行扩展,应用范围更广,实现了服 务的可扩展性,访问的一致性, 服务实现的多样性, 不同类型服务的易配置和 易添加性以及动态加载性。本发明可以提供高度模块化且可动态、增量扩展的 服务, 特别适合于电信设备管理中 EMS (网元管理系统)和 NMS (网络管理 系统)之间的服务提供方式。
以下结合附图和具体实施例对本发明进行详细描述,但不作为对本发明的 限定。 附图简要说明
图 1为本发明所述的分布式服务系统的服务提供方法流程示意图; 图 2为本发明所述的服务实现及配置文件生成过程示意图;
图 3为本发明所述的服务加载与发布流程示意图;
图 4为本发明所述的用户使用服务时的流程示意图。 实现本发明的最佳方式
如图 1所示, 为本发明所述的分布式服务提供方法流程示意图。首先, 确
定要使用的扩展接口、 公共管理服务以及要提供的具体服务(步骤 101 ) ; 由 所述具体服务实现所述扩展接口, 并确定各服务的名称与服务主实现 (步骤
102) ; 根据所述各服务的名称与服务主实现, 分别生成描述各服务的配置文 件(步骤 103 ) ; 系统通过读取并解析所述配置文件, 分别加载各服务的主实 现(步骤 104) ; 发布所述公共管理服务, 并将要提供的具体服务在公共管理 服务上进行注册发布 (步骤 105 ) 。
此外,如果具体服务还需要不同的实现策略,那么, 本发明还可以进而将 不同的策略及其组合方式进一步的描述入配置文件,并在服务加载时,通过读 取和解析配置文件, 动态的将不同策略组合入服务主实现中。
本发明所使用的扩展接口,是一种运用在框架中的常用技术。该技术可以 使得接口的功能变得可扩展而不会影响到已有的使用者。 为了达到这个目的, 扩展接口技术提供了一个高层的、一致的抽象服务接口,该接口中定义了用于 服务扩展所需要的方法, 比如: 服务查询等, 由具体的服务实现该接口。
本发明所述的具体服务, 其在实现时必须要继承上述确定好的扩展接口。 其中, 公共管理服务为系统的一项基本服务, 在启动时加载和发布, 所有其他 服务都通过向公共管理服务注册的方式进行发布。
本发明所述的描述服务的配置文件采用 XML格式, 其中的信息可以具体 涉及服务名称, 服务实现主实现组件, 组成服务的策略名称和策略实现组件, 以及策略在服务实现中的组合方式。使用服务描述的配置文件,系统可以在运 行时动态地加载并根据策略名称、组合方式等灵活地组装服务,从而可以在对 系统其他部分没有任何影响的情况下, 扩展和改变服务的内容。
所述配置文件的描述格式举例如下:
<servicereg>
<service name- 'sample" imp="sampleServiceImp">
<strategy name="strategy 1 " imp=" strategy limp"
means- 'setStrategy 1 " />
<strategy name="strategy2" imp- ' strategy2Imp"
means="setStrategy2" />
</service>
</servicereg>
优选的, 在生成配置文件后, 可以把具体的服务、策略实现以及对应的配 置文件, 复制到系统指定的目录下, 为服务的加载和启动做准备。
系统加载、启动并发布服务时, 系统在配置目录读取服务配置文件, 采用 动态加载和控制反转 (Inversion Of Control) 技术来完成服务的加载、 组装, 并通过把服务注册到公共管理服务的方式发布服务。 控制反转是这样一种技 术, 它可以在运行时动态、灵活地建立起组件之间的依赖关系, 而组件本身却 无需知晓和其建立起关系的其他组件的细节。这样就可以使得组件的开发者集 中精力于组件本身。
当客户使用服务, 客户可以使用一个统一的访问点去获取公共的管理服 务。通过该服务, 客户可以通过服务名称查询自己感兴趣的具体服务, 如果服 务存在, 就可以获取并使用该服务了。
如图 2所示,为本发明所述的服务实现及配置文件生成过程示意图。首先, 由具体的服务实现去扩展事先定义的扩展接口,也就是实现服务实现,并确定 出服务名称(步骤 201 );然后,判断服务是否需要分解为不同的实现策略(步 骤 202) , 若步骤 202的判断为假, 跳至步骤 206; 若步骤 202的判断为真, 则描述服务实现策略(步骤 203) , 就是分解问题领域, 解析出需要实现的策 略组件; 描述服务策略组合方式(步骤 204) , 就是确定策略和服务之间的协 作方式; 实现服务实现策略(步骤 205),就是实现出与服务协作的策略组件; 生成用于服务描述的配置文件(步骤 206) , 就是将上面分析的服务名称, 服 务实现组件,组成服务的策略名称和策略实现组件, 以及策略在服务实现中的 组合方式描述在在配置文件中。
如图 3所示, 为本发明所述的服务加载与发布流程示意图。首先, 触发服 务加载动作 (步骤 301 ) ; 然后, 读取并解析服务配置文件 (步骤 302) ; 加 载服务主实现,对从文件中解析出的服务主实现组件,动态加载(步骤 303 ); 判断服务配置文件中是否有策略配置,就是看服务配置文件中是否有对服务主 实现的策略组件配置 (步骤 304) ; 如果步骤 304判断为假, 则转步骤 307; 如果步骤 304判断为真, 则分析并加载策略实现(步骤 305) , 就是解析出配 置文件中的策略组合方式并动态加载策略实现组件;再把策略实现组合进服务 实现主体(步骤 306) , 根据步骤 305解析出的策略组合方式, 把策略实现组 合进服务实现主体; 最后把服务实现注册到公共管理服务中 (步骤 307) , 公
共管理服务在系统启动时发布,所有的其他服务通过在公共管理服务上注册的 方式发布。
如图 4所示, 为本发明所述的用户使用服务时的流程示意图。首先, 客户 获取公共管理服务(步骤 401 ) ; 然后, 客户告知公共管理服务自己想获取的 具体服务名称(步骤 402) ; 然后, 客户使用公共管理服务获取具体服务实体 (步骤 403 ) ; 最后, 客户使用具体服务(步骤 404) 。
下面用 JAVA语言实现的一个例子来说明本发明,该例子中采用 CORBA 作为分布式对象的基础平台。首先确定一个扩展接口, 在本例中, 这个扩展接 口是一个退化接口:
interface CommService{
};
然后我们再确定一个公共管理服务对象:
interface ServiceMng{
CommService getService(in string servname);
};
然后再确定一个要实现的服务, 例子采用最简单的 HelloWorld样例 interface HelloworldService "CommService {
void sayHello();
};
上述过程可以采用 IDL语言进行描述, IDL是用于 CORBA协议的接口定 义语言, 与此相似的, 如果采用其他的协议, 可以使用其他的定义语言来完成 定义。
进一步,分析该服务实现中是否需要不同的实现策略,例如在本例的服务 中, 可以采用不同的语言策略。 对中文来说, 要说: "世界, 你好! ", 对英 文来说, 要说: "Hello World! ", 所以, 需要两种不同的语言策略。
下面是这两种策略的具体实现。
public interface Hello World{
public String getHello();
}
Public class EnglishHelloworld implements HelloWorld {
public String getHello(){
return "Hello World!":
public class ChineseHello World implements HelloWorld{
public String getHello(){
return "世界, 你好! ";
}
}
接着, 实现服务,在该服务实现中, 确定了策略的组合方式。
public class HelloworldServicelmpl extends HelloworldService PO^ private ORB orb = null;
private Hello World hello;
public void setORBEnv(ORB orb) {
this.orb = orb;
}
public void sayHello () {
System.out.println(hello.getHello());
}
Public void setHello(Hello World hello world) {
this.hello = helloworld;
}
}
接下来, 生成描述该服务的配置文件, 对于英文来说如下: <servicereg>
<service name- 'Hello World" imp- 'HelloworldServiceImpl">
<strategy name="language" imp- 'EnglishHelloworld' means="setHello" />
</service>
</servicereg>
对于中文来说如下:
<servicereg>
<service name- 'Hello World" imp="HelloworldServiceImpl">
<strategy name- 'language" imp- ' ChineseHello World'
means- 'setHello" />
</service>
</servicereg> 对于本例来说, 公共管理服务的实现如下:
public class ServiceMnglmpl extends S erviceMngPOA {
public CommService getService(String servname) {
return services.getservname ) ;
}
public void registerService(String name, CommService srv) { services— .put(name, srv);
}
private Hashtable services— = new Hashtable();
系统在加载 HelloWorld服务时, 会读取并分析 HdloWorld服务的配置文 件。 首先动态加载该服务的主实现 HelloworldServicelmpl, 然后分析并加载相 应的策略,并根据所配置的组合手段把策略组合进服务实现中,并通过调用公 共管理服务 ServiceMnglmpl的 registerService方法把自己发布出去。
客户要访问 HelloWorld服务时, 首先获得 CORBA的命名服务, 然后获 得 公 共 管 理 服 务 ServiceMnglmpl , 调 用 ServiceMnglmpl 的 getService("HelloWorld")方法获得 HelloWorld服务。
当然,本发明还可有其他多种实施例,在不背离本发明精神及其实质的情 况下,熟悉本领域的技术人员当可根据本发明作出各种相应的改变和变形,但 这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。 工业应用性
采用本发明所述方法, 与现有技术相比, 提供了一种高效, 便捷, 一致,
并且易于扩展的分布式服务提供方法, 采用配置文件的方式方便对服务的组 织, 服务的配置发布不再采用硬编码的方式, 而是采用动态加载和控制反转
(Inversion of Control)技术使得服务的表示和实现分离, 从而可以很方便地 实现服务的多样性。运用这种方法, 可以极大地节省服务开发的时间, 可以帮 助分布式服务系统构建底层服务管理框架。由于控制反转的引入,应用对框架 不存在直接依赖,提高了服务组件的可测试性,本发明提供的配置文件组织方 式和服务访问方式还可以根据实际需要去进行扩展,应用范围更广,实现了服 务的可扩展性,访问的一致性, 服务实现的多样性, 不同类型服务的易配置和 易添加性以及动态加载性。本发明可以提供高度模块化且可动态、增量扩展的 服务, 特别适合于电信设备管理中 EMS (网元管理系统)和 NMS (网络管理 系统) 之间的服务提供方式。
Claims
1、 一种分布式服务系统的服务提供方法, 其特征在于, 包括如下步骤: 步骤一, 确定要使用的扩展接口、 公共管理服务以及要提供的具体服务; 步骤二, 由所述具体服务实现所述扩展接口,并确定各服务的名称与服务 主实现;
步骤三,根据所述各服务的名称与服务主实现,分别生成描述各服务的配 置文件;
步骤四, 系统通过读取并解析所述配置文件, 分别加载各服务的主实现; 步骤五,发布所述公共管理服务,并将要提供的具体服务在公共管理服务 上进行注册发布。
2、 如权利要求 1所述的方法, 其特征在于, 进一步包括如下步骤: 公共管理服务根据用户指示确定用户需要获取的具体服务名称; 公共管理服务根据所述具体服务名称获取该具体服务实体提供给用户使 用。
3、 如权利要求 1所述的方法, 其特征在于, 所述由具体服务实现所述扩 展接口,并确定服务名称与服务主实现的步骤,进一步包括确定该服务的实现 策略的步骤, 包括:
步骤三一, 判断并确定该服务需要分解为不同的实现策略;
步骤三二, 分解问题领域, 解析出需要实现的策略组件;
歩骤三三, 确定所述策略与所述服务之间的协作方式;
步骤三四, 实现出与所述服务相协作的策略组件。
4、 如权利要求 3所述的方法, 其特征在于, 所述生成描述各服务的配置 文件的步骤中所述的配置文件进一步包括如下信息:组成服务的策略名称、策 略实现组件, 以及策略在服务实现中的组合方式。
5、 如权利要求 1所述的方法, 其特征在于, 所述生成描述各服务的配置 文件的步骤后, 进一步包括步骤:
将具体的服务实现以及对应的配置文件复制到系统指定的目录下,为加载 做准备。
6、 如权利要求 4所述的方法, 其特征在于, 所述生成描述各服务的配置
文件的步骤后, 进一步包括步骤:
将具体的服务、 策略实现以及对应的配置文件复制到系统指定的目录下。
7、 如权利要求 4所述的方法, 其特征在于, 所述加载步骤, 进一步包括 如下步骤:
步骤七一, 判断并确定所述配置文件中含有策略配置信息;
步骤七二,解析出配置文件中的策略实现及其组合方式,并对其进行加载; 歩骤七三, 根据所述策略的组合方式, 将策略实现组合到服务主实现中。
8、 如权利要求 1所述的方法, 其特征在于, 所述加载步骤中, 使用控制 反转技术来建立起组件之间的依赖关系。
9、如权利要求 1或 4所述的方法,其特征在于,所述的配置文件采用 XML 格式文件描述。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200510090749.0 | 2005-08-15 | ||
CNB2005100907490A CN100401259C (zh) | 2005-08-15 | 2005-08-15 | 一种分布式服务系统的服务提供方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007019745A1 true WO2007019745A1 (fr) | 2007-02-22 |
Family
ID=37737857
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2005/001976 WO2007019745A1 (fr) | 2005-08-15 | 2005-11-23 | Methode de fourniture de service d'un systeme distribue de service |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN100401259C (zh) |
WO (1) | WO2007019745A1 (zh) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101882073A (zh) * | 2009-05-04 | 2010-11-10 | 谭家辉 | 面向服务的应用系统及其通信方法、创建器和创建方法 |
CN101826987B (zh) * | 2010-04-27 | 2012-05-02 | 北京邮电大学 | 一种基于融合开放网络的混合服务支撑系统及方法 |
CN105338025B (zh) * | 2014-07-21 | 2019-04-09 | 阿里巴巴集团控股有限公司 | 调用组件方法、系统、客户端及集中组件方法和服务器 |
CN105635303B (zh) * | 2016-01-19 | 2019-06-21 | 锐达互动科技股份有限公司 | 一种用分布式部署服务接口提高并发访问量的方法及系统 |
CN108052374B (zh) * | 2017-12-29 | 2021-08-31 | 郑州云海信息技术有限公司 | 一种部署容器微服务的方法及装置 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003045084A2 (en) * | 2001-11-19 | 2003-05-30 | Nokia Corporation | Provision of location information |
WO2003085556A1 (en) * | 2002-04-08 | 2003-10-16 | Nokia Corporation | Group management |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6484214B1 (en) * | 1998-03-05 | 2002-11-19 | Mcdonnell Douglas Helicopter Company | Method for distributed object communications based on dynamically acquired and assembled software components |
US7603469B2 (en) * | 2002-01-15 | 2009-10-13 | International Business Machines Corporation | Provisioning aggregated services in a distributed computing environment |
-
2005
- 2005-08-15 CN CNB2005100907490A patent/CN100401259C/zh not_active Expired - Fee Related
- 2005-11-23 WO PCT/CN2005/001976 patent/WO2007019745A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003045084A2 (en) * | 2001-11-19 | 2003-05-30 | Nokia Corporation | Provision of location information |
WO2003085556A1 (en) * | 2002-04-08 | 2003-10-16 | Nokia Corporation | Group management |
Also Published As
Publication number | Publication date |
---|---|
CN1916856A (zh) | 2007-02-21 |
CN100401259C (zh) | 2008-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8918454B2 (en) | Managing rule sets as web services | |
Bruneton et al. | Recursive and dynamic software composition with sharing | |
EP1960899B1 (en) | Conforming web services to an updated contract | |
US7673283B2 (en) | Method and system for improved modeling language profile | |
US8230448B2 (en) | Methods, systems and computer program products for web service interaction with a resource management system | |
Fang et al. | A version-aware approach for web service directory | |
WO2007019745A1 (fr) | Methode de fourniture de service d'un systeme distribue de service | |
Al Belushi et al. | An approach to wrap legacy applications into web services | |
Frank et al. | Using an interface proxy to host versioned web services | |
Möller et al. | Mixing service oriented and high level architectures in support of the GIG | |
KR101190597B1 (ko) | 로봇 소프트웨어 컴포넌트를 위한 메소드 포트 장치 및 구성 방법 | |
Rademacher et al. | Design of a domain-specific language based on a technology-independent web service framework | |
Schmidt et al. | Osgi 4c: enabling osgi for the cloud | |
Rana et al. | Service design patterns for computational grids | |
Li et al. | Integrate software agents and CORBA in computational grid | |
Zaremba et al. | Towards dynamic execution semantics in semantic web services | |
Sinclair et al. | Enhancing UDDI for grid service discovery by using dynamic parameters | |
Condie | Distributed Computing, Tomorrow's Panacea—an Introduction to Current Technology | |
Huang et al. | A flexible and efficient approach to reconcile different web services-based event notification specifications | |
Lau et al. | Deployment contracts for software components | |
Sheng et al. | Discovering e-services using UDDI in SELF-SERV | |
Karousos et al. | Developer support in open hypermedia systems: Towards a hypermedia service discovery mechanism | |
Vassilopoulos et al. | Distributed technologies CORBA, Enterprise JavaBeans, Web services: a comparative presentation | |
Domaschka et al. | Towards generic and middleware-independent support for replicated, distributed objects | |
Zhang et al. | Research on Multi-tier Distributed Systems Based on AOP and Web Services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 05814346 Country of ref document: EP Kind code of ref document: A1 |