Web service archive

• US 7,487,513 B1
• Filed: 12/30/2003
• Issued: 02/03/2009
• Est. Priority Date: 12/30/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Falter, Timm, Bender, Joachim, Huvar, Martin, Savchenko, Vladimir
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): Cao; Diem K
• Application Number:
  US10/750,065
• Time in Patent Office: 1,862 Days
• Field of Search: 719313-320, 719328-330, 717106-108, 717114-119, 717174-178, 707/100, 709217-219, 709245-246
• US Class Current: 719/320
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/61 Installation

Abstract

A computing device may define a virtual interface to provide an interface for a Web service implementation. The computing device may also create a Web service definition to specify a behavior of the defined virtual interface. The computing device may then provide a Web service archive that includes the virtual interface and the Web service definition.

Claims

1. A computer-implemented method for generating a deployable Web service archive, comprising:

selecting a Web service implementation comprising a plurality of Web service operations and a plurality of Web service parameters;

generating a first virtual interface to the Web service implementation, the first virtual interface to expose a first subset of the Web service operations and Web service parameters;

generating a second virtual interface to the Web service implementation, the second virtual interface to expose a second subset of the Web service operations and Web service parameters different, at least in part, than the first subset of the Web service operations and Web service parameters;

generating a Web service definition for each of the first and second virtual interfaces, each Web service definition specifying a protocol-independent communication type for communications with the Web service implementation via the first and second virtual interfaces, and further specifying a protocol-independent authentication type for authenticating with the Web service implementation via the first and second virtual interfaces;

generating a Web service deployment descriptor for each Web service definition, each Web service deployment descriptor defining a communication protocol to implement the specified protocol-independent communication type of the corresponding Web service definition, and further defining an authentication protocol to implement the specified protocol-independent authentication type of the corresponding Web service definition; and

generating the deployable Web service archive, the deployable Web service archive comprising the Web service implementation, the first and second virtual interfaces to the Web service implementation, the Web service definition for each of the first and second virtual interfaces, and the Web service deployment descriptor for each Web service definition.

2. The computer-implemented method of claim 1, further comprising:

generating a second Web service definition for the first virtual interface, the second Web service definition specifying a second protocol-independent communication type for communications with the Web service implementation different than the first protocol-independent communication type, and further specifying a protocol-independent authentication type for authenticating with the Web service implementation;

generating a second Web service deployment descriptor for the second Web service definition, the second Web service deployment descriptor defining a second communication protocol to implement the specified protocol-independent communication type of the second Web service definition, and further defining a second authentication protocol to implement the specified protocol-independent authentication type of the second Web service definition, wherein the second communication protocol, or the second authentication protocol, or both are different than the first communication protocol and first authentication protocol defined by the first Web service deployment descriptor for the first Web service definition associated with the first Virtual interface; and

wherein

the deployable Web service archive further comprises the second Web service definition and the second Web service deployment descriptor.

3. The computer-implemented method of claim 1, further comprising:

sending the deployable Web service archive to a Web service application server.

4. The computer-implemented method of claim 3, further comprising:

registering the deployable Web service archive with a Web service application server.

5. The computer-implemented method of claim 1, further comprising:

providing the deployable Web service archive to a Universal, Discovery, Description, and Integration (UDDI) Web services directory server.

6. The computer-implemented method of claim 1, wherein the protocol-independent communication type comprises one of:

stateful session communication;

or

stateless communication.

7. The computer-implemented method of claim 1, wherein the protocol-independent authentication type comprises one of:

no authentication;

basic authentication; and

strong authentication.

8. The computer-implemented method of claim 1, wherein:

basic authentication comprises implementation of username and password based authentication; and

wherein

strong authentication comprises implementation of client certificate based authentication.

9. The computer-implemented method of claim 1, wherein:

the first subset of the Web service operations and the Web service parameters represent a first view of the Web service implementation; and

wherein

the second subset of the Web service operations and the Web service parameters represent a second view of the Web service implementation, the second view providing access, at least in part, to functionality of the Web service implementation hidden from the first view and lacking access, at least in part, to functionality of the Web service implementation accessible from the first view.

10. The computer-implemented method of claim 9, further comprising:

publishing the first view of the Web service implementation as a first Web service; and

publishing the second view of the same Web service implementation as a second Web service, separate from the first Web service.

11. The computer-implemented method of claim 1, wherein the first virtual interface to expose the first subset of the Web service operations and Web service parameters comprises:

exposing a parameter using a parameter name different than that specified by the Web service implementation;

exposing the parameter using a data type different than that specified by the Web service implementation; and

exposing the parameter using a default value different than that specified by the Web service implementation.

12. The computer-implemented method of claim 1, wherein generating the deployable Web service archive comprises:

