System and method for storing large messages

• US 7,257,645 B2
• Filed: 04/01/2003
• Issued: 08/14/2007
• Est. Priority Date: 05/01/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Hoebanx, Pascal, Dalal, Sanjay, Wiser, David
• Primary Examiner(s): JUNG, DAVID YIUK
• Application Number:
  US10/404,865
• Publication Number:
  US 20040006663A1
• Time in Patent Office: 1,596 Days
• Field of Search: 715/503, 713/150, 707/10, 707/101, 709/238
• US Class Current: 709/238
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A large message can be stored by separating the message into an envelope portion containing information such as headers, protocols, and addresses, and a payload portion containing items such as file attachments. The envelope portion can be stored in local storage, while the payload can be stored to a persistent store. The message can be processed incrementally, such that the entire message is never in system memory. Once the envelope portion is processed, the payload portion can be read in increments without being processed, and those increments written directly to the persistent store. Alternatively, the payload can be streamed to the persistent store. A pointer in the envelope can then be used to locate and retrieve attachments from persistent storage.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for storing a message, comprising:

a memory component adapted to temporarily store information for the message;

a persistent store adapted to persistently store information for the message; and

an integration component that includes a transport layer to receive the incoming message, wherein the integration component further

creates a separate envelope and payload for the message,

stores the payload in the persistent store,

creates within the envelope a header information and pointers to portions of the payload,

stores the envelope in the memory component, and

allows other applications to retrieve selected portions of the message from the persistent store using the pointers in the envelope.

2. The system of claim 1 wherein the integration component creates within the envelope the header information and pointers to the portions of the payload, including a separate pointer for any separate attachments in the message, and subsequently allows the other applications to retrieve the separate attachments in the message using the separate pointers for the separate attachments.

3. The system of claim 2 wherein the envelope is sent to the other applications for use by the other applications in retrieving portions of the message, while the payload remains stored in the persistent store.

4. A system according to claim 1, wherein:

the integration component is adapted to separate the message into an envelope portion containing information selected from the group consisting of headers, protocols, addresses, and message text.

5. A system according to claim 1, further comprising:

a Web server adapted to receive the message and direct the message to the integration component.

6. A system according to claim 1, wherein:

the persistent store is selected from group consisting of file-based persistent stores and data-based persistent stores.

7. A system according to claim 1, wherein:

the integration component is further adapted to process message in increments of the overall message size.

8. A system according to claim 6, wherein:

the integration component is further adapted to write the payload to the persistent store in increments.

9. A system according to claim 1, wherein:

the integration component is further adapted to process message in increments each having a size selected from the group consisting of 1 MB, 5 MB, or 10 MB.

10. A system according to claim 1, wherein:

the integration component is further adapted to process message in increments each having a size selected from the group consisting of 1%, 5%, 10%, and 25% of the overall file size.

11. A system according to claim 1, wherein:

the integration component is selected from the group consisting of integration applications, integration servers, integration transport layers, and integration plug-ins.

12. A system according to claim 1, wherein

the integration component is adapted to store the payload portion in the persistent store, wherein the payload is stored in multiple locations in the persistent store.

13. A system according to claim 1, wherein:

the integration component is adapted to store the payload portion in the persistent store and any other persistent store, wherein the payload portion can be stored to more than one persistent store.

14. A system according to claim 1, further comprising:

a protocol parser adapted to identify portions of the message to the integration component.

15. A system according to claim 14, wherein:

the protocol parser is further adapted to stop parsing the protocol parser when reaches payload portion of the message.

16. A system according to claim 1, further comprising:

an XML parser for reading header and body portions of the message.

17. A system according to claim 1, wherein:

the integration component is further adapted to store the payload portion to the persistent store in a stream without processing the payload portion.

18. A system according to claim 1, wherein:

the integration component is adapted to receive messages in XML.

19. A system according to claim 1, wherein:

the integration component is adapted to receive messages having a file size selected from the group consisting of at or above 1 MB, at or above 10 MB, at or above 50 MB, and at or above 100 MB.

20. A method for storing a message, comprising:

receiving the message at an integration component;

creating a separate envelope and payload for the message;

storing the payload in a persistent store;

creating within the envelope a header information and pointers to portions of the payload;

storing the envelope in a memory component; and

allowing other applications to access the envelope and to retrieve selected portions of the message from the persistent store using the pointers in the envelope.

21. A method according to claim 20, further comprising:

parsing the message with a protocol parser to identify portions of the message to the integration component.

22. A method according to claim 20, further comprising:

parsing the message with an XML parser to read header and body portions of the message.

23. A method according to claim 20, further comprising:

processing the message in increments.

24. A method according to claim 20, further comprising:

processing the message as a stream.

25. The method of claim 20 wherein the method further comprises creating within the envelope the header information and pointers to the portions of the payload, including a separate pointer for any separate attachments in the message, and subsequently allowing the other applications to retrieve the separate attachments in the message using the separate pointers or the separate attachments.

26. The method of claim 25 wherein the method further comprises sending the envelope to the other applications for use by the other applications in retrieving portions of the message, while the payload remains stored in the persistent store.

27. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:

receiving a message from a first application;

creating a separate envelope and payload for the message;

storing the payload in a persistent store;

creating within the envelope pointers to portions of the payload;

storing the envelope in a memory component; and

allowing other applications to access the envelope and to retrieve selected portions of the message from the persistent store using pointers in the envelope.

28. The computer readable medium of claim 27 further including instructions stored thereon which when executed cause the computer to perform the additional steps of creating within the envelope the portions of the payload, including a separate pointer for any separate attachments in the message, and subsequently allowing the other applications to retrieve the separate attachments in the message using the separate pointers for the separate attachments.

29. The computer readable medium of claim 28 further including instructions stored thereon which when executed cause the computer to perform the additional steps of sending the envelope to the other applications for use by the other applications in retrieving portions of the message, while the payload remains stored in the persistent store.