Method and apparatus for managing web services within a computer network system
View Patent ↗The present invention is directed to a method and apparatus that manages Web Services within an enterprise having an intranet. In an embodiment of the present invention, a Management Server (MS) is connected with a Management Server Client (MSC) via a network. The MS and MSC work in concert to manage Web Services by providing performance monitoring, security, contract and Service Level Agreement (SLA) management, and other performance enhancements in a unique, pluggable, expandable architecture. In another embodiment of the present invention, the MS is connected to an MSC via a network using a Web Services Application Programming Interface (API). The MSC is connected with a server for providing Web Services to a client. The Web Services are provided to the client through the MSC. The MS provides configuration data to the MSC for management of the Web Services provided through the MSC. In yet another embodiment, the MS is connected to a plurality of MSC's. Each MSC is connected with a plurality of servers. Each of the servers can provide Web Services to a plurality of clients. The Web Services are provided to each client through at least one MSC. In a further embodiment, the Web Services are provided to a client through an MSC that is connected to the server.
1. A client and server computer system, the system comprising:
a network;
a client connected with said network;
a server connected with said client via said network;
a Management Server Client (MSC) connected with said server;
an Application Programming Interface (API) for allowing access only to licensed MSC's;
a Management Server (MS) connected with said MSC via said API, said MS providing configuration data to said MSC; and
a pipeline within said MSC and wherein said MSC uses said pipeline to manage said services provided from said server to said client, said pipeline comprising a plurality of components, said plurality of components comprising a caching component for caching a service from said server;
wherein said client sends requests for services from said server to said client;
wherein said MSC intercepts said requests for said services from said server to said client;
wherein said services are provided to said client via said MSC;
wherein upon receiving said configuration data via said API, said MSC manages services provided from said server to said client;
wherein said caching component is configured to read a Simple Object Access Protocol (SOAP) request from said client, to decide which parameters in said SOAP Request from said client would affect a SOAP response from said server, to ignore parameters in said SOAP request from said client that would not affect said SOAP response, and to compare whether said parameters from said client that would effect said SOAP response are equivalent to parameters stored in said caching component.
2. The system of claim 1 , wherein said caching component sends a SOAP response stored in said caching component if said parameters from said client that would effect said SOAP response are equivalent to said parameters stored in said caching component.
3. The system of claim 1 , wherein said caching component forwards said parameters from said client that would effect said SOAP response to said server to generate said SOAP response if said parameters from said client that would effect said SOAP response are not equivalent to said parameters stored in said caching component.
4. A client and server computer system, the system comprising:
a network;
a client connected with the network;
a server connected with the client via the network, the client adapted to send requests for services from the server to the client;
a Management Server Client (MSC) connected with the server, the MSC adapted to intercept the requests for the services from the server to the client, the services being provided to the client via the MSC; and
a pipeline within the MSC used by the MSC to manage the services provided from the server to the client, the pipeline comprising a caching component for caching a service from said server;
wherein the caching component is configured to read a Simple Object Access Protocol (SOAP) request from the client, to decide which parameters in the SOAP Request from the client would affect a SOAP response from the server, to ignore parameters in the SOAP request from the client that would not affect the SOAP response, and to compare whether the parameters from the client that would effect the SOAP response are equivalent to parameters stored in the caching component.
5. The system of claim 4 , further comprising an Application Programming Interface (API) for allowing access only to licensed MSC's.
6. The system of claim 5 , further comprising a Management Server (MS) connected with the MSC via the API, the MS adapted to provide configuration data to the MSC, wherein upon receiving the configuration data via the API, the MSC manages services provided from the server to the client.
7. The system of claim 4 , wherein the caching component sends a SOAP response stored in the caching component if the parameters from the client that would effect the SOAP response are equivalent to the parameters stored in the caching component.
8. The system of claim 4 , wherein the caching component forwards the parameters from the client that would effect the SOAP response to the server to generate the SOAP response if the parameters from the client that would effect the SOAP response are not equivalent to the parameters stored in the caching component.
9. A network system for managing services provided from first and second plurality of servers to a client, the system comprising:
an Application Programming Interface (API);
a first Management Server Client (MSC) connected with said first plurality of servers a second MSC connected with said second plurality of servers;
a Management Server (MS) connected with said first and second MSc's; and
a pipeline used by at least one of the first and second MSc's to manage the services provided from the corresponding first or second server to the client, the pipeline comprising a caching component for caching a service from the server;
wherein said first and second MSc's are licensed MSc's;
wherein said API only allows access to licensed MSc's;
wherein said MS provides configuration data to said first and second MSc's via said API;
wherein upon receiving said configuration data via said API, said first MSC manages services provided from said first plurality of servers to said client and said second MSC manages services provided from said second plurality of servers server to said client; and
wherein the caching component is configured to read a Simple Object Access Protocol (SOAP) request from the client, to decide which parameters in the SOAP Request from the client would affect a SOAP response from the server, to ignore parameters in the SOAP request from the client that would not affect the SOAP response, and to compare whether the parameters from the client that would effect the SOAP response are equivalent to parameters stored in the caching component.
10. The system of claim 9 , wherein the caching component sends a SOAP response stored in the caching component if the parameters from the client that would effect the SOAP response are equivalent to the parameters stored in the caching component.
11. The system of claim 9 , wherein the caching component forwards the parameters from the client that would effect the SOAP response to the server to generate the SOAP response if the parameters from the client that would effect the SOAP response are not equivalent to the parameters stored in the caching component.