CN103577931A - Reusable-software-service management system based on semanteme and implementation method thereof - Google Patents
Reusable-software-service management system based on semanteme and implementation method thereof Download PDFInfo
- Publication number
- CN103577931A CN103577931A CN201310515219.0A CN201310515219A CN103577931A CN 103577931 A CN103577931 A CN 103577931A CN 201310515219 A CN201310515219 A CN 201310515219A CN 103577931 A CN103577931 A CN 103577931A
- Authority
- CN
- China
- Prior art keywords
- service
- services
- bpel
- information
- management
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000011161 development Methods 0.000 claims abstract description 79
- 230000008569 process Effects 0.000 claims abstract description 26
- 235000019580 granularity Nutrition 0.000 claims abstract description 17
- 230000000007 visual effect Effects 0.000 claims abstract description 15
- 230000006870 function Effects 0.000 claims description 58
- 230000005714 functional activity Effects 0.000 claims description 26
- 230000019771 cognition Effects 0.000 claims description 6
- 230000000694 effects Effects 0.000 claims description 6
- 230000003993 interaction Effects 0.000 claims description 6
- 238000004458 analytical method Methods 0.000 claims description 5
- 239000012634 fragment Substances 0.000 claims description 5
- 238000011165 process development Methods 0.000 claims description 4
- 239000000344 soap Substances 0.000 claims description 4
- 238000009825 accumulation Methods 0.000 claims description 3
- 230000008859 change Effects 0.000 claims description 3
- 230000008570 general process Effects 0.000 claims description 3
- 238000012216 screening Methods 0.000 claims description 2
- 238000012800 visualization Methods 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 74
- 238000010586 diagram Methods 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a reusable-software-service management system based on semanteme and an implementation method of the reusable-software-service management system. The reusable-software-service management system comprises a service management module based on a multi-type software service management model and used for conducting modeling on three software service management objects with different granularities, a service storage and discovery module based on visual guiding operation and used for storing functional semanteme information based on service description information, storing service semanteme relation information based on service relations and providing rapid and accurate service inquiry results, and a BPEL development platform cooperative interface used for supporting the purpose that software services of a service asset repository are loaded into a development platform, and a service process is established through the visual dragging and splicing service. By the adoption of the reusable-software-service management system, the requirement that users share resources can be met, a new service is rapidly established on the basis of exiting services, the reusability of each service is improved, the function of the open service is brought into full play, development consumption is reduced, and the service development efficiency is improved.
Description
Technical Field
The invention relates to a Service-oriented architecture (SOA) technology in the field of software development, in particular to a reusable software Service management system based on semantics and an implementation method thereof, which are used for managing various services and Business Process Execution Language (BPEL) generated in a BPEL development platform.
Background
With the popularization of Service-oriented architecture (SOA), Web services as the core of implementing the SOA become more and more popular and are used to manage interfaces and resources. Web services are interoperable, stand-alone, modular, location-specific, loosely-coupled software elements that serve other applications via open standards of Web protocols and data formats (e.g., HTTP, XML, SOAP, etc.). SOA and Web services provide great interoperability, flexibility and reusability for enterprise IT architecture.
The existing Web services can be combined, and the services with small granularity and single function can be combined into new services with larger granularity and more complexity, so that the development time of users can be saved, and the reuse value of the services can be improved. After the Web services for realizing the specific functions are defined, the execution sequence of the services is determined according to the actual business logic, and meanwhile, the interactive process among the services is described, so that the combination of the Web services is completed. The service combination creates a new value-added service, thereby accelerating the development speed of the system and saving the development cost.
The WS-BPEL specification is a popular service composition specification in the industry, which defines various elements related to service composition, and a process developer can write BPEL code to combine services according to the specification, but provided that a user can be skilled in BPEL language. Thus, many visual BPEL development platforms, such as Active BPEL, BPEL Designer Project, etc., have emerged. The platforms allow a service developer to construct a logic structure of the service application by dragging visual graphic components, and the platforms automatically generate corresponding executable BPEL codes, so that the development efficiency of the service process is improved, and the development period is shortened. However, this simple method of associating various elements of the BPEL language with the visual components does not completely shield the developer from the grammatical details of the BPEL language, and therefore, further improvement of the development efficiency is limited.
On the basis of open source software BPEL Designer Project, a BPEL development platform based on Web service modeling provides service dragging operation with different granularities, can directly drag Web service to construct a business process, automatically generates corresponding BPEL elements and fills related attribute values, shields grammar details of BPEL language and avoids extra operation of developers. Meanwhile, coarse-grained combined service is provided, and rapid development by developers is facilitated. However, with the continuous development and accumulation of services, the management of services becomes a huge challenge. How to effectively organize and manage the increasing services (including the combined services) is to provide a good development environment for developers, the services meeting the requirements can be quickly and accurately found in the development process, the created services are added into the existing service library, and meanwhile, an accurate service recommendation function is provided, so that the development efficiency of the developers is improved, the development period is shortened, and based on the reasons, an efficient service management system is necessary.
Disclosure of Invention
In view of the above, the present invention provides a semantic-based reusable software service management system and an implementation method thereof, which implement storage of service information based on a relational database and an RDF description framework, manage core business logic based on a Spring framework, implement display of a platform view based on an Eclipse plug-in development technology, provide an efficient service management manner, so as to implement management of multiple types of software services, provide accurate service query, and improve service development efficiency.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a reusable software service management system based on semantics mainly comprises a service management module, a service storage and service discovery module and a BPEL development platform cooperation interface; wherein,
the service management module provides a basis for the service storage and service discovery module, is used for realizing a service management model based on semantic annotation and body classification, managing three service management objects with different granularities, defining different service object bodies and function bodies according to the definition of the objects in the model, recording different function information and relation semantic information among services, and performing classification management;
the service storage and service discovery module is connected with the service management module, provides a visual view for direct interaction for a user, and guides the user to store services and discover services; the method is integrated on a BPEL development platform in the form of an Eclipse plug-in, different storage guides are provided for different service objects, and views of service discovery and result viewing are provided; and the number of the first and second groups,
the BPEL development platform collaboration interface is called by a service storage and service discovery module and is used for communicating with the BPEL development platform, transmitting the searched service related information to the BPEL development platform for service loading, and finally generating a BPEL flow on the development platform through visual dragging combined service; reusable service detailed information selected by a user is obtained from a BPEL development platform and is transmitted to a service storage module, so that the service function information and the semantic associated information are automatically stored, and the accumulation of a service library is realized.
The service storage and service discovery module is also used for providing a good service discovery function for the user through the information management service provided by the user during service storage, and improving the accuracy of the query result by utilizing the semantic information of the service.
The service management model realizes management of different service objects and an auxiliary management object, and the service management object is an atomic service, a collaboration service and an application framework; the auxiliary management object is a functional activity; wherein,
atomic services, which are various types of Web services provided by service providers, implemented based on SOAP, or REST style; the atomic service can independently complete the operation of some specified functions and is a basic element in the service combination;
the cooperative service is positioned on the basis of the atomic service, provides new value-added service for users by describing the sequence relation and the interaction relation among the services, and is a combined service flow described by BPEL language; the method is a service with larger granularity, and more complex functions can be completed by using an atomic service; the collaboration service and the atomic service have semantic relation of inclusion and inclusion;
the application framework is abstract description of a business process, is a general process framework of a certain application field, is a reusable part extracted by field experts from a plurality of process development processes, and is described by adopting BPEL language; the application framework is a service abstraction with the maximum granularity, and cannot be actually executed as a service per se, but the flow framework can be utilized in service combination and is composed of a plurality of functional activities, so that the application framework and the functional activities have inclusion and included semantic association; and the number of the first and second groups,
the functional activity is positioned in the middle layer between the application framework and the atomic service and the cooperative service, is not a management object which is actually required, and is established for assisting in managing the three services; the functional activity is an abstraction of a service realized by a certain function, and a functional activity represents a collection of services for completing a certain function, wherein the service can be an atomic service or a cooperative service, the service is a core associated with three services, each service object has a specific relation, the service object has an inclusion and contained relation with the atomic service and the cooperative service, and the service object has an inclusion and contained relation with an application framework.
A realization method of a reusable software service management system based on semantics comprises the following steps:
A. modeling software service management objects with three different granularities by using a service management module based on a multi-type software service management model, carrying out body division according to the field, granularity and type of service, managing the semantic relation between the functional information of the service and the service, and storing service description information and real service in a service library;
B. through a service storage and service discovery module based on visual guide operation, storing functional semantic information according to service description information, storing service semantic relation information according to the relation between services, and providing a quick and accurate service search result;
C. and a BPEL development platform cooperation interface is adopted to support the loading of the software service of the service asset library into the development platform, and the business process is constructed through the visual dragging and splicing service.
Wherein, defining three different levels of ontologies using the service management model includes:
the service ontology realizes modeling of the service management object, three different service ontologies are established according to the definitions of three types of service management objects, the three different service ontologies respectively correspond to the atomic service, the collaborative service and the application framework, basic information and semantic information for describing the service are covered, the definitions of the information accurately reflect the relation among the services, and the definitions of various basic concepts are the most basic guarantee in the service management model;
the domain ontology defines different application domains, and is the home domain of each service application scene; in the domain ontology layer, the definitions of different domains are performed by domain experts on the basis of the cognition of an objective world, and the domain ontology can be dynamically adjusted by a specific manager according to the management strategy of a platform;
the functional ontology inherits from the domain ontology, which is further refinement of the domain ontology, defines each functional entity in a certain domain according to different functions, and each functional ontology represents a set of services with similar functions; the definition of the function ontology is divided by the domain expert according to objective cognition, and the division of the function ontology needs to support dynamic change to adapt to the requirement of service management.
Utilizing the service storage module to perform the following operations:
a user selects Web services or BPEL flow segments needing to be stored in a BPEL development platform, selects a service storage function and triggers storage operation;
analyzing the selected description document or BPEL flow segment of the Web service, splitting the description document containing a plurality of services, and displaying the information obtained by analysis to a user;
adding detailed service description information by a user, selecting the field of service attribution and function activities, and submitting a storage request after the description is finished;
storing basic information of the service into a traditional relational database, recording semantic association between the service and other services by using an RDF resource description framework, and finishing storage of service information; and if the storage fails, returning corresponding error information and reminding the user.
The service discovery module also comprises basic fuzzy search and advanced accurate search, and specifically comprises the following steps:
a user opens a service search view or a service advanced search dialog box on a BPEL development platform, inputs related search keywords according to requirements or provides detailed information on specific service attributes, reduces the search range and submits a service search request;
and carrying out preliminary screening by utilizing a searching function of the relational database, acquiring the finally recommended service by utilizing SPARQL search reasoning, and displaying a searching result to a user.
And using the BPEL development platform cooperation interface to complete the following steps:
a user selects a service required by development in a service list of a search result, and right-clicking selects loading or clicks a loading button to trigger the operation of loading the service; calling a BPEL development platform cooperation interface, and transmitting the selected service related information to the BPEL development platform; the BPEL development platform encapsulates the transmitted service information into corresponding service objects, and then the service objects are displayed on a visualization component of the BPEL development platform to allow a user to use the service in a dragging mode;
a user selects stored services or BPEL process fragments on a BPEL development platform to complete analysis of the services or the BPEL process fragments, then transfers detailed information of the services to a service storage module by calling a BPEL development platform cooperation interface, and encapsulates the detailed information into corresponding service objects to complete service storage.
The reusable software service management system based on the semantics and the realization method thereof provided by the invention have the following advantages:
a reusable software service management system based on semantics and an implementation method thereof utilize semantic annotation and ontology classification to manage three different types of service objects and semantic relations between the service objects, and provide a convenient and efficient common service management center for storing, inquiring, classifying and calling services for users. The invention can satisfy the requirement of sharing resources by multiple users, quickly construct new service on the basis of the existing service, improve the reusability of the service, fully exert the function of the open service, reduce the development consumption and improve the service development efficiency.
Drawings
FIG. 1A and FIG. 1B are schematic structural diagrams of a reusable software service management platform according to an embodiment of the present invention;
FIG. 2 is a diagram of the relationship between service objects managed by the present invention;
FIG. 3 is an ontology diagram of a service management model employed in the present invention;
FIG. 4 is a data layer structure diagram of the platform implementation of the present invention;
FIG. 5 is a sequence diagram of an atomic service store in the present invention;
FIG. 6 is a sequence diagram of application framework storage in the present invention;
FIG. 7 is a flow chart of a service query in the present invention.
Detailed Description
The method of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments of the invention.
The basic idea of the invention is: the method comprises the steps of obtaining information of services or BPEL process fragments on a BPEL development platform by using a BPEL development platform cooperation interface, guiding a user to add detailed description information of the services through a service storage view, then storing the information into a shared service library, managing the services by using a service management model based on semantic annotation and body classification, providing an efficient service discovery function for the user on the basis, finding the services meeting development requirements, loading the selected services into the BPEL development platform through the BPEL development platform cooperation interface, and finally realizing the use of the services.
In an open collaborative network, different service providers can share their resources and build new services quickly on the basis of existing services. The multi-user sharing in the cooperative network needs a good service management platform to efficiently manage the increasing services, provides a platform for service sharing and service discovery for service developers, and allows the service developers to quickly and accurately find the services meeting the requirements. Through the service management system, the user can obtain the following benefits: the service reuse fully exerts the function of opening the service, reduces the development consumption and improves the development speed; service evaluation, namely measuring services according to a certain strategy and providing a standard for service selection; and service analysis, namely analyzing related problems including user preference, service use frequency and the like on the basis of the collected information, and helping to specify a service policy.
The reusable software service management system based on semantics and the implementation method thereof are used for rapidly building an enterprise service flow in service-oriented business development, the reusable software service management system provides a multi-level and multi-granularity software service function module for the generation of the enterprise service flow, and the service flow is rapidly generated and effectively managed by finding and recommending the service module. The system mainly comprises: the method comprises the steps that a service management module based on a multi-type software service management model models service function module management objects with three different granularities required in SOA business process development, body division is carried out according to the field, granularity and type of the service module, the semantic relation between the function information of the service and the service is managed, and service description information and service module codes are stored in a service library; the service storage module and the service discovery module based on visual guide operation store functional semantic information according to service description information, store service semantic relation information according to the relation between services and provide a quick and accurate service search result; the interface used in cooperation with the BPEL development platform supports loading of services of the software service library into the development platform, and the business process is constructed through visual dragging and splicing services.
The invention adopts a layered software system architecture, realizes the storage of service information based on a relational database and an RDF description framework, manages the core service logic based on a Spring framework, realizes the display of a platform view based on an Eclipse plug-in development technology, and provides an efficient software service management mode, thereby realizing the management of various types of software services, providing accurate service inquiry and improving the software service development efficiency.
Fig. 1A and fig. 1B are schematic structural diagrams of a reusable software service management platform according to an embodiment of the present invention. Belongs to a reusable software service management platform which is used in cooperation with a BPEL development platform. As shown in fig. 1A and 1B, the platform is implemented by using a layered architecture, which specifically includes:
the data layer is the basis of the platform and is used for realizing a data management model serving as a core of the platform, storing relevant service information and effectively managing the information, and the service layer completes access operation on the data layer by calling a uniform data access control interface.
And the business layer is used for realizing the core logic of the reusable software service management platform, including service storage and service discovery, providing necessary information for the display of the view layer upwards, responding to the view operation of a user, and acquiring data required by the operation from the data layer downwards and storing new data.
And the viewing layer is used for displaying information to a user and performing necessary manual interaction to guide the user to perform related operation, so that good user experience is provided for the user.
In the management platform, further, the service management model implemented by the data layer specifically includes:
three service management objects and one auxiliary management object are modeled, namely an atomic service, a collaboration service, an application framework and a functional activity. Further, it is defined as:
atomic Services (AS) is a Web Service of various types provided by a Service provider, and may be implemented based on SOAP or may be of REST style. Atomic services, which are capable of independently performing operations for certain specified functions, are essential elements in a service composition. Each atomic service is defined by a tuple:
AS = <SC，SA，SR>
the SC is a basic information set of an atomic service, and all types of services must provide the basic information, including the name, description information, application field, service provider, submission time, service location, and the like of the service. The SA is an extra service information set defined by the user for different service types, and may be null, and metadata for service description needs to be defined by the user. E.g., manner of request for RESTful Web services, etc. The SR is a set of relationships between the atomic service and other management objects, mainly relationships with the collaborative services and functional activities.
The Collaboration Service (CS) is a combined Service flow described by BPEL language, which provides new value-added services for users by describing the sequence relationship and interaction relationship between services on the basis of atomic services. The method is a larger-granularity service, and uses an atomic service to complete more complex functions, namely, a collaboration service is composed of the atomic service, so that the collaboration service and the atomic service have semantic relation of inclusion and inclusion. Each collaboration service is defined by a tuple:
CS = <CC，CR>
the CC is a basic information set of the collaboration service, similar to the SC of the atomic service, and includes information such as a name, description information, an application field, a service provider, a submission time, and a process address of the service. A CR is a set of relationships between a collaboration service and other managed objects, primarily describing the relationships with atomic services and functional activities.
An Application Framework (AF) is an abstract description of a business process, is a general process Framework in a certain Application field, is a reusable part extracted by developers from many process development processes, and is described by adopting a BPEL language. The application framework is a service abstraction with maximum granularity, which cannot be actually executed as a service per se, but the flow framework can be utilized in service combination and is composed of a plurality of functional activities, so that the application framework and the functional activities have inclusion and included semantic association. Each application framework is defined by a tuple:
AF = <AC，AR>
the AC is a basic information set of the application framework, and since the same as the collaboration service is a BPEL flow segment, the basic information is the same as the CC of the collaboration service, and includes the name, description information, application field, service provider, submission time, and flow address of the service. AR is a collection of relationships between the application framework and other management objects, primarily semantic relationships with functional activities.
The functional Activity (AT) is an intermediate layer between the application framework and the atomic and collaborative services, and is not an actually required management object and is established to assist in managing the three services. A functional activity is an abstraction of a service implemented by a certain function, and a functional activity represents a collection of services for performing a certain function, wherein the service can be an atomic service or a collaboration service, and is a core associated with three services, and has a specific relationship with each service object, an inclusion and inclusion relationship with the atomic service and the collaboration service, and an inclusion and inclusion relationship with an application framework. Each functional activity is defined by a tuple:
AT = <TC，TR>
the TC is a basic information set of the functional activity, and includes information such as a name, description information, and an application field of the functional activity. The TR is a set of relationships between functional activities and other management objects, which relationships include semantic associations with atomic services, collaboration services, and application frameworks due to the hub location of the functional activity.
FIG. 2 is a diagram of the relationship between service objects managed by the present invention. As shown in FIG. 2, the relationship between service objects is displayed.
According to the definition of the service management object, three ontologies with different levels are established, namely a service ontology, a field ontology and a function ontology. Further, it is defined as:
the service ontology realizes modeling of the service management object, three different service ontologies are established according to definitions of three types of service management object tuples, the three different service ontologies respectively correspond to an atomic service, a collaboration service and an application framework, basic information and semantic information for describing the service are covered, semantic association among the three service ontologies corresponds to various relationships defined in the previous section, the definitions of the information accurately reflect the relationships among the services, and the definitions of various basic concepts are the most basic guarantee in the service management model.
In the domain ontology layer, different application domains are defined, and the definition of the domains is performed by domain experts on the basis of the cognition of the objective world. Thus, to avoid inconsistencies in domain partitioning, domain ontologies are defined by professional platform administrators and are responsible for subsequent administrative operations. The division of the domains should be simple and have a wide coverage, the simplicity requires the classification to be as clear as possible, and the wide coverage means that the stored services can belong to a certain domain. The domain ontology divides all service management objects once, divides all services into two parts and treats all services, and can more accurately position the services. Since the domain ontology is manually involved, its definition may not remain unchanged, and as services increase and technologies continue to develop, the old domain partitions may not meet new requirements, so the domain ontology may be dynamically adjusted by a specific administrator according to the management policy of the platform.
The function ontologies are inherited from domain ontologies, and services in each domain are further refined according to the function attributes of the services, and each function ontology represents a set of services with similar functions. Through function-based aggregation, service management becomes more efficient and simple. Each service belongs to a specific function in a certain field, and similar services can be easily discovered and recommended through the field and the function. The definition of the function ontology is also divided by the domain experts according to objective cognition, but different from the domain ontology, the demand of the function ontology changes more frequently, so that the division of the function ontology needs to be more flexible, and dynamic change can be supported to adapt to the demand of service management.
FIG. 3 is an ontology diagram of a service management model employed by the present invention. As shown in FIG. 3, the ontology structure of the service management model is shown.
In the above management platform, further, the data layer implements a dual storage structure of a traditional relational database and an RDF, and specifically includes:
when the reusable software service management platform stores the service, all information of the service is stored in the traditional relational database, the database is used for realizing efficient management of data, the complexity of the platform is reduced, and then the relational semantic information of the service in the RDF semantic document is updated in time according to the related data in the database. When a service layer of the platform reads data, the data access control can be treated differently according to the service requirements, for data acquisition which does not need semantic reasoning, the data access control can directly search the required data from a database, and for data reading which needs semantic mining, the data access control can read information from an RDF document and perform corresponding semantic reasoning, so that richer service description information is provided for the service. The data reading efficiency of the platform can be improved through the classification, and because the reading speed of the RDF document is far lower than the storage speed of the database, the operation of the RDF document is reduced as much as possible by the platform, so that the processing speed of the platform is improved. As shown in fig. 4, a platform data layer structure is shown.
In the above management platform, further, the service layer includes:
and the service storage module allows a user to store newly developed services into the platform for subsequent reuse, and the services can be atomic services, cooperative services or application frameworks, so that the user can rapidly develop new processes based on the existing services through service sharing among service providers.
The service discovery module searches all services which possibly meet the requirements of the user from the existing service library according to the input information of the user, is one of main functions provided by the reusable software service management platform, and requires that the query result reaches a certain accuracy and recall ratio.
In the foregoing management platform, further, the service storage module specifically includes:
the atomic service storage firstly requires a user to input simple description information through an interface, such as an application field and the like, and then add a corresponding description document, because a plurality of atomic services may exist in the same document, the document needs to be parsed, the document is split into the plurality of atomic services, each parsed atomic service is re-displayed to the user, and the user performs detailed description on each atomic service, such as function description and the like, so that each atomic service can be accurately positioned. And finally, the data access control object realizes the persistence of data in a database and an RDF document to finish the service storage function. As shown in fig. 5, a sequence diagram is stored for an atomic service.
The application framework and the collaborative service are basically stored the same, taking the storage application framework as an example, a user needs to right-click a sequence needing to be stored in a service generation platform, a storage dialog box can correspondingly pop up, relevant information of the sequence can be displayed in the dialog box, the sequence includes activity and the like, the user submits the information after inputting the information, the information of the service is transmitted to business logic by calling a Web interface, all the information of the service is arranged and packaged into corresponding application framework objects, the application framework objects are delivered to a data access control object to be stored in a database and an RDF document, meanwhile, the activity information contained in the application framework is updated, the semantic relation between the application framework and the RDF document is maintained, and finally, the result is returned. As shown in fig. 6, a sequence diagram for storing an application framework from an Eclipse plug-in view.
In the management platform, further, the specific process of the service discovery module is as follows:
a user inputs corresponding search information in a basic search view or an advanced search dialog box and submits a query request;
the client transmits all the search information to the server through the Web service interface, and the server inquires the service;
packaging corresponding query conditions, and realizing query of the database through a data access control object to obtain a query result;
reasoning semantic information of the service by using a SPARQL in a Jena frame through a data access control object to obtain a corresponding search result;
and finally, the merging result is returned to the user and displayed in the service list view to finish the service searching process.
FIG. 7 is a flow chart of a service query in the present invention. As shown in fig. 7, a process of service inquiry is shown.
In the management platform, the view layer is realized by adopting an Eclipse platform plug-in development technology, the common display of the foreground is realized by utilizing Graphical User Interface (GUI) controls provided by SWT, and for a more complicated Graphical Interface, the realization of the view is simplified by utilizing Trees, tables and other components packaged by JFace. And the BPEL development platform is communicated with the BPEL development platform through a BPEL development platform cooperation interface, so that the functions of loading services and the like are realized. Further, the viewing layer includes:
dialogs, including service storage dialogs and configuration dialogs. The service storage dialog boxes are divided into three types according to different service objects, the three types respectively correspond to the storage of the atomic service, the collaboration service and the application framework, the service selected by the user is stored in the platform as the object, and the user is required to fill in corresponding necessary information such as application fields, names, comments and the like in the dialog boxes. The configuration dialog box is a configuration center for connecting the Eclipse plug-in client and the platform server, and a user can configure a connection address of the server on the dialog box, wherein the connection address comprises port information, so that the plug-in client can find the Web service.
Views, including a service query view and a service listing view. The service query view comprises a basic query view supporting fuzzy search of simple keywords and an advanced search view supporting precise search, wherein the basic query view only provides a text box for a user to input keywords, and the advanced search view provides precise classification including detailed information of types, fields, descriptions, owners and the like. The service list view shows basic information of the service to the user list, the result of the service query is displayed in the view, the displayed service information has names, descriptions, providers, types and the like, and the view supports the user to load the selected service into the service generation platform for use in development.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (8)
1. A reusable software service management system based on semantics is characterized by mainly comprising a service management module, a service storage and service discovery module and a BPEL development platform cooperation interface; wherein,
the service management module provides a basis for the service storage and service discovery module, is used for realizing a service management model based on semantic annotation and body classification, managing three service management objects with different granularities, defining different service object bodies and function bodies according to the definition of the objects in the model, recording different function information and relation semantic information among services, and performing classification management;
the service storage and service discovery module is connected with the service management module, provides a visual view for direct interaction for a user, and guides the user to store services and discover services; the method is integrated on a BPEL development platform in the form of an Eclipse plug-in, different storage guides are provided for different service objects, and views of service discovery and result viewing are provided; and the number of the first and second groups,
the BPEL development platform collaboration interface is called by a service storage and service discovery module and is used for communicating with the BPEL development platform, transmitting the searched service related information to the BPEL development platform for service loading, and finally generating a BPEL flow on the development platform through visual dragging combined service; reusable service detailed information selected by a user is obtained from a BPEL development platform and is transmitted to a service storage module, so that the service function information and the semantic associated information are automatically stored, and the accumulation of a service library is realized.
2. The reusable software service management system based on semantics of claim 1, wherein the service storage and service discovery module is further configured to provide a good service discovery function for a user through an information management service provided by the user during service storage, and improve accuracy of a query result by using semantic information of the service.
3. The semantics-based reusable software service management system of claim 1, wherein the service management model implements management of different service objects and an auxiliary management object, the service management object being an atomic service, a collaborative service and an application framework; the auxiliary management object is a functional activity; wherein,
atomic services, which are various types of Web services provided by service providers, implemented based on SOAP, or REST style; the atomic service can independently complete the operation of some specified functions and is a basic element in the service combination;
the cooperative service is positioned on the basis of the atomic service, provides new value-added service for users by describing the sequence relation and the interaction relation among the services, and is a combined service flow described by BPEL language; the method is a service with larger granularity, and more complex functions can be completed by using an atomic service; the collaboration service and the atomic service have semantic relation of inclusion and inclusion;
the application framework is abstract description of a business process, is a general process framework of a certain application field, is a reusable part extracted by field experts from a plurality of process development processes, and is described by adopting BPEL language; the application framework is a service abstraction with the maximum granularity, and cannot be actually executed as a service per se, but the flow framework can be utilized in service combination and is composed of a plurality of functional activities, so that the application framework and the functional activities have inclusion and included semantic association; and the number of the first and second groups,
the functional activity is positioned in the middle layer between the application framework and the atomic service and the cooperative service, is not a management object which is actually required, and is established for assisting in managing the three services; the functional activity is an abstraction of a service realized by a certain function, and a functional activity represents a collection of services for completing a certain function, wherein the service can be an atomic service or a cooperative service, the service is a core associated with three services, each service object has a specific relation, the service object has an inclusion and contained relation with the atomic service and the cooperative service, and the service object has an inclusion and contained relation with an application framework.
4. A realization method of a reusable software service management system based on semantics is characterized by comprising the following steps:
A. modeling software service management objects with three different granularities by using a service management module based on a multi-type software service management model, carrying out body division according to the field, granularity and type of service, managing the semantic relation between the functional information of the service and the service, and storing service description information and real service in a service library;
B. through a service storage and service discovery module based on visual guide operation, storing functional semantic information according to service description information, storing service semantic relation information according to the relation between services, and providing a quick and accurate service search result;
C. and a BPEL development platform cooperation interface is adopted to support the loading of the software service of the service asset library into the development platform, and the business process is constructed through the visual dragging and splicing service.
5. The method for implementing the reusable software service management system based on semantics of claim 4, wherein defining three different levels of ontology using the service management model comprises:
the service ontology realizes modeling of the service management object, three different service ontologies are established according to the definitions of three types of service management objects, the three different service ontologies respectively correspond to the atomic service, the collaborative service and the application framework, basic information and semantic information for describing the service are covered, the definitions of the information accurately reflect the relation among the services, and the definitions of various basic concepts are the most basic guarantee in the service management model;
the domain ontology defines different application domains, and is the home domain of each service application scene; in the domain ontology layer, the definitions of different domains are performed by domain experts on the basis of the cognition of an objective world, and the domain ontology can be dynamically adjusted by a specific manager according to the management strategy of a platform;
the functional ontology inherits from the domain ontology, which is further refinement of the domain ontology, defines each functional entity in a certain domain according to different functions, and each functional ontology represents a set of services with similar functions; the definition of the function ontology is divided by the domain expert according to objective cognition, and the division of the function ontology needs to support dynamic change to adapt to the requirement of service management.
6. The method for implementing the reusable software service management system based on semantics of claim 5, being characterized in that the service storage module is utilized to perform the following operations:
a user selects Web services or BPEL flow segments needing to be stored in a BPEL development platform, selects a service storage function and triggers storage operation;
analyzing the selected description document or BPEL flow segment of the Web service, splitting the description document containing a plurality of services, and displaying the information obtained by analysis to a user;
adding detailed service description information by a user, selecting the field of service attribution and function activities, and submitting a storage request after the description is finished;
storing basic information of the service into a traditional relational database, recording semantic association between the service and other services by using an RDF resource description framework, and finishing storage of service information; and if the storage fails, returning corresponding error information and reminding the user.
7. The method for implementing the reusable software service management system based on semantics of claim 5, wherein the service discovery module further comprises a basic fuzzy search and a high-level precise search, and the following steps are specifically performed:
a user opens a service search view or a service advanced search dialog box on a BPEL development platform, inputs related search keywords according to requirements or provides detailed information on specific service attributes, reduces the search range and submits a service search request;
and carrying out preliminary screening by utilizing a searching function of the relational database, acquiring the finally recommended service by utilizing SPARQL search reasoning, and displaying a searching result to a user.
8. The method for implementing the semantic-based reusable software service management system according to claim 4, wherein the following steps are performed by using the BPEL development platform collaboration interface:
a user selects a service required by development in a service list of a search result, and right-clicking selects loading or clicks a loading button to trigger the operation of loading the service; calling a BPEL development platform cooperation interface, and transmitting the selected service related information to the BPEL development platform; the BPEL development platform encapsulates the transmitted service information into corresponding service objects, and then the service objects are displayed on a visualization component of the BPEL development platform to allow a user to use the service in a dragging mode;
a user selects stored services or BPEL process fragments on a BPEL development platform to complete analysis of the services or the BPEL process fragments, then transfers detailed information of the services to a service storage module by calling a BPEL development platform cooperation interface, and encapsulates the detailed information into corresponding service objects to complete service storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310515219.0A CN103577931A (en) | 2013-10-28 | 2013-10-28 | Reusable-software-service management system based on semanteme and implementation method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310515219.0A CN103577931A (en) | 2013-10-28 | 2013-10-28 | Reusable-software-service management system based on semanteme and implementation method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103577931A true CN103577931A (en) | 2014-02-12 |
Family
ID=50049671
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310515219.0A Pending CN103577931A (en) | 2013-10-28 | 2013-10-28 | Reusable-software-service management system based on semanteme and implementation method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103577931A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106027576A (en) * | 2016-08-03 | 2016-10-12 | 浪潮(北京)电子信息产业有限公司 | Implementation method and device of multi-granularity service-oriented architecture |
| CN107368317A (en) * | 2017-07-24 | 2017-11-21 | 无锡江南计算技术研究所 | A kind of multiplexing of Web application modules and heavily loaded system and method |
| CN109101277A (en) * | 2017-06-20 | 2018-12-28 | 恒为科技（上海）股份有限公司 | A kind of information processing system based on semantic consistency |
| WO2019105093A1 (en) * | 2017-11-30 | 2019-06-06 | 广州市动景计算机科技有限公司 | Data encapsulating method and apparatus, data processing device and apparatus, and electronic device |
| CN111208976A (en) * | 2019-12-27 | 2020-05-29 | 广西泊客网络科技有限公司 | Method for automatically generating software system architecture |
| CN111435297A (en) * | 2019-01-14 | 2020-07-21 | 神州数码信息系统有限公司 | Automatic service adaptation method based on semantics |
| CN113495725A (en) * | 2021-06-08 | 2021-10-12 | 山西三友和智慧信息技术股份有限公司 | Artificial intelligence visual programming tool system based on big data |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101777004A (en) * | 2010-01-26 | 2010-07-14 | 北京邮电大学 | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment |
-
2013
- 2013-10-28 CN CN201310515219.0A patent/CN103577931A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101777004A (en) * | 2010-01-26 | 2010-07-14 | 北京邮电大学 | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment |
Non-Patent Citations (4)
| Title |
|---|
| LILI FANG,ET AL: "Service Management Model Based on Ontology", 《2012IEEE/ACIS 11TH INTERNATIONAL CONFERENCE ON COMPUTER AND INFORMATION SCIENCE》, 31 December 2012 (2012-12-31) * |
| 杨志: "基于本体的语义互操作研究", 《中国博士学位论文全文数据库信息科技辑》, no. 01, 15 January 2013 (2013-01-15) * |
| 段华: "基于扩展BPEL模型的SOA流程生成", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 08, 15 August 2012 (2012-08-15) * |
| 邓娜 等: "业务流程执行语言中流程模板的生成", 《北京邮电大学学报》, vol. 34, no. 06, 31 December 2011 (2011-12-31) * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106027576A (en) * | 2016-08-03 | 2016-10-12 | 浪潮(北京)电子信息产业有限公司 | Implementation method and device of multi-granularity service-oriented architecture |
| CN109101277A (en) * | 2017-06-20 | 2018-12-28 | 恒为科技（上海）股份有限公司 | A kind of information processing system based on semantic consistency |
| CN109101277B (en) * | 2017-06-20 | 2024-04-19 | 恒为科技（上海）股份有限公司 | Information processing system based on semantic consistency |
| CN107368317A (en) * | 2017-07-24 | 2017-11-21 | 无锡江南计算技术研究所 | A kind of multiplexing of Web application modules and heavily loaded system and method |
| WO2019105093A1 (en) * | 2017-11-30 | 2019-06-06 | 广州市动景计算机科技有限公司 | Data encapsulating method and apparatus, data processing device and apparatus, and electronic device |
| CN111435297A (en) * | 2019-01-14 | 2020-07-21 | 神州数码信息系统有限公司 | Automatic service adaptation method based on semantics |
| CN111208976A (en) * | 2019-12-27 | 2020-05-29 | 广西泊客网络科技有限公司 | Method for automatically generating software system architecture |
| CN111208976B (en) * | 2019-12-27 | 2023-04-11 | 广西泊客网络科技有限公司 | Method for automatically generating software system architecture |
| CN113495725A (en) * | 2021-06-08 | 2021-10-12 | 山西三友和智慧信息技术股份有限公司 | Artificial intelligence visual programming tool system based on big data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103577931A (en) | Reusable-software-service management system based on semanteme and implementation method thereof | |
| US7421699B2 (en) | Service meta model for an enterprise service architecture | |
| US20140172827A1 (en) | In-memory, columnar database multidimensional analytical view integration | |
| US9053445B2 (en) | Managing business objects | |
| Fill | SeMFIS: a flexible engineering platform for semantic annotations of conceptual models | |
| US9400647B2 (en) | Application discovery and integration using semantic metamodels | |
| Xinhua et al. | Big Data-as-a-Service: Definition and architecture | |
| Afsarmanesh et al. | Semi-automated software service integration in virtual organisations | |
| US10505873B2 (en) | Streamlining end-to-end flow of business-to-business integration processes | |
| Vitvar et al. | Semantic technologies for e-Government: an overview | |
| Castellanos et al. | A framework for alignment of data and processes architectures applied in a government institution | |
| Karakoc et al. | A workflow-based Web service composition system | |
| Rodríguez et al. | Assisted mashup development: On the discovery and recommendation of mashup composition knowledge | |
| Ed-Douibi et al. | APIComposer: Data-driven composition of REST APIs | |
| US9886520B2 (en) | Exposing relationships between universe objects | |
| Browne et al. | IBM Cognos Business Intelligence V10. 1 Handbook | |
| AbuJarour et al. | Web services and business processes: A round trip | |
| Gonen et al. | Ontological support for the evolution of future services oriented architectures | |
| Cuevas-Vicenttín et al. | Evaluating hybrid queries through service coordination in HYPATIA | |
| Zdravković et al. | Model-based, client-side integration of heterogeneous data from REST services | |
| Radeck et al. | Modeling and calculating capabilities of composite web applications for assisted end user development | |
| Ceri et al. | The anatomy of a multi-domain search infrastructure | |
| Tietz et al. | A requirements model for composite and distributed web mashups | |
| Coetzee et al. | Goal-based composition of scalable hybrid analytics for heterogeneous architectures | |
| Daniel et al. | Mashups and end-user development |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140212 |
|
| RJ01 | Rejection of invention patent application after publication |