TWI579782B - Service management method - Google Patents

Description

A method of service management

The present invention relates to the field of enterprise resource planning systems, and in particular to a method of service management.

Service oriented is a method of architecting software systems. The functionality of the service-oriented architecture is loaded by the server and provides external functionality through an interface.

The service-oriented architecture enables common infrastructure functions to be defined in services, making the implementation of functions easier to manage, maintain, and extend, enabling software systems to quickly respond to changing needs and respond to different application environments.

It is very important to classify services into service levels, reflecting the composite or irregular nature of services. If the partitioning method is not good, more and more small-grained services will be defined, designed and deployed, but there is no shortage. Controllability leads to major performance, flexible application and management issues.

In the traditional way, obtaining a service is generally through a service interface. The interface is an implementation of the implementation of the service function, and the service implementation provides functionality by disclosing some methods. The service is obtained by specifying the service interface type to obtain the service implementation corresponding to the service interface. The service definition process is not directly related to the business, such as a save service, which is implemented in one way in the order, in another way in the sales order, and in other ways in the purchase order. Therefore, in order to implement the same function with different business logics, different service interfaces need to be established, making the number of service interfaces large and difficult to manage. For example, (see Figure 1), the function of saving the service needs to have a save service implementation. In the traditional way it may be necessary to define three not The same interface (in turn, the service interface M, the service interface N, the service interface O) and then the service implementation in the service implementation M and the service implementation O can specify different interfaces when the service is invoked to obtain the corresponding service implementation.

The object of the present invention is to solve the above problems and provide a method for service management, which not only subdivides a service by a business domain, but also makes the requester of the service only need to care about the service domain and the service interface type, and Service providers and service creators store and manage services, adding services to service providers based on the scope of application of the services. At the same time, the method provides an upwardly addressed service provider link, ensuring that the service can be properly located and stored. In addition, the method provides different service lifecycle types.

In order to achieve the above object, the present invention adopts the following management method: a service management method, which is applied to a software system, and includes the following steps: (a) subdividing a service by a plurality of service areas, each a business domain having a business domain identifier; (b) adding a projection of the service on the business domain to at least one service provider based on the segmentation result, the projection including the business domain identifier, a service type and a service creator; and (c) when requesting the service, obtaining the service creator of the projection according to the service domain identifier and the service type, by the service The creator returns a service instance.

Further, the at least one service provider is a plurality of phased service providers.

Further, in the step (b), the projection is added to a plurality of the service providers according to the application range of the projection.

Further, in the step (c), the method further includes the following steps: when requesting the service, requesting a service from the at least one service provider by using a service call (GetService) method provided by the at least one service provider Starting to retrieve one by one to other service providers, looking up the service creator of the projection; and returning the service instance by the service creator when the projected service creator is retrieved.

Further, in the step of returning to the service instance, an exception is thrown when the projection is not retrieved.

Further, in the step of retrieving the projected service creator, further comprising, when the service type is found to have an interrupt flag, stopping the retrieval.

Further, after the step of subdividing the service by the service domain, the method further includes: dividing the service directory into the different file directories according to the service domain identifier, and configuring the service in the all file directories.

Further, the software system is an enterprise resource planning system.

In addition, the present invention further provides a method for service management, which is applied to a software system, comprising the steps of: identifying a common function in a software system and defining a service interface; and providing a service interface corresponding to each service domain according to the service interface. Specific service instances; set a lifecycle type for each service, specifying a service creation based on the lifecycle type Constructing, according to the service application scope, the type of the service interface, the service domain identifier, and the service creator together as a service projection into the service provider; when receiving the service request, by using the service domain identifier and service Type, retrieving a corresponding service creator from one of the service providers of the multi-layer service provider; retrieving the corresponding service creator layer by layer by the service link of the multi-layer service provider; and when retrieving the correspondence The service creator returns the service instance according to the lifecycle type of the service.

The advantages of the present invention are as follows: (1) By subdividing services in the service domain, the requester of the service only needs to care about the service domain and the service interface type, while maintaining the diversity of service implementation and being easier to develop; (2) being close to each other The related services are organized together with the service provider. The service provider provides a unified service invocation method (GetService) to facilitate system development and design. (3) Provides an upwardly addressed service provider link to ensure that the service can be serviced. It is correctly located and stored, perfectly supporting the complex application and requirements of the client-server model; and (4) providing different service lifecycle types to meet the complex business requirements of the software system.

