Web services message processing runtime framework

US9690637B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9690637-B2
Application numberUS-79409410-A
CountryUS
Kind codeB2
Filing dateJun 4, 2010
Priority dateSep 21, 2005
Publication dateJun 27, 2017
Grant dateJun 27, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method is described that involves creating a reliable messaging object that includes a configuration context object. The reliable messaging object is created by reading configuration data from the configuration context object and writing instructions for delivery of the reliable messaging object based on the configuration data. The reliable messaging object is received in a messaging system independent from a web services runtime framework. The reliable messaging object is processed in the messaging system by placing the reliable messaging object into a queue and performing a quality of service check on the reliable messaging object.

First claim

Opening claim text (preview).

I claim: 1. A method comprising: creating a reliable messaging object comprising a configuration context object, wherein the configuration context object describes a state of a reliable messaging protocol associated with a first hibernated message; receiving the reliable messaging object in a messaging system independent from a web services runtime framework; and processing, using one or more processors, the reliable messaging object in the messaging system. 2. The method of claim 1 , wherein the configuration context object comprises a serialized web services message object and configuration data. 3. The method of claim 1 , wherein creating the reliable messaging object comprises: reading configuration data from the configuration context object; writing instructions for delivery of the reliable messaging object based on configuration data associated with the configuration context object; and stopping the web services runtime framework at an endpoint after creating the reliable messaging object. 4. The method of claim 3 , further comprising writing sequence data to the reliable messaging object, wherein sequence data associated with the reliable messaging object tracks sequences of messages exchanged between endpoints over a communications network. 5. The method of claim 1 , wherein processing the reliable messaging object in the messaging system comprises: storing a state of the web services runtime framework in a database; storing the received reliable messaging object in the database; placing the reliable messaging object into a queue; performing a quality of service check on the reliable messaging object; and invoking an instance of an event handler to restart the web services runtime framework after the quality of service check has been performed on the reliable messaging object. 6. The method of claim 5 , wherein performing the quality of service check on the reliable messaging object comprises: determining a delivery policy for the reliable messaging object from instructions for delivery written to the reliable messaging object; checking if the reliable messaging object satisfies the delivery policy; sending a first portion of the reliable messaging object that satisfies the delivery policy to an event handler object; and retaining a second portion of the reliable messaging object that does not satisfy the delivery policy. 7. The method of claim 5 , wherein invoking the instance of the event handler to restart the web services runtime framework comprises: recreating the configuration context object; applying a configuration associated with the configuration context object to the web services runtime framework; and restarting the web services runtime framework after applying the configuration from the configuration context object. 8. A system comprising: a software application coupled to an endpoint on a communications network to send or receive business data over the communications network; a web services runtime framework coupled to the endpoint, the web services runtime framework having one or more processors to invoke an instance of a reliable messaging protocol to process a web services message object, the instance of the reliable messaging protocol to create a reliable messaging object comprising the web services message object and invoke an instance of a messaging system independent from the web services runtime framework at the endpoint on the communications network, the messaging system independent from the web services runtime framework coupled to the endpoint on the communications network to provide services to process the reliable messaging object; an instance of an event handler coupled to the messaging system to invoke calls to the web services runtime framework after the messaging system has processed the reliable messaging object; and an instance of a Hyper Text Transfer Protocol (HTTP) coupled to the endpoint to enable sending and receiving a web services message over the communications network. 9. The system of claim 8 , wherein the messaging system independent from the web services runtime framework comprises: a service to monitor delivery of the reliable messaging object created by the instance of the reliable messaging protocol; a service to store the reliable messaging object to a database coupled to the web services runtime framework on the endpoint on the communications network; a service to queue the reliable messaging object; a service to perform quality of service checks on the reliable messaging object; and a service to send or retain parts of the reliable messaging object according to a delivery policy specified by the instance of the reliable messaging protocol. 10. A non-transitory machine-readable storage medium comprising instructions therein that when executed by a machine cause the machine to perform a method, the method comprising: creating a reliable messaging object comprising a configuration context object, wherein the configuration context object describes a state of a reliable messaging protocol associated with a first hibernated message; receiving the reliable messaging object in a messaging system messaging system independent from a web services runtime framework; and processing the reliable messaging object in the messaging system. 11. The non-transitory machine-readable storage medium of claim 10 , wherein the method further comprises: reading configuration data from the configuration context object; writing instructions for delivery of the reliable messaging object based on configuration data from the configuration context object; and stopping the web services runtime framework at an endpoint after creating the reliable messaging object. 12. The non-transitory machine-readable storage medium of claim 11 , wherein the method further comprises writing sequence data to the reliable messaging object, wherein sequence data associated with the reliable messaging object tracks sequences of messages exchanged between endpoints over a communications network. 13. The non-transitory machine-readable storage medium of claim 10 , wherein the method further comprises: storing a state of the web services runtime framework in a database; storing the received reliable messaging object in the database; placing the reliable messaging object into a queue; performing a quality of service check on the reliable messaging object; and invoking an instance of an event handler to restart the web services runtime framework after the quality of service check has been performed on the reliable messaging object. 14. The non-transitory machine-readable storage medium of claim 13 , wherein the method further comprises: determining a delivery policy for the reliable messaging object from instructions for delivery written to the reliable messaging object; checking if the reliable messaging object satisfies the delivery policy; sending a first portion of the reliable messaging object that satisfies the delivery policy to an event hander object; and retaining a second portion of the reliable messaging object that does not satisfy the delivery policy. 15. The non-transitory machine-readable storage medium of claim 13 , wherein the method further comprises: recreating the configuration context object; applying a configuration from the configuration context object to the web services runtime framework; and restart the web services runtime framework after applying the configuration from the configuration context object.

Assignees

Inventors

Classifications

  • Tax preparation or submission · CPC title

  • based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

  • G06F9/546Primary

    Message passing systems or structures, e.g. queues · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9690637B2 cover?
A method is described that involves creating a reliable messaging object that includes a configuration context object. The reliable messaging object is created by reading configuration data from the configuration context object and writing instructions for delivery of the reliable messaging object based on the configuration data. The reliable messaging object is received in a messaging system i…
Who is the assignee on this patent?
Angelov Dimitar, Sap Se
What technology area does this patent fall under?
Primary CPC classification G06F9/546. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 27 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).