CN100401259C - A service provision method for a distributed service system - Google Patents

Abstract

The present invention provides a service provision method of a distributed service system. Firstly, the extended interface to be used, the public management service and the specific service to be provided are determined; then the specific service implements the extended interface, and the name of each service is determined and the service main implementation; then according to the names of the services and the service main implementation, respectively generate configuration files describing each service; the system loads the main implementation of each service respectively by reading and parsing the configuration files; publishes the public Manage services, and register and publish the specific services to be provided on the public management service. The invention overcomes the problems of inconsistency in access, difficulty in expansion, and huge chain reaction caused by adding or changing services in the prior art.

Description

A service provision method for a distributed service system

technical field

The invention relates to a computer data service providing method, in particular to a service providing method for a distributed service system.

Background technique

The distributed service system is to split the functions of the service system, put each function on several independent components, and complete the functions of the whole system through the mutual cooperation between these components. Here, several independent components can refer to several independent CPUs, but more usually refers to several computers on a network.

Using a distributed system, the biggest advantage lies in the processing speed of the system. Each function of the system is placed on several independent components, and the components of each part complete their own function blocks and work together in a parallel manner. Another advantage of the distributed service system is that each functional module is separated, which is convenient for management, maintenance and update. Server management and maintenance are also very important in large-scale service systems.

A typical distributed service system roughly includes the following parts:

The presentation layer is mainly responsible for the communication interface and data transmission between the business layer and users, and is the only part that directly deals with users;

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;

Data source, mainly used to store data.

However, a distributed system has far greater complexity in service provision than a service provider and consumer running on a single machine. The main reasons for this complexity are as follows:

1. Due to the distribution of the system, the server program and the client program may not be developed by the same development team, which causes the interface between the service provider and the client to be non-standard, resulting in difficulties in interoperability. When multiple service providers and clients are involved , the situation becomes even worse.

2. It is precisely because of the irregularity mentioned above that it is difficult to expand the service. When new services need to be added or existing services need to be changed due to changes in requirements, a serious chain reaction will be caused: those clients (or servers) that have nothing to do with the changes will also have to be rebuilt and deployed. When the system involves development teams belonging to several different companies, this knock-on effect can cause huge unnecessary waste.

3. Deployment is an important work in distributed services, and the difficulty of this work directly affects the workload of distributed service releases and upgrades. Unfortunately, many service providers now have to rebuild and restart the entire system when they need to upgrade or provide new services. workload.

It is precisely because of the above reasons that many current distributed systems are very inconsistent in terms of service provision and difficult to expand and deploy. And the companies and groups that develop these systems have to spend a lot of unnecessary money and energy.

Contents of the invention

The technical problem to be solved by the present invention is to provide a service providing method of a distributed service system, which overcomes problems in the prior art such as inconsistency in access, difficulty in expansion, and huge chain reaction caused by adding or changing services.

The present invention provides a service providing method of a distributed service system, comprising the following steps:

Determine the extended interface to be used, common management services, and specific services to be provided;

Realize the extension interface by the specific service, and determine the name of each service and the main implementation of the service;

Generate configuration files describing each service according to the name of each service and the main implementation of the service;

The system loads the main implementation of each service respectively by reading and parsing the configuration file;

Publish the public management service, and register and release the specific service to be provided on the public management service.

Preferably, the present invention further comprises the steps of:

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 according to the specific service name and provides it to the user.

Wherein, the step of implementing the service through the extended interface, and determining the service name and the service master further includes the step of determining the implementation strategy of the service, including the following steps:

Judging and determining that the service needs to be decomposed into different implementation strategies;

Decompose the problem domain and analyze the strategy components that need to be implemented;

Determine how policies and services will collaborate;

Implement policy components that work with services.

Wherein, in the step of generating a configuration file describing each service, the configuration file further includes information: the name of the strategy constituting the service, the component implementing the strategy, and the way the strategy is combined in the implementation of the service.

Wherein, the loading step further includes the following steps:

Judging and determining that the configuration file contains policy configuration information;

Parse out the policy implementation and its combination in the configuration file, and load it;

According to the combination method of the policy, the policy implementation is combined as in the service master implementation.

Compared with the prior art, the method of the present invention provides an efficient, convenient, consistent, and easy-to-expand method for providing distributed services. The method of configuration files is used to facilitate the organization of services, and the configuration and release of services is easy Instead of hard-coding, dynamic loading and Inversion of Control (Inversion of Control) technologies are used to separate service representation and implementation, so that service diversity can be easily realized. Using this method can greatly save time for service development, and can help distributed service systems build an underlying service management framework. Due to the introduction of inversion of control, the application has no direct dependence on the framework, which improves the testability of the service components. The configuration file organization method and service access method provided by the present invention can also be expanded according to actual needs, and the application range is wider. It realizes the scalability of services, the consistency of access, the diversity of service implementations, the easy configuration and addition of different types of services, and the dynamic loading. The present invention can provide highly modularized, dynamically and incrementally expandable services, and is especially suitable for the service provision mode between EMS (network element management system) and NMS (network management system) in telecommunication equipment management.

