Policy based message aggregation framework

• US 20070234369A1
• Filed: 04/03/2006
• Published: 10/04/2007
• Est. Priority Date: 04/03/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lo, Wei-Lun, Yakushev, Ruslan, Paramisivam, Kartik
• Granted Patent: US 7,890,955 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Messages generated by an originating application are aggregated into batches based on a configuration policy. The configuration policy contains business logic used to aggregate messages into a batch. Once a batch is complete, it is formatted into a single stream output and sent to a destination application designed to receive the messages. Messages may also be aggregated into batches that are controlled by the originating application. The messages include an indicator set by the originating application to signal when a batch is complete. Once the batch is complete, it is formatted into a single stream output and sent to a destination application designed to receive the messages.

Claims

1. A computerized method of aggregating messages comprising:

receiving a plurality of messages from at least one application;

executing a batch configuration policy on the received messages;

aggregating the received messages in a batch as a function of the batch configuration policy;

assembling the batch into a single stream message output.

2. The method of claim 1, wherein the single stream message output is addressed to an endpoint.

3. The method of claim 1, wherein the executing further comprises maintaining an instance state associated with the batch.

4. The method of claim 3, further comprising storing the instance state in a data store.

5. The method of claim 4, wherein the receiving, executing, and maintaining are associated with a first computer and the data store is associated with a second computer.

6. The method of claim 1, wherein the receiving further comprises storing the received messages in a data store.

7. The method of claim 1, wherein the batch configuration policy contains business logic to batch the messages for the application.

8. The method of claim 7, wherein the business logic includes at least one of the following policy parameters:

a sort order of the messages in the batch, a number of messages in the batch, a cumulative number of bytes in the batch, one or more types of messages in the batch, and a time period to accumulate messages.

9. The method of claim 1, wherein the aggregating further comprises sorting the messages as function of the configuration policy.

10. The method of claim 1, wherein the messages comply with an EDI (Electronic Data Interchange) standard.

11. The method of claim 1, wherein one or more computer-readable media have computer-executable instructions for performing the method of claim 1.

12. A computerized method of aggregating messages comprising:

receiving a plurality of messages from at least one application, said messages including a batch identifier and a batch end indicator;

aggregating the received messages in a batch as a function of the batch identifier;

completing the aggregating as a function of the batch end indicator;

assembling the batch into a single stream message output.

13. The method of claim 12, further comprising hashing the batch identifier to determine the instance of a batcher for aggregating the messages.

14. The method of claim 12, wherein the batch end indicator signals when the batch is complete.

15. The method of claim 12, wherein the single stream message output is addressed to an endpoint.

16. The method of claim 12, further comprising maintaining an instance state associated with the batch.

17. The method of claim 16, further comprising storing the instance state in a data store.

18. The method of claim 12, wherein one or more computer-readable media have computer-executable instructions for performing the method of claim 12.

19. A system for aggregating messages for an application, said messages being addressed to a send port, said system comprising one or more computer-executable components comprising:

a message engine component for receiving messages from the application;

a batch configuration policy, said batch configuration policy containing business logic to batch the messages for the application;

a batcher component for aggregating messages into a batch as a function of the batch configuration policy, said batcher component being associated with the send port, said batcher component receiving messages addressed to the send port from the message engine; and

wherein the message engine component creates a new instance of the batcher associated with the send port if the batcher component associated with the send port does not exist.

20. The system of claim 19, wherein the message engine component is associated with a first computer and maintains an instance state of the batch stored in a data store associated with a second computer, said instance state including a message identifier and send port identifier;

and

wherein the message engine component is associated with a first computer and stores the message in said data store associated with said second computer.