Runtime execution of a reliable messaging protocol

• US 20070067475A1
• Filed: 09/21/2005
• Published: 03/22/2007
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Videlov, Vladimir, Savchenko, Vladimir, Angelov, Dimitar, Baikov, Chavdar
• Granted Patent: US 7,711,836 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]

Abstract

A system and method for the lifecycle of a protocol processing a message is described. In one embodiment, in a stateless object-oriented runtime environment, an instance of a reliable messaging protocol is used to process a message. The processing including receiving a message and performing operations based on said message.

Claims

1. A method, comprising:

processing a Web services message within a stateless object oriented runtime environment using an instance of a reliable messaging protocol, said processing comprising;

receiving a sequence identification request from an endpoint;

generating the sequence identification for the message;

transmitting the sequence identification to the endpoint; and

receiving the message from the endpoint.

2. The method of claim 1, wherein the processing further comprises:

invoking a timer after the receipt of the message from the endpoint, wherein if the timer expires the processing of the message is terminated.

3. The method of claim 1, wherein the message received from the endpoint comprises:

the sequence identification;

a message identifier; and

message data.

4. The method of claim 3, further comprising:

transmitting an acknowledgment to the endpoint upon receipt of the message.

5. The method of claim 3, further comprising:

placing the message into an hibernated state.

6. The method of claim 5, wherein hibernating further comprises:

serializing the reliable messaging protocol instance'"'"'s context;

creating a system message; and

persisting said system message.

7. The method of claim 5, further comprising:

awakening said message from the hibernated state.

8. A computing system comprising a machine, said computing system also comprising instructions disposed on a computer readable medium, said instructions capable of being executed by said machine to perform a method, said method comprising:

processing a Web services message within a stateless object oriented runtime environment using an instance of a reliable messaging protocol, said processing comprising;

receiving a sequence identification request from an endpoint;

generating the sequence identification for the message;

transmitting the sequence identification to the endpoint; and

receiving the message from the endpoint.

9. The computing system of claim 8, wherein the processing further comprises:

invoking a timer after the receipt of the message from the endpoint, wherein if the timer expires the processing of the message is terminated.

10. The computing system of claim 8, wherein the message received from the endpoint comprises:

the sequence identification;

a message identifier; and

message data.

11. The computing system of claim 10, further comprising:

transmitting an acknowledgment to the endpoint upon receipt of the message.

12. The computing system of claim 10, further comprising:

placing the message into an hibernated state.

13. The computing system of claim 12, wherein hibernating further comprises:

serializing the reliable messaging protocol instance'"'"'s context;

creating a system message; and

persisting said system message.

14. The computing system of claim 12, further comprising:

awakening said message from the hibernated state.

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

processing a Web services message within a stateless object oriented runtime environment using an instance of a reliable messaging protocol, said processing comprising;

receiving a sequence identification request from an endpoint;

generating the sequence identification for the message;

transmitting the sequence identification to the endpoint; and

receiving the message from the endpoint.

16. The article of manufacture of claim 15, wherein the processing further comprises:

invoking a timer after the receipt of the message from the endpoint, wherein if the timer expires the processing of the message is terminated.

17. The article of manufacture of claim 15, wherein the message received from the endpoint comprises:

the sequence identification;

a message identifier; and

message data.

18. The article of manufacture of claim 15, further comprising:

transmitting an acknowledgment to the endpoint upon receipt of the message.

19. The article of manufacture of claim 15, further comprising:

placing the message into an hibernated state.

20. The article of manufacture of claim 19, further comprising:

awakening said message from the hibernated state.