Unified Management Of Service Components In SOA

With continuous changing of enterprise needs and increasing of legacy systems between enterprises and internal enterprises, new architecture SOA came into being. And it largely resolved legacy systems problem. In the application systems based on SOA architecture, every function consists of Service components which had loose coupling and unifying definition interface. With more and more service components had been developed by Research institutions and developers, how to issue, combine and invoke these components were put forward higher request. So this paper proposed a kind method that how to make unified management of Service components.In the management of Service Components, service registration and publishing technology was the first step. This paper introduced the semantic Web services and domain ontology and added rich semantic information in service description. UDDI structure also was expanded so that service provider could register service components with semantic information into UDDI conveniently. It was helpful to dynamic service discovery and combination later. Recall ratio and accuracy of service were also improved.Secondly, this paper adopted concept similarity of domain ontology to calculate matching degree of services. Take the matching degree of service as weight of using this service in figure planning and find out all service grouping sequences meeting requirements. Then, find out optimal combination scheme in these grouping sequences through service's weights. When UDDI couldn't find single service which meet service request, it would try to meet service request through the interface of service combination.Finally, realize service invocation through changing optimal combination scheme to BPEL codes. In generating BPEL codes, the conversion from OWL-S to WSDL was needed first. The reason was that this paper was based on the semantic Web services description language OWL-S, but BPEL was based on WSDL. This paper designed a middle layer called business flow execution engine. It realized combination service invocation through a simple invocation interface which was provided by engine interface.