Hierarchical message handler

• US 10,812,623 B2
• Filed: 09/21/2016
• Issued: 10/20/2020
• Est. Priority Date: 09/21/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Richter, Matthias, Hase, Eva Angelina, Bellemann de Leon, Gabriela, Schoenecker, Mathias, Dominguez Anzuinelli, Gisella, Michaelis, Nicolai, Rosier, Michael, Carbol, Gunilla, Schuhmacher, Frank, Pfeil, Lorenz
• Primary Examiner(s): Joshi, Suraj M
• Assistant Examiner(s): Means, Jaren
• Application Number:
  US15/271,616
• Publication Number:
  US 20180084046A1
• Time in Patent Office: 1,490 Days
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system includes invoking, from a first application, a first method of a first interface to instantiate a first instance of a message handler class, the first instance of the message handler class associated with a first message buffer, providing, from the first application, a second interface and a handler to the first instance of the message handler class to a second application, and invoking, from the second application, a second method of the second interface to add a first message to the first message buffer associated with the first instance of the message handler class.

Claims

1. A system comprising:

a first server comprising a first memory and a first one or more processors, the first memory storing a first application comprising program code executable to cause the first server to;

invoke a first method of a first interface to instantiate a first instance of a message handler class, the first instance of the message handler class storing a first message buffer, wherein the first message buffer stores a base message, and to instantiate a second instance of the message handler class; and

provide a second interface to a second application comprising program code;

a second server comprising a second memory and a second one or more processors, the second memory storing the second application comprising program code executable, with executable program code of the first application, to cause the second server to;

invoke a second method of the second interface to add a first message to a second message buffer stored within the second instance of the message handler class, and subsequently transfer the first message from the second message buffer to the first message buffer stored within the first instance of the message handler class, wherein the base message and first message are interrelated messages having related message content;

a data store;

a logging server comprising a third memory and a third one or more processors, the third memory storing a first logging tool comprising program code executable to cause the logging server to expose a first logging interface and to store log data in the data store; and

a third server comprising a fourth memory and a fourth one or more processors, the fourth memory storing a service factory comprising program code executable to cause the third server to instantiate a first mediation class, the first mediation class to expose a generic logging interface to the message handler class and to call the first logging interface based on calls to the generic logging interface.

2. A system according to claim 1, the first application comprising program code being further executable to cause the first server to:

invoke the first method of the first interface to instantiate the second instance of the message handler class, the second instance of the message handler class associated with a second message buffer;

invoke a third method of the first interface to add a third message to the second message buffer associated with the second instance of the message handler class; and

invoke a fourth method of the first interface to acquire the second message from the first message buffer and to store the acquired second message in the second message buffer.

3. A system according to claim 1, wherein the subsequent transfer of the first message from the second message buffer to the first message buffer avoids the second application directly affecting the contents of the first message buffer.

4. A system comprising:

a first one or more processors;

a first application comprising program code executable to cause the system to;

invoke a first method of a first interface to instantiate a first instance of a message handler class, the first instance of the message handler class storing a first message buffer, wherein the first message buffer stores a base message, and to instantiate a second instance of the message handler class; and

provide a second interface to a second application comprising program code; and

the second application comprising program code executable to cause the system to;

invoke a second method of the second interface to add a first message to a second message buffer stored within the second instance of the message handler class, and subsequently transfer the first message from the second message buffer to the first message buffer stored within with the first instance of the message handler class, wherein the base message and first message are interrelated messages having related message content.

5. A system according to claim 4, the first application comprising program code being further executable to cause the system to:

invoke a third method of the first interface to add the base message to the first message buffer associated with the first instance of the message handler class.

6. A system according to claim 5, wherein the first message is a detail message, the first message is stored in association with an identifier of the base message, and the base message is associated with a first level of a hierarchy and the first message is associated with a second level of the hierarchy.

7. A system according to claim 4, the first application comprising program code being further executable to cause the system to:

invoke the first method of the first interface to instantiate the second instance of the message handler class, the second instance of the message handler class associated with a second message buffer; and

invoke a third method of the first interface to add a third message to the second message buffer associated with the second instance of the message handler class.

8. A system according to claim 7, the first application comprising program code being further executable to cause the system to:

invoke a fourth method of the first interface to acquire the first message from the second message buffer and to store the acquired first message in the first message buffer.

9. A system according to claim 8, wherein the first message is a detail message, the first message is stored in association with an identifier of the base message, and the base message is associated with a first level of a hierarchy and the first message is associated with a second level of the hierarchy.

10. A system according to claim 4, wherein the second interface comprises a subset of the methods of the first interface.

11. A system according to claim 4, further comprising:

a first logging tool comprising program code executable to cause the system to expose a first logging interface and to store log data in a data store; and

a service factory comprising program code executable to cause the system to instantiate a given first mediation class based on a service factory knowledge of an environment, the first mediation class to expose a generic logging interface to the message handler class and to call the first logging interface based on calls to the generic logging interface.

12. A system according to claim 11, further comprising:

a second logging tool comprising program code executable to cause the system to expose a second logging interface and to store log data in the data store,

wherein the service factory comprising program code is further executable to cause the system to instantiate a second mediation class, the second mediation class to expose the generic logging interface to the message handler class and to call the second logging interface based on calls to the generic logging interface.

13. A computer-implemented method comprising:

invoking, from a first application, a first method of a first interface to instantiate a first instance of a message handler class, the first instance of the message handler class storing a first message buffer, wherein the first message buffer stores a base message, and to instantiate a second instance of the message handler class;

providing, from the first application, a second interface to a second application; and

invoking, from the second application, a second method of the second interface to add a first message to a second message buffer stored within the second instance of the message handler class, and subsequently transfer the first message from the second message buffer to the first message buffer stored within the first instance of the message handler class, wherein the base message and first message are interrelated messages having related message content.

14. A method according to claim 13, further comprising:

invoking a third method of the first interface to add the base message to the first message buffer associated with the first instance of the message handler class.

15. A method according to claim 14, wherein the first message is a detail message, the first message is stored in association with an identifier of the base message, and the base message is associated with a first level of a hierarchy and the first message is associated with a second level of the hierarchy.

16. A method according to claim 13, further comprising:

invoking, from the first application, the first method of the first interface to instantiate the second instance of the message handler class, the second instance of the message handler class associated with a second message buffer; and

invoking, from the first application, a third method of the first interface to add a third message to the second message buffer associated with the second instance of the message handler class.

17. A method according to claim 16, further comprising:

invoking, from the first application, a fourth method of the first interface to acquire the first message from the second message buffer and to store the acquired first message in the first message buffer.

18. A method according to claim 17, wherein the first message is detail message, the first message is stored in association with an identifier of the base message, and the base message is associated with a first level of a hierarchy and the first message is associated with a second level of the hierarchy.

19. A method according to claim 13, further comprising:

exposing, at a first logging tool, a first logging interface to store log data in a data store; and

instantiating a first mediation class at a service factory, the first mediation class to expose a generic logging interface to the message handler class and to call the first logging interface based on calls to the generic logging interface.

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

exposing, at a second logging tool, a second logging interface to store log data in the data store,

wherein the service factory is executable to instantiate a second mediation class, the second mediation class to expose the generic logging interface to the message handler class and to call the second logging interface based on calls to the generic logging interface.