Description of drawings

FIG. 1 is a schematic flow chart of a service providing method of a distributed service system according to the present invention;

Fig. 2 is a schematic diagram of the process of service realization and configuration file generation according to the present invention;

Fig. 3 is a schematic diagram of the service loading and publishing process described in the present invention;

Fig. 4 is a schematic flow chart of the user using the service according to the present invention.

Detailed ways

As shown in FIG. 1 , it is a schematic flowchart of the method for providing distributed services in the present invention. First, determine the extended interface to be used, the public management service, and the specific service to be provided (step 101); implement the extended interface by the specific service, and determine the name and service master implementation of each service (step 102); The name of each service described and the main implementation of the service generate configuration files describing each service respectively (step 103); the system loads the main implementation of each service respectively by reading and parsing the configuration file (step 104); publishes the public management service, and register and release the specific service to be provided on the public management service (step 105).

In addition, if specific services require different implementation strategies, the present invention can further describe different strategies and their combinations into configuration files, and dynamically implement Combine the different strategies into the service master implementation.

The extended interface used in the present invention is a common technology used in the framework. This technology can make the functions of the interface scalable without affecting existing users. In order to achieve this goal, the extended interface technology provides a high-level, consistent abstract service interface, which defines the methods needed for service extension, such as: service query, etc., and the interface is implemented by specific services.

The specific service described in the present invention must inherit the above-mentioned defined extension interface when it is implemented. Among them, the public management service is a basic service of the system, which is loaded and released at startup, and all other services are published by registering with the public management service.

The configuration file describing the service in the present invention adopts the XML format, and the information therein can specifically relate to the service name, the main implementation component of the service, the policy name and the policy implementation component of the service, and the combination mode of the policy in the service implementation. Using the configuration file described by the service, the system can dynamically load at runtime and flexibly assemble the service according to the policy name, combination method, etc., so that the content of the service can be expanded and changed without any impact on other parts of the system.

An example of the description format of the configuration file is as follows:

<servicereg>

<service name="sample" imp="sampleServiceImp">

<strategy name="strategy1" imp="strategy 1 Imp"

means=”setStrategy 1”/>

<strategy name="strategy2" imp="strategy 2 Imp"

means="setStrategy2"/>

</service>

</servicereg>

Preferably, after the configuration file is generated, the specific service, policy implementation and corresponding configuration file can be copied to the directory specified by the system to prepare for loading and starting of the service.

When the system loads, starts and publishes the service, the system reads the service configuration file in the configuration directory, uses dynamic loading and inversion of control (Inversion Of Control) technology to complete the loading and assembly of the service, and registers the service to the public management service way to publish services. Inversion of control is a technology that can dynamically and flexibly establish dependencies between components at runtime, and the components themselves do not need to know the details of other components with which they have established relationships. This allows the developer of the component to concentrate on the component itself.

When customers use the service, the customer can use a unified access point to obtain common management services. Through this service, customers can query the specific service they are interested in through the service name. If the service exists, they can obtain and use the service.

As shown in FIG. 2 , it is a schematic diagram of the process of service realization and configuration file generation in the present invention. Firstly, the specific service implementation extends the pre-defined extension interface, that is, implements the service implementation, and determines the service name (step 201); then, judges whether the service needs to be decomposed into different implementation strategies (step 202), if step If the judgment of step 202 is false, skip to step 206; if the judgment of step 202 is true, then describe the service implementation strategy (step 203), which is to decompose the problem domain and analyze the strategy components that need to be implemented; describe the service strategy combination method (step 204 ), is to determine the collaboration mode between the strategy and the service; to implement the service implementation strategy (step 205), is to realize the strategy component that cooperates with the service; to generate a configuration file for service description (step 206), that is, to analyze the above The service name, service implementation components, policy names and policy implementation components that make up the service, and the combination of policies in the service implementation are described in the configuration file.

As shown in FIG. 3 , it is a schematic diagram of the service loading and publishing process described in the present invention. First, trigger the service loading action (step 301); then, read and parse the service configuration file (step 302); load the service master implementation, and dynamically load the service master implementation component parsed from the file (step 303); judge Whether there is a policy configuration in the service configuration file is to see whether there is a policy component configuration (step 304) implemented by the service master in the service configuration file; if step 304 is judged as false, then go to step 307; if step 304 is judged as 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 components; Combining the policy implementation into the service implementation subject; finally registering the service implementation into the public management service (step 307), the public management service is released when the system starts, and all other services are released by registering on the public management service.

