Port type agnostic proxy support for web services intermediates

• US 7,464,142 B2
• Filed: 12/12/2003
• Issued: 12/09/2008
• Est. Priority Date: 12/12/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Flurry, Gregory Alan, Holdsworth, Simon Antony James, Snell, James Michael
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Nooristany; Sulaiman
• Application Number:
  US10/734,773
• Publication Number:
  US 20050132086A1
• Time in Patent Office: 1,824 Days
• Field of Search: 709217-219, 709/203, 709223-227, 719/328, 719/311
• US Class Current: 709/217
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods, systems, and products are disclosed in which port type agnostic proxy support for web services intermediaries is typically provided by receiving in a web services intermediary a request for execution of a web services operation, wherein the request includes parametric information from which an endpoint for a target service that supports the operation can be identified; identifying, in dependence upon the parametric data, the endpoint for a target service that supports the operation; creating a target service request for execution of the operation on the target service; and issuing the target service request to the target service. Exemplary embodiments typically also include the return path of request-response processing; receiving in the intermediary a response from the target service; creating in the intermediary, in dependence upon the response from the target service, a response from the intermediary; and returning the response from the intermediary to the requesting client.

Claims

1. A method of port type agnostic proxy support for web services intermediaries, the method comprising:

receiving in a web services intermediary a request for execution of a web services operation, wherein;

the web services intermediary includes a proxy, wherein no configuration data available to the proxy describes an endpoint of the target service and the requester submits request for operations in port types completely unknown to the intermediary; and

the request includes parametric information from which an endpoint for a target service that supports the operation is identified;

identifying, by the web services intermediary in dependence upon the parametric data, the endpoint for a target service that supports the operation;

creating, by the web services intermediary, a target service request for execution of the operation on the target service, further comprising;

composing a request in a data structure useful in a binding-neutral interface; and

calling the binding-neutral interface, passing the request as a call parameter; and

issuing, by the web services intermediary, the target service request to the target service.

2. The method of claim 1 wherein the target service request as created and issued to the target service bears unexamined and unmodified message contents of the request received in the web services intermediary.

3. The method of claim 1 further comprising identifying to a requester an endpoint of the web services intermediary as an endpoint that supports the operation.

4. The method of claim 1 wherein the parametric information includes a port type for the operation.

5. The method of claim 1 wherein identifying, in dependence upon the parametric information, the endpoint for a target service that supports the operation further comprises:

identifying, in dependence upon the parametric information, a multiplicity of endpoints of target services that support the operation; and

selecting one endpoint from the multiplicity of endpoints in accordance with selection rules.

6. The method of claim 5 wherein:

the parametric information includes a port type for the operation, and

identifying, in dependence upon the parametric information, a multiplicity of endpoints of target services that support the operation comprises identifying from a registry, in dependence upon the port type, a multiplicity of target services for the port type.

7. The method of claim 5 wherein selecting one endpoint from the multiplicity of endpoints further comprises selecting one endpoint from the multiplicity of endpoints in accordance with selection rules for load balancing among target services.

8. The method of claim 1 wherein issuing the target service request to the target service comprises calling one or more member methods in a binding-neutral interface.

9. The method of claim 1 further comprising:

receiving in the intermediary a response from the target service;

creating in the intermediary, in dependence upon the response from the target service, a response from the intermediary; and

returning the response from the intermediary to the requesting client.