A symmetrical two-way decoupling enterprise service description method and service scheduling system

Abstract

The invention discloses a symmetrical bidirectional decoupling enterprise service description method and service scheduling system, and relates to the field of service-based service and system integration. The method separates service semantics and service disposition and introduces an extra attribute to indicate service types (output or input) and scheduling types (synchronous reading, synchronous writing or asynchronous writing). For a type definition, a message structure definition, a service Operation definition and the like, a WSDL2.0 protocol is observed so that better integration with other WSDL description services can be ensured. Compared to the prior art, the method can be used to describe the service demand of a service scheduler and the service description of a service provider through the same mode so as to enable the service scheduler to be decoupled from the service provider in logic, thereby having quite good popularization and application values.

Description

technical field [0001] The invention relates to the field of service-based business and system integration, in particular to a symmetrical bidirectional decoupling enterprise service description method and a service dispatching system. Background technique [0002] Service-oriented architecture (service-oriented architecture, SOA) is widely used in the integration of complex information systems and in the service design of enterprise applications. It integrates different functional units (called services) of applications through well-defined The interface and the contract are connected, so that the service caller does not need to care about the technical implementation details of the service provider, improves the openness of the software system, and reduces the complexity and cost of system integration. [0003] At present, the SOA architecture is mainly implemented through service components (such as CORBA) and Web Service, but the main problem is that although the service...

AI Technical Summary

Problems solved by technology

[0003] At present, the SOA architecture is mainly implemented through service components (such as CORBA) and Web Service, but the main problem is that although the service implementation does not care about how others call it, the service caller solves the connection and connection of the service provider through the ESB. For routing issues, we still need to care about the service interface of the service caller, send a service request (Request) according to the service interface, and understand the response message (Response) of the service provider, so as to process it according to the content of the response message

[0005] With the improvement of users' requirements for system responsiveness (Responsiveness), the concept of asynchrony is more and more widely used in system design. In particular, Ajax technology greatly improves the performance and user experience of websites in web programming. It also further promotes the asynchronous programming model, but there is still a lack of ready-made frameworks for integration in terms of asynchronous service calls

Images