The specific implementation manner of the method for service management of the present invention will be described in detail below with reference to the accompanying drawings.

2 is a flow chart of steps of a service management method according to the present invention. The service management method is applied to a software system, and includes the following steps:

S101: Subdivide a service by a service domain, where each service domain has a service domain identifier (For example, in Fig. 3, M12 represents the service area subdivision service). The service is a category of function points in the software system that is used to perform a required function. The invention is based on the service domain division service, is implemented by a stable universal interface agreement service, and associates a specific service implementation with a service domain by using a service domain identifier (for example, called by TypeKey), wherein the TypeKey is a service identifier. , through the common interface plus the business domain identifier (TypeKey), to obtain the correct service implementation in the business domain. The following is an example to illustrate the breakdown of services by business domain. See Figure 3: Service Implementation A (M122) and Service Implementation C (M124) are two projections of the service service common interface ISaveService in the service domain identifier TypekeyA and the service domain identifier TypekeyC. . When acquiring the service, if in the service area A, the specific service implementation A corresponding to the service area A can be found, and in the service area C, the specific service implementation C corresponding to the service area C can be found. Therefore, there is no need to inform the service provider which service area corresponds to the service interface, and no additional interface is required to enable the service provided by the server.

S102: According to the business requirement in each business domain, each service interface of each business domain provides a service implementation by writing a code, and the same service implementation may be reused for different service areas with the same functional business requirement.

S103: Dividing into different file directories according to the service domain identifier, and configuring the service in the file directory.

Here, different file directories are distinguished according to the service domain identifier, because when the system loads the service according to the configuration, the file folder in which the profile is located determines which application domain the service should be applied to. Each file directory corresponds to a service domain identifier (TypeKey), that is, corresponds to a service domain. In particular, not all services need to be configured in the business domain In the directory of the file, there is a public service that does not need to specify the TypeKey. You can configure it in the root directory or register the service directly in the code.

S104: Add a projection of the service on the service domain to a service provider of a multi-layer phase link according to a subdivision result, where the projection includes the service domain identifier (TypeKey) and a service interface type. (ISaveService) and a service creator. The projection refers to different service implementations for the service interface in different service areas. When one of the service providers of the multi-layer phase link service provider receives the service request, the service provider M11 of FIG. 4 internally has a dictionary M111, and the dictionary M111 includes a plurality of key-value pairs. For example, the key M112 and the value M113, the key value pair is the content of the above projection, the key M112 (key) is the business domain identifier and the service interface type, and the value M113 (value) is an internal service creation. Device. The key M112 and the value M113 are in a one-to-one correspondence. The following is another example to illustrate the service projection and service provider relationship. In Figure 4, the service interface ISaveService has different projections in different service areas A, B, and C, that is, service implementation A (M122), service. Implementation B (M123) and service implementation C (M124), where the three keys are set to ISaveService+A, ISaveService+B, ISaveService+C. Since the service type has been provided, the service implementation has been written into the code. For the service provider, when the software system executes, the service generates a corresponding service instance, and the service instance is provided by the service creator. carry out. The service creator is used to create service instances according to different types of service lifecycles. Services have different lifecycle types, including SingleGet, Singleton, Callback, and WeakReference. Where SingleGet is to generate a new service instance each time it is called; Singleton is to reuse the same service instance, that is, when the service is first called, a service instance is generated, and then the service is called when the same service is used. The instance is done to complete the function; Callback is the process created by the service instance, allowing incoming logic to determine how to create a service instance, and WeakReference to return a weak reference to the service instance. In addition, SingleGet, Singleton, and WeakReference are fixed creation logic, while Callback can customize the creation logic for added flexibility. Both Singleton and WeakReference will check if a service instance has been created. If there is, then it will not be created. If not, a new service instance will be created, but the service instance of Singleton will not be destroyed. WeakReference service instance will be released when not in use. After being released, it needs to be recreated.

S105: When one of the service providers of the multi-layered link service is requested by the service provider, start searching from one of the service providers according to the specified service domain identifier and the service interface type. The service creator of this projection. A service provider, also known as a service container, uses key-value pairs in a service provider that store the service creator. When any service provider receives a service request, it will return the required service instance, which is provided by the service creator. There are two ways to dynamically link a service to a service environment. One way is to be directly related to the service provider. At runtime, the service object can be dynamically connected to or disconnected from a service environment by setting up a service provider associated with the service object. Another way is to attach to another service, not directly associated with the service provider, by which the service provider is obtained. For example, if service A is connected to another service B, and service B is in the client service environment, service A can also share the service in the client service environment.

