Web services hibernation

• US 7,721,293 B2
• Filed: 09/21/2005
• Issued: 05/18/2010
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Savchenko, Vladimir S., Angelov, Dimitar, Baikov, Chavdar S.
• Primary Examiner(s): Backer; Firmin
• Assistant Examiner(s): BELCHER, HERMAN A
• Application Number:
  US11/232,708
• Publication Number:
  US 20070067383A1
• Time in Patent Office: 1,700 Days
• Field of Search: 709/203, 709/217
• US Class Current: 719/313
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level

Abstract

A method is described that involves comprising, during runtime in an object-oriented environment, invoking, from an object, a first Web services endpoint method to process a first message by: invoking the first Web services endpoint method through a first interface according to an endpoint method invocation format, where, the first Web services endpoint method is implemented with a first component that is provided one or more services by a first container. The method also involves invoking, from the object, a second Web services endpoint method to process a second message by: invoking the second Web services endpoint method through a second interface according to the endpoint method invocation format. The second Web services endpoint method is implemented with a second component that is provided one or more services by a second container. The first and second containers have respective interfaces that are different.

Claims

1. A method comprising:

reading program code from memory and processing said program code with one or more processors to perform the following;

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing at least one of a plurality of stateless protocols to support a Web service to which said Web services message pertains, each one of said protocols of said plurality of protocols performing one or more operations that contribute to a different part of said processing;

invoking a stateless Web services reliable messaging protocol instance to place the processing into an hibernated state;

halting the execution of the plurality of protocols performing operations as a part of the processing upon the invocation of the stateless Web services reliable messaging protocol instance;

serializing message data of the Web services message and state information of the halted protocols;

creating a messaging system message comprising the serialized message data and state information;

persisting the messaging system message;

retrieving the messaging system message;

deserializing the messaging system message;

resuming the execution of the plurality of protocols using the state information of the messaging system message to continue processing the Web services message from the point at which the execution was halted.

2. The method of claim 1, wherein the message data of the Web services message comprises a body of the Web services message and the Web services message'"'"'s header information.

3. The method of claim 2, wherein the message data of the Web services message further comprises an attachment to the Web services message.

4. The method of claim 1, wherein the messaging system message further comprises information from a Simple Object Access Protocol (SOAP) header of the Web services message, including:

a sequence identification of the Web services message;

a message number of the Web services message; and

a last message flag.

5. The method of claim 1, further comprising:

recording that the messaging system message has been persisted in a messaging system processing array.

6. The method of claim 1, further comprising:

processing another Web services message while the messaging system message is persisted.

7. An article of manufacture storing program code which, when executed by a machine, causes the machine to perform a method, the method comprising:

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing at least one of a plurality of stateless protocols to support a Web service that said Web services message pertains to, each one of said protocols of said plurality of protocols performing one or more operations that contribute to a different part of said processing;

invoking a stateless Web services reliable messaging protocol instance to place the processing into an hibernated state;

halting the execution of the plurality of protocols performing operations as a part of the processing upon the invocation of the stateless Web services reliable messaging protocol instance;

serializing message data of the Web services message and state information of the halted protocols;

creating a messaging system message comprising the serialized message data and state information;

persisting the messaging system message;

retrieving the messaging system message;

deserializing the message system message;

resuming the execution of the plurality of protocols using the state information of the messaging system message to continue processing the Web services message from the point at which the execution was halted.

8. The article of manufacture of claim 7, wherein the message data of the Web services message comprises a body of the Web services message and the Web services message'"'"'s header information.

9. The article of manufacture of claim 7, wherein the message data of the Web services message further comprises an attachment to the Web services message.

10. The article of manufacture of claim 7, wherein the messaging system further comprises information from a Simple Object Access Protocol (SOAP) header of the Web services message, including:

a sequence identification of the Web services message;

a message number of the Web services message; and

a last message flag.

11. The article of manufacture of claim 7, further comprising:

recording that that messaging system message has been persisted in a messaging system processing array.

12. The article of manufacture of claim 7, further comprising:

processing another Web services message while the messaging system message is persisted.

13. A system comprising:

a processor; and

a memory coupled to the processor, the memory to store instructions which when executed by the processor cause the system to perform a method, the method comprising;

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing at least one of a plurality of stateless protocols to support a Web service that said Web services message pertains to, each one of said protocols of said plurality of protocols performing one or more operations that contribute to a different part of said processing;

invoking a stateless Web services reliable messaging protocol instance to place the processing into an hibernated state;

halting the execution of the plurality of protocols performing operations as a part of the processing upon the invocation of the stateless Web services reliable messaging protocol instance;

serializing message data of the Web services message and the state information of the halted protocols;

creating a messaging system message comprising the serialized message data and state information;

persisting the messaging system message;

retrieving the messaging system message;

deserializing the messaging system message;

resuming the execution of the plurality of protocols using the state information of the messaging system message to continue processing the Web services message from the point at which the execution was halted.

14. The method of claim 13, wherein the message of data of the Web services message comprises a body of the Web services message and the Web services message'"'"'s header information.

15. The method of claim 14, wherein the message data of the Web services message further comprises an attachment to the Web services message.

16. The method of claim 13, wherein the messaging system message further comprises information from a Simple Object Access Protocol (SOAP) header of the Web services message, including:

a sequence identification of the Web services message;

a message number of the Web services message; and

a last message flag.

17. The method of claim 13, further comprising:

recording that the messaging system message has been persisted in a messaging system processing array.

18. The method of claim 13, further comprising:

processing another Web services message while the messaging system message is persisted.