As shown in FIG. 4 , it is a schematic flow chart of the user using the service according to the present invention. First, the client obtains the public management service (step 401); then, the client informs the public management service of the specific service name he wants to obtain (step 402); then, the client uses the public management service to obtain a specific service entity (step 403); finally, the client Concrete services are used (step 404).

An example implemented by JAVA language is used to illustrate the present invention below, and CORBA is adopted as the basic platform of distributed objects in this example. First determine an extension interface, in this example, the extension interface is a degenerate interface:

interface CommService{

};

Then we determine a public management service object:

interface ServiceMng{

CommService getService(in string servname);

};

Then determine a service to be implemented, the example uses the simplest HelloWorld sample

interface HelloworldService::CommService {

void sayHello();

};

The above process can be described by using IDL language, which is an interface definition language used in the CORBA protocol. Similarly, if other protocols are used, other definition languages can be used to complete the definition.

Further, analyze whether different implementation strategies are required in the service implementation. For example, in the service of this example, different language strategies can be adopted. For Chinese, it is necessary to say: "Hello, world!" For English, it is necessary to say: "Hello World!" Therefore, two different language strategies are required.

The following is the specific implementation of these two strategies.

public interface HelloWorld{

public String getHello();

}

Public class EnglishHelloworld implements HelloWorld{

public String getHello(){

return "Hello World!";

}

}

public class ChineseHello World implements Hello World{

public String getHello(){

return "Hello, world!";

}

}

Next, the service is implemented, in which the policy combination is determined.

public class HelloworldServiceImpl extends HelloworldService POA{

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 helloworld){

this.hello = helloworld;

}

}

Next, generate a configuration file describing the service, which for English is as follows:

<servicereg>

<service name="Hello World" imp="HelloworldServiceImpl">

<strategy name="language" imp="EnglishHelloworld"

means="setHello"/>

</service>

</servicereg>

For Chinese it is as follows:

<servicereg>

<service name="Hello World" imp="HelloworldServiceImpl">

<strategy name="language" imp="ChineseHello World"

means="setHello"/>

</service>

</servicereg>

For this example, the common management service is implemented as follows:

public class ServiceMngImpl extends ServiceMngPOA{

public CommService getService(String servname){

return services.getservname);

}

public void registerService(String name, CommService srv){

services_.put(name, srv);

}

private Hashtable services_=new Hashtable();

}

When the system loads the Hello World service, it will read and analyze the configuration file of the Hello World service. Firstly, the main implementation of the service, HelloworldServiceImpl, is dynamically loaded, and then the corresponding strategy is analyzed and loaded, and the strategy is combined into the service implementation according to the configured combination means, and released by calling the registerService method of the public management service ServiceMngImpl.

When a client wants to access the Hello World service, he first obtains the CORBA naming service, then obtains the public management service ServiceMngImpl, and calls the getService("Hello World") method of ServiceMngImpl to obtain the Hello World service.

Claims (8)

1. A method for providing a distributed service system, comprising the steps of: Determine the extended interface to be used, common management services, and specific services to be provided; Realize the extension interface by the specific service, and determine the name of each service and the main implementation of the service; Generate configuration files describing each service according to the name of each service and the main implementation of the service; By reading and parsing the configuration file, the system uses control inversion technology to establish dependencies between components, and loads the main implementation of each service respectively; Publish the public management service, and register and release the specific service to be provided on the public management service. 2. The method according to claim 1, further comprising the steps of: 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 according to the specific service name and provides it to the user. 3. The method according to claim 1, wherein the step of realizing the service through the extension interface and determining the service name and the service master further includes the step of determining the realization strategy of the service, including: Judging and determining that the service needs to be decomposed into different implementation strategies; Decompose the problem domain and analyze the strategy components that need to be implemented; Determine how policies and services will collaborate; Implement policy components that work with services. 4. The method according to claim 3, characterized in that, in the step of generating a configuration file describing each service, the configuration file further includes information: the policy name of the service, the policy implementation component, and the policy in the service implementation combination. 5. The method according to claim 1, characterized in that, after the step of generating configuration files describing each service, further comprising the steps of: Copy the specific service implementation and corresponding configuration files to the directory specified by the system to prepare for loading. 6. The method according to claim 4, further comprising the step of: Copy specific services, policy implementations, and corresponding configuration files to the directory specified by the system. 7. The method according to claim 4, wherein the loading step further comprises the steps of: Judging and determining that the configuration file contains policy configuration information; Parse out the policy implementation and its combination in the configuration file, and load it; According to the combination method of the policy, the policy implementation is combined as in the service master implementation. 8. The method according to claim 1 or 4, wherein the configuration file is described in XML format.

Images