A web service processing engine system and processing method

Abstract

The invention provides a web service processing engine system based on an event-driven architecture. The web service processing engine system comprises an event processing module and a web service analysis and execution module, wherein the event processing module is used for converting a web service call request of a service consume side into an event and transmitting the event to the web service analysis and execution module, and the web service analysis and execution module is used for analyzing the event transmitted by the event processing module and executing web service call according to analysis results. The invention further provides a web service processing method based on the event-driven architecture. By means of the web service processing engine system and method based on the event-driven architecture, advantages of open service gateway initiative (OSGi) and service component architecture (SCA) technical standards are blended, so that a web service processing engine based on electronic design automation (EDA) and being flexible, strong and suitable for various heterogeneous environments can be constructed.

Description

technical field [0001] The present invention relates to the field of information technology, in particular to a method for converting the traditional method of synchronously processing WebService messages into an asynchronous processing engine system and processing method based on Event Driven Architecture (EventDriven Architecture, EDA). Background technique [0002] WebService is an important technical support system in Service-Oriented Architecture (SOA). In most cases, WebService is a means of exposing business / technical functions provided by enterprises or organizations as services. Traditional SOA mainly supports synchronous service invocation and execution, that is, after a service consumer requests a service, a connection must be maintained between the service provider and the consumer until the service consumer receives a response. [0003] Therefore, the topology of traditional SOA is service-driven and exists in an open, dynamic, and changeable environment, while ...

AI Technical Summary

Problems solved by technology

[0003] Therefore, the topology of traditional SOA is service-driven and exists in an open, dynamic, and changeable environment, while WebService is characterized by loose coupling, distribution, and autonomy, so the service collaboration method based on time constraints can only be used for In a specific closed environment with precise time, it is not suitable for a software system based on a Web environment

[0004] In addition, there are some service-based collaborative engine systems, which are an application module designed to run in a web container. These systems have more or less the following defects: the deployment mode is only for the web container; third-party class libraries are used to parse With the implementation of WebService, it is unable to process SOAP (Simple Object Access Protocol, Simple Object Access Protocol) messages by itself; it cannot well support industry standards such as SCA (Service Component Architecture, Service Component Framework), OSGi (OpenService Gateway Initiative), etc.; it does not consider security, performance, transactions, etc. related to WebService QoS factor; does not consider integration with other components such as rule engine

Images