Extendable and completely self-defined unified interface service platform

Abstract

The invention is applied in the field of J2EE (Java 2 Platform, Enterprise Edition) standardized Web service, discloses an on-line identifying, on-line extending and unified processing method for Web service, and is a Web service allocating and processing platform constructed on the basis of the RESTFUL thinking. The platform comprises a service allocation monitoring module and a service processing module, wherein the service allocation monitoring module is used for allocating Web service and extending Web service through pages, used for supporting service on-line management, used for operating on-line and off-line service through pages, and used for realizing service unified allocation in two manners of database scripts and JAR package plugins; the service processing module is used for responding an application client request through the HTTP (Hyper Text Transport Protocol) basic method, and adopts URI (Uniform Resource Identifier) to describe service resources. The platform supports the on-line real-time monitoring of the service response situation, can realize real-time query and monitoring of the service processing condition by allocating pages, can control the visitor volume, and can conduct on-line adjustment; the platform can be widely applied in the application environments which need fast and flexible allocation of Web service, and has the characteristics of high stability and high expansibility.

Description

technical field [0001] The invention relates to configuration, monitoring and application processing of Web services, in particular to a service interface custom configuration and service processing platform. Background technique [0002] At present, the development of Web services is generally based on the Web service platform of traditional SOAP, WSDL, and UDDI protocols. The protocols are complex and the development is difficult. Every change needs to restart the system to take effect, which is not flexible enough; [0003] Traditional web services are hard-coded and packaged into services, which cannot be expanded and customized. In addition, traditional web services use the SAOP protocol, which determines that both requests and returns must be in XML format, and other formats, such as JSON format, cannot be used; [0004] The number of traditional web services depends on the capacity of the system itself, which cannot be controlled before reaching the maximum capacity, ...

AI Technical Summary

Problems solved by technology

[0002] At present, the development of Web services is generally based on the Web service platform of traditional SOAP, WSDL, and UDDI protocols. The protocols are complex and the development is difficult. Every change needs to restart the system to take effect, which is not flexible enough;

[0003] Traditional web services are hard-coded and packaged into services, which cannot be expanded and customized. In addition, traditional web services use the SAOP protocol, which determines that both requests and returns must be in XML format, and other formats, such as JSON format, cannot be used;

[0004] The number of traditional web services depends on the capacity of the system itself, which cannot be controlled before reaching the maximum capacity, causing the system to crash when overloaded, and it is also impossible to use a general method to personalize the amount of access for specific users;

[0005] Traditional web services abstract the web by defining personalized interfaces, without using the basic methods of HTTP, which reduces the interoperability of service calls;

Images