S106: If the projected service creator is not found, the requested service provider searches up to other service providers layer by layer. As shown in Figure 5, the underlying layer first invokes the service, and the UserControl (for example, opening the service form) opens a window containing a service container (service provider M11) containing some control services associated with this control. Format control A service that displays colors in a certain field. These services are registered in the service provider of the user control item and can be directly obtained. For another example, click the Save Toolbar button to invoke the client's legality check. Since the legality check service is directly registered in this form, it can be obtained directly from the form's service provider. For example, if the save service is to be executed and the save service is registered on the server, then the service link of the service provider of the multi-layer chain is searched up by layer. First, in the service provider of the user control item, that is, in the internal dictionary of the service provider M11, if not found, the request is forwarded to the service provider M20 of the upper layer, if the service provider of the upper layer is provided If the M20 (that is, the Form Service Provider) is not found, it is forwarded again to the client service provider M30, and the client service provider M30 searches for the presence or absence of the button, and if so, returns to the service. Instance, if not, continue to look up (ie, look up in the internal dictionary of the server service provider M40). If you look up on the server (on the server or appdomain machine), you need to cross the network boundary.

S107: Return the service instance when the projected service creator is retrieved. After receiving the call to save the service, the server service provider M40 retrieves and finds the key in the dictionary, and obtains the service creator corresponding to the save service in the service domain from the corresponding value, and creates according to the setting of the life cycle type. Save the service instance and return it. A flag (field) is set in each service provider to identify the superior service provider of the current level of service provider. In the step of searching up the layer by layer, when it is required to cross the network boundary, if the service type is found to have an interrupt flag, the service creator that searches for the projection is stopped up layer by layer. That is to say, the search is only done in the dictionary of the local service provider, and does not cross the network. If the service creator of the projection is not retrieved during the entire retrieval process (the retrieval process ends by retrieving the top-level service provider and interrupting the retrieval when crossing the network boundary), An exception was raised, ie the service could not be found.

Referring to Figure 6, the present invention proposes a method of a specific embodiment, the specific steps of which are as follows:

Step S601: First, define some common functions and common interfaces in the software system, such as ISaveService, IApproveService, IDeleteService and other common interfaces. Then in a business area, such as the business logic for order fulfillment, a stored service implementation is required in the order business logic. If it is found that there is no service implementation of the save order, the saved service implementation needs to be created for the order service, ie the ISaveService interface is implemented.

Step S602: When defining the service, set a function point category tag (service type). The service function point is implemented when a function package is applied.

Step S603: When defining the service (implementing the service), the implementation is performed according to the method agreement in the service interface and the business requirement in the service area. The Save method is declared in the service interface ISaveService. When the save service is implemented, the ISaveService interface is implemented. The implementation method of the Save method is required.

Step S604: The function point of the service and the function point interpreter of the service are preset. After receiving the function point set, the function point interpreter places the service projection corresponding to the function point in the service container of the corresponding service provider according to the function point category mark, and the application method of the function point is also stored in the interpreter.

Step S605: The save service is marked as a service type on a function point of the save service. The save service is placed in the service provider container when the software system is loaded. At the same time, the lifecycle type of the save service needs to be defined (for example, the save service lifecycle type is Singleton). At this point, the save service is defined.

Step S606: Configuring the save service in a function package, for example, placing the save service in a function package of the order. The business domain identifier of the order is A. During the order loading process, the system registers the save service with the server service provider. In the internal dictionary of the server service provider, the key is ISaveService+A, and the value is the corresponding service of the save service. Service creator. At this point, the system completes the loading process for saving the service in the order.

Step S607: When the software system is executed, the front end of the client side performs a save operation on the document of the service area A, and the back end requests the service provider of the current control item to save the service, adopts a common method to enter GetService, and uses ISaveService as a service interface. Type, with A as the business domain identifier. After receiving the call to save the service, the service provider of the current user control retrieves the key of (ISaveService+A) in the dictionary of the service provider of the user control item.

Step S608: When the service provider of the user control item finds that it is not found in the dictionary, the upper form service provider is found according to the service link. When the form service provider receives a call to save the service, it retrieves the key (ISaveService+A) in the form service provider's dictionary. When the form service provider finds that it is not found in the dictionary, the client service provider is found based on the service link. When the client service provider receives the call to save the service, the key of (ISaveService+A) is retrieved in the dictionary of the client service provider. If the client service provider finds that it is not found in the dictionary, it crosses the network boundary to the server service provider according to the service link.

Step S609: After the server service provider receives the call to save the service, the key of (ISaveService+A) is retrieved in the dictionary of the server service provider. If the server service provider finds the key, the service creator corresponding to the save service in the service domain A is obtained from the corresponding value. Since the lifecycle type of the save service is Singleton, it is determined whether the SaveService service is available. Instance, if not, not created, if not, then the service creator Create a new saveService (SaveService) instance.

Step S610: Calling the service instance service implementation method of the save service, and executing the save logic of the document A.

The invention has the beneficial effects that the service requester can use the business domain and the service interface type combination manner, and the upwardly addressed service provider link to correctly perform the positioning and storage service, and complete the development requirement.

While the invention has been described above in terms of the preferred embodiments, the invention is not intended to limit the invention, and the invention may be practiced without departing from the spirit and scope of the invention. The scope of protection of the present invention is therefore defined by the scope of the appended claims.

S101~S107‧‧‧Steps

M10‧‧‧Service projection and service provider relationship

M12‧‧‧Business area segmentation services

M121‧‧‧Save service interface

M122‧‧‧Service Implementation A

M123‧‧‧Service Implementation B

M124‧‧‧ Service Implementation C

M11‧‧‧ service provider

M111‧‧‧ dictionary

M112‧‧‧ key

M113‧‧ value

M20‧‧‧ Form Service Provider

M30‧‧‧Customer Service Provider

M40‧‧‧Server Service Provider

S601~S610‧‧‧Steps

1 is a schematic diagram of a conventional manner of performing service implementation using different interfaces; FIG. 2 is a flow chart of steps of the service management method of the present invention; FIG. 3 is a schematic diagram of a service domain subdivision service according to the present invention; Schematic diagram of the relationship between the service projection and the service provider of the present invention; FIG. 5 is a schematic diagram of the process of the service creator of the present invention for retrieving the projection from the service provider layer by layer; and FIG. 6 is an embodiment of the present invention A schematic diagram of specific implementation steps of the service management method.

S101~S107‧‧‧Steps

Claims (9)

A method for service management, the method for service management being applied to a software system, the method for service management comprising the steps of: (a) subdividing a service by a plurality of service areas, each of the service areas having a service a domain identifier; (b) adding a projection of the service on the service domain to at least one service provider based on the segmentation result, the projection including the service domain identifier, a service type, and a service creator, The service creator creates a service instance according to the service type; and (c) when one of the service providers of the at least one service provider receives the service request, according to the service domain identifier and the service type, One of the service providers begins to retrieve the projected service creator, and if the projected service creator is not found, retrieves from the requested service provider layer by layer to other service providers until the projection is obtained A service creator that returns a service instance by the service creator. The method of service management according to claim 1, wherein the at least one service provider is a plurality of phased service providers. The method of service management according to claim 2, wherein in the step (b), the application range according to the projection is added to the plurality of service providers. The method of service management according to claim 1, wherein in the step (c), the requested service provider is searched up to the other service provider to the other service provider according to the service call method of the service link. Service, first find the client service provider, if the user service provider does not find the projected service creator, then cross the network boundary to the server service To retrieve the service creator of the projection. The method of service management according to claim 1, wherein if the projected service creator is not retrieved during the entire retrieval process, a message that the service cannot be found is triggered. The method of service management according to claim 1, wherein in the step of retrieving the projected service creator, further comprising, when the service type is found to have an interrupt flag, stopping the retrieval. The method of service management according to claim 1, wherein after the step (a), the method further comprises: dividing the service directory identifier into different file directories, and defining the service in the file directory. . The method of service management according to claim 1, wherein the software system is an enterprise resource planning system. A method for service management, comprising the steps of: identifying a general function in a software system and defining a service interface; providing, according to the service interface, a specific service instance corresponding to the service interface for each service domain; The service sets a lifecycle type, and specifies a service creator according to the lifecycle type; according to the application scope of the service, the service interface type, the business domain identifier, and the service creator are put together as a service projection In the service provider; when receiving the service request, the corresponding service creator is retrieved from one of the multi-layer service providers by the service domain identifier and the service type; Retrieving a corresponding service creator layer by layer by the service link of the multi-layer service provider; and when retrieving the corresponding service creator, the service creator returns according to the life cycle type of the service The created service instance.