Web service client extensions

• US 7,694,140 B1
• Filed: 12/30/2003
• Issued: 04/06/2010
• Est. Priority Date: 12/30/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Sachenko, Vladimir, Huvar, Martin, Falter, Timm
• Primary Examiner(s): Moise; Emmanuel L
• Assistant Examiner(s): PHAM, LUU T
• Application Number:
  US10/749,735
• Time in Patent Office: 2,289 Days
• Field of Search: 709/230, 709/203, 726/3, 713/150, 713/170
• US Class Current: 713/170
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A computing device may access a description of a Web service. The computing device may generate a Web service proxy based, at least in part, on the accessed description of the Web service. The computing device may provide a client protocol implementation to extend the functionality of the generated Web service client proxy. A feature of the client protocol implementation may be set to define a behavior of the Web service client without regenerating the Web service client proxy.

Claims

1. A method in a Web service provider communicatively interfaced with a plurality of Web service clients, comprising:

obtaining a description of a Web service comprising protocol-independent business logic;

generating a Web service client proxy based, at least in part, on the description obtained, wherein the generated Web service client proxy comprises the protocol-independent business logic in an executable format and is extended with one or more client protocol implementations;

generating a first virtual interface to the Web service based on the description obtained, the first virtual interface comprising a mapping of the protocol-independent business logic of the Web service to a first transport protocol that provides a first Web service client access to the protocol-independent business logic of the Web service, and wherein the first Web service client comprises a Web service client authentication extension having a user selectable authentication protocol therein for specifying the authentication protocol to be implemented by the Web service client proxy between the virtual interface and the first Web service client, without regenerating the Web service client proxy;

receiving and implementing the user specified authentication protocol without regenerating the Web service client proxy, wherein the user specified authentication protocol is received from the first Web service client via a logical port between the first Web service client and the Web service client proxy;

processing message traffic exchanged between the Web service client proxy and the first Web service client via the first virtual interface in accordance with the first transport protocol and the user specified authentication protocol implemented by the Web service client proxy;

generating a second virtual interface to the Web service based on the description obtained, the second virtual interface comprising a mapping of the protocol-independent business logic of the Web service to a second transport protocol different than the first transport protocol, wherein the second virtual interface to provide a second Web service client access to the protocol-independent business logic of the Web service without regenerating the Web service; and

processing message traffic exchanged between the Web service client proxy and the second Web service client via the second virtual interface in accordance with the second transport protocol, and in accordance with a second user selectable authentication protocol received and implemented without regenerating the Web service client proxy.

2. The method of claim 1, wherein the first user selectable authentication protocol requires the use of an X.509 authentication certificate.

3. The method of claim 1, wherein the first transport protocol is selected from the group comprising HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP), SOAP over HTTP, SOAP over File Transfer Protocol (FTP), SOAP over Simple Mail Transfer Protocol (SMTP), and HTTP over Secure Socket Layer (HTTPS);

and

wherein the second transport protocol is selected from the group comprising HTTP, SOAP, SOAP over HTTP, SOAP over FTP, SOAP over SMTP, and HTTPS, wherein the second transport protocol selected is different from the first transport protocol selected.

4. The method of claim 1, further comprising:

generating the Web service client proxy responsive to a request, the Web service client proxy comprising the first virtual interface and the second virtual interface, wherein the Web service client proxy to execute at a Web service proxy server separate from the Web service provider.

5. The method of claim 1, wherein the first transport protocol comprises an authentication mechanism and a transport guarantee mechanism.

6. The method of claim 5, wherein the first transport protocol further comprises a specified port binding.

7. The method of claim 1, wherein obtaining the description of the Web service comprises:

obtaining a Web Service Definition Language (WSDL) document from a Universal Description, Discovery, and Integration (UDDI) directory, the UDDI directory comprising a plurality of WSDL documents, each describing one of a plurality of Web services accessible via the Web service provider, wherein the WSDL document obtained describes the Web service comprising the protocol-independent business logic.

8. A computer-readable storage medium having instructions stored thereon that, when executed by a processor in a Web service provider, cause the Web server provider to execute a method comprising:

obtaining a description of a Web service comprising protocol-independent business logic;

generating a Web service client proxy based at least in part on the description obtained, wherein the generated Web service client proxy comprises the protocol-independent business logic in an executable format and is extended with one or more client protocol implementations;

generating a first virtual interface to the Web service based on the description obtained, the first virtual interface comprising a mapping of the protocol-independent business logic of the Web service to a first transport protocol that provides a first Web service client access to the protocol-independent business logic of the Web service, and wherein the first Web service client comprises a Web service client authentication extension having a user selectable authentication protocol therein for specifying the authentication protocol to be implemented by the Web service client proxy between the virtual interface and the first Web service client, without regenerating the Web service client proxy;

receiving and implementing the user specified authentication protocol without regenerating the Web service client proxy, wherein the user specified authentication protocol is received from the first Web service client via a logical port between the first Web service client and the Web service client proxy;

processing message traffic exchanged between the Web service client proxy and the first Web service client via the first virtual interface in accordance with the first transport protocol and the user specified authentication protocol implemented by the Web service client proxy;

generating a second virtual interface to the Web service based on the description obtained, the second virtual interface comprising a mapping of the protocol-independent business logic of the Web service to a second transport protocol different than the first transport protocol, wherein the second virtual interface to provide a second Web service client access to the protocol-independent business logic of the Web service without regenerating the Web service; and

processing message traffic exchanged between the Web service client proxy and the second Web service client via the second virtual interface in accordance with the second transport protocol, and in accordance with a second user selectable authentication protocol received and implemented without regenerating the Web service client proxy.

9. The computer-readable storage medium of claim 8, wherein the authentication protocol requires the use of an X.509 authentication certificate.

10. The computer-readable storage medium of claim 8, wherein the first transport protocol is selected from the group comprising HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP), SOAP over HTTP, SOAP over File Transfer Protocol (FTP), SOAP over Simple Mail Transfer Protocol (SMTP), and HTTP over Secure Socket Layer (HTTPS);

and

wherein the second transport protocol is selected from the group comprising HTTP, SOAP, SOAP over HTTP, SOAP over FTP, SOAP over SMTP, and HTTPS, wherein the second transport protocol selected is different from the first transport protocol selected.

11. The computer-readable storage medium of claim 8, further comprising:

generating the Web service client proxy responsive to a request, the Web service client proxy comprising the first virtual interface and the second virtual interface, wherein the Web service client proxy to execute at a Web service proxy server separate from the Web service provider.

12. The computer-readable storage medium of claim 8, wherein the first transport protocol comprises an authentication mechanism and a transport guarantee mechanism.

13. The computer-readable storage medium of claim 12, wherein the first transport protocol further comprises a specified port binding.

14. The computer-readable storage medium of claim 8, wherein obtaining the description of the Web service comprises:

obtaining a Web Service Definition Language (WSDL) document from a Universal Description, Discovery, and Integration (UDDI) directory, the UDDI directory comprising a plurality of WSDL documents, each describing one of a plurality of Web services accessible via the Web service provider, wherein the WSDL document obtained describes the Web service comprising the protocol-independent business logic.