packing the Web service implementation, the first and second virtual interfaces to the Web service implementation, the Web service definition for each of the first and second virtual interfaces, and the Web service deployment descriptor for each Web service definition in a deployable container.

13. The computer-implemented method of claim 12, wherein the deployable container comprises either a Web services container or an Enterprise Java Bean compatible container.

14. A method comprising:

selecting a Web service implementation comprising a plurality of Web service operations and a plurality of Web service parameters;

generating a first virtual interface to the Web service implementation, the first virtual interface to expose a first subset of the Web service operations and Web service parameters;

generating a second virtual interface to the Web service implementation, the second virtual interface to expose a second subset of the Web service operations and Web service parameters different, at least in part, than the first subset of the Web service operations and Web service parameters;

generating a Web service definition for each of the first and second virtual interfaces, each Web service definition specifying a protocol-independent communication type for communications with the Web service implementation via the first and second virtual interfaces, and further specifying a protocol-independent authentication type for authentication with the Web service implementation via the first and second virtual interfaces;

generating a Web service deployment descriptor for each Web service definition, each Web service deployment descriptor defining a communication protocol to implement the protocol-independent communication type specified by the Web service definition, and further defining an authentication protocol to implement the protocol-independent authentication type specified by the Web service definition; and

sending the Web service implementation, the first and second virtual interfaces, the Web service definition for each of the first and second virtual interfaces, and the Web service deployment descriptor for each Web service definition to a Web service directory server.

15. The method of claim 14, wherein sending the Web service implementation, the first and second virtual interfaces, the Web service definition, and the Web service deployment descriptor to the Web service directory server comprises:

packing the Web service implementation, the first and second virtual interfaces, the Web service definition, and the Web service deployment descriptor in a deployable Web services archive; and

sending the deployable Web services archive to the Web service directory server.

16. The method of claim 15, further comprising:

registering the deployable Web service archive with a Web service application server.

17. The method of claim 15, further comprising:

providing the deployable Web service archive to a Universal, Discovery, Description, and Integration (UDDI) Web services directory server.

18. The method of claim 14, further comprising:

generating a second Web service definition specifying a protocol-independent communication type for communication with the Web service implementation via the first virtual interface and a protocol-independent authentication type for authentication with the Web service implementation via the first virtual interface, wherein the protocol-independent communication type and the protocol-independent authentication type of the second Web service definition are different than the protocol-independent communication type and the protocol-independent authentication type of the first Web service definition.

19. The method of claim 14, wherein:

the protocol-independent communication type comprises one of a stateful session communication or a stateless communication; and

wherein

the communication protocol comprises one of HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP) over HTTP, SOAP over File Transfer Protocol (FTP), and SOAP over Simple Mail Transfer Protocol (SMTP).

20. The method of claim 14, wherein:

the first subset of the Web service operations and Web service parameters represent a first view of the Web service implementation; and

wherein

the second subset of the Web service operations and Web service parameters represent a second view of the Web service implementation, the second view providing access, at least in part, to functionality of the Web service implementation hidden from the first view and lacking access, at least in part, to functionality of the Web service implementation accessible from the first view.

21. The method of claim 20, further comprising:

publishing the first view of the Web service implementation as a first Web service; and

publishing the second view of the same Web service implementation as a second Web service, separate from the first Web service.

22. An article of manufacture having instructions stored thereon that, when executed by a processor, cause the processor to perform a method comprising:

selecting a Web service implementation comprising a plurality of Web service operations and a plurality of Web service parameters;

generating a first virtual interface to the Web service implementation, the first virtual interface to expose a first subset of the Web service operations and Web service parameters;

generating a second virtual interface to the Web service implementation, the second virtual interface to expose a second subset of the Web service operations and Web service parameters different, at least in part, than the first subset of the Web service operations and Web service parameters;

generating a Web service definition for each of the first and second virtual interfaces, each Web service definition specifying a protocol-independent communication type for communications with the Web service implementation via the first and second virtual interfaces, and further specifying a protocol-independent authentication type for authentication with the Web service implementation via the first and second virtual interfaces;

generating a Web service deployment descriptor for each Web service definition, each Web service deployment descriptor defining a communication protocol to implement the protocol-independent communication type specified by the Web service definition, and further defining an authentication protocol to implement the protocol-independent authentication type specified by the Web service definition; and

sending the Web service implementation, the first and second virtual interfaces, the Web service definition for each of the first and second virtual interfaces, and the Web service deployment descriptor for each Web service definition to a Web service directory server.

23. The article of manufacture of claim 22, wherein sending the Web service implementation, the first and second virtual interfaces, the Web service definition, and the Web service deployment descriptor to the Web service directory server comprises:

packing the Web service implementation, the first and second virtual interfaces, the Web service definition, and the Web service deployment descriptor in a deployable Web services archive; and

sending the deployable Web services archive to the Web service directory server.

24. The article of manufacture of claim 23, wherein the method further comprises:

registering the deployable Web service archive with a Web service application server.

25. The article of manufacture of claim 23, wherein the method further comprises:

providing the deployable Web service archive to a Universal, Discovery, Description, and Integration (UDDI) Web services directory server.

26. The article of manufacture of claim 22, further comprising:

generating a second Web service definition specifying a protocol-independent communication type for communication with the Web service implementation via the first virtual interface and a protocol-independent authentication type for authentication with the Web service implementation via the first virtual interface, wherein the protocol-independent communication type and the protocol-independent authentication type of the second Web service definition are different than the protocol-independent communication type and the protocol-independent authentication type of the first Web service definition.

27. The article of manufacture of claim 22, wherein:

the protocol-independent authentication type comprises one of no authentication, basic authentication, and strong authentication; and

wherein

the authentication protocol comprises one of HyperText Transfer Protocol (HTTP) with user name and password, HTTP secured through the Secure Socket Layer (SSL), and X.509 Client Certificates using HTTP secured through SSL.

28. The article of manufacture of claim 22, wherein:

the first subset of the Web service operations and Web service parameters represent a first view of the Web service implementation; and

wherein

the second subset of the Web service operations and Web service parameters represent a second view of the Web service implementation, the second view providing at least partial access to functionality of the Web service implementation hidden from the first view and lacking, at least partially, access to functionality of the Web service implementation accessible from the first view.

29. The article of manufacture of claim 28, wherein the method further comprises:

publishing the first view of the Web service implementation as a first Web service; and

publishing the second view of the same Web service implementation as a second Web service, separate from the first Web service.

30. A system having at least one processor comprising:

means for selecting a Web service implementation comprising a plurality of Web service operations and a plurality of Web service parameters;

means for generating a first virtual interface to the Web service implementation, the first virtual interface to expose a first subset of the Web service operations and Web service parameters;

means for generating a second virtual interface to the Web service implementation, the second virtual interface to expose a second subset of the Web service operations and Web service parameters different, at least in part, than the first subset of the Web service operations and Web service parameters;

means for generating a Web service definition for each of the first and second virtual interfaces, each Web service definition comprising means for specifying a protocol-independent communication type for communications with the Web service implementation via the first and second virtual interfaces, and further comprising means for specifying a protocol-independent authentication type for authenticating with the Web service implementation via the first and second virtual interfaces;

means for generating a Web service deployment descriptor for each Web service definition, each Web service deployment descriptor comprising means for defining a communication protocol to implement the specified protocol-independent communication type of the corresponding Web service definition, and further comprising means for defining an authentication protocol to implement the specified protocol-independent authentication type of the corresponding Web service definition; and

means for generating a deployable Web service archive comprising the Web service implementation, the first and second virtual interfaces to the Web service implementation, the Web service definition for each of the first and second virtual interfaces, and the Web service deployment descriptor for each Web service definition.

31. The system of claim 30, wherein:

the protocol-independent communication type comprises one of stateful session communication or stateless communication; and

wherein

the communication protocol comprises one of HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP) over HTTP, SOAP over File Transfer Protocol (FTP), and SOAP over Simple Mail Transfer Protocol (SMTP).

32. The system of claim 30, wherein:

the protocol-independent authentication type comprises one of no authentication, basic authentication, and strong authentication; and

wherein

the authentication protocol comprises one of HyperText Transfer Protocol (HTTP) with user name and password, HTTP secured through the Secure Socket Layer (SSL), and X.509 Client Certificates using HTTP secured through SSL.

33. The system of claim 30, wherein:

the first subset of the Web service operations and Web service parameters represent a first view of the Web service implementation; and

wherein

the second subset of the Web service operations and Web service parameters represent a second view of the Web service implementation, the second view comprising means for providing access, at least in part, to functionality of the Web service implementation hidden from the first view and lacking access, at least in part, to functionality of the Web service implementation accessible from the first view.

34. The computer-implemented method of claim 33, further comprising:

means for publishing the first view of the Web service implementation as a first Web service; and

means for publishing the second view of the same Web service implementation as a second Web service, separate from the first Web service.

35. The system of claim 30, wherein the first virtual interface to expose the first subset of the Web service operations and Web service parameters comprises one or more of:

means for exposing a parameter using a parameter name different than that specified by the Web service implementation;

means for exposing the parameter using a data type different than that specified by the Web service implementation; and

means for exposing the parameter using a default value different than that specified by the Web service implementation.