Apparatus and method for observing runtime behavior of an application program

• US 20060129995A1
• Filed: 11/30/2004
• Published: 06/15/2006
• Est. Priority Date: 11/30/2004
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: DeBoe, Benjamin L.G.J.P., Rits, Maarten E.
• Application Number:
  US10/999,315
• Publication Number:
  US 20060129995A1
• Time in Patent Office: Days
• US Class Current: 717/127
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466

Abstract

A method and apparatus for observing runtime behavior of an application program. In one embodiment, the runtime behavior of the input program is observed according to at least one program target. Following execution of the input program, a report is generated to identify access to underlying layers of the input program directed to the at least one program target. In one embodiment, aspect oriented programming enables observation of the behavior of a running program. This enables the checking of each method invocation in the input program against a program target. This runtime information is extracted and provided as a report, which may be used to redesign an existing application for improving security or manageability. Other embodiments are described and claims.

Claims

1. A method, comprising:

observing, during execution of an input program, the behavior of the input program according to at least one program target; and

generating a report to identify access to underlying layers of the input program directed to the at least one program target.

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

detecting a method call directed to the program target within a calling method;

determining a stack trace for the detected method call; and

registering the detected method call and stack trace.

3. The method of claim 2, wherein determining the stack trace further comprises extracting a path from a method within an upper layer of the input program to the calling method to invoke the program target.

4. The method of claim 1, wherein the program target is one of a service, a method, a class and a resource.

5. The method of claim 1, wherein prior to observing, the method further comprises accessing a configuration file to determining the at least one program target and a report format.

6. The method of claim 1, wherein observing the behavior further comprises:

checking each method invocation issued by the input program against the at least one program target; and

identifying each issued method invocation directed to the program target.

7. The method of claim 6, wherein identifying each issued method invocation further comprises:

outputting, for each identified method invocation, a signature of a calling method that issued the identified method invocation, a signature of a called method by the method invocation and arguments passed to the called method.

8. The method of claim 1, wherein prior to observing the behavior, the method further comprises:

creating at least one aspect within the input program to identify each downcall issued during execution of the input program and direct to the program target; and

adding advice to the at least one aspect within the input program to export a path from a method within an upper layer of the input program to the calling method that invoked the program target.

9. The method of claim 8, wherein creating at least one aspect further comprises inserting a point cut within at least one method of the input program to check the method against the program target.

10. The method of claim 8, wherein creating at least one aspect further comprises inserting a point cut within each method of the input program to check each call issued by each method against the program target.

11. A method, comprising:

executing an input program;

identifying each downcall issued by the input program to at least one program target within an underlying layer of the input program; and

outputting, for each identified downcall, a signature of a calling module that issued the identified downcall, a signature of a called module by the identified module invocation and arguments passed to the called module.

12. The method of claim 11, wherein prior to executing the input program, the method further comprises:

creating at least one aspect within the input program to identify each downcall issued during execution of the input program and direct to the program target; and

adding advice to the at least one aspect within the input program to export a path from a method within an upper layer of the input program to the calling method that invoked the program target.

13. The method of claim 12, wherein creating at least one aspect further comprises inserting a point cut within at least one method of the input program to check the method against the program target.

14. The method of claim 12, wherein creating at least one aspect further comprises inserting a point cut within each method of the input program to check each call issued by each method against the program target.

15. The method of claim 11, wherein outputting further comprises generating a report to identify access to underlying layers of the input program directed to the at least one program target.

16. The method of claim 11, wherein a downcall comprises a call to a called method within a body of a calling method.

17. A machine accessible medium including instructions that when executed cause the machine to:

execute an input program;

identify each downcall issued by the input program to at least one program target within an underlying layer of the input program; and

output, for each identified downcall, a signature of a calling module that issued the identified downcall, a signature of a called module by the identified module invocation and arguments passed to the called module.

18. The machine accessible medium of claim 17, wherein prior to executing the input program, the machines is further to:

create at least one aspect within the input program to identify each downcall issued during execution of the input program and direct to the program target; and

add advice to the at least one aspect within the input program to export a path from a method within an upper layer of the input program to the calling method that invoked the program target.

19. The machine accessible medium of claim 18, wherein to create at least one aspect, the machine is further to:

insert a point cut within at least one method of the input program to check the method against the program target.

20. The machine accessible medium of claim 17, wherein to create the at least one aspect, the machine is further to:

insert a point cut within each method of the input program to check each call issued by each method against the program target.

21. The machine accessible medium of claim 17, wherein to output, the machine is further to:

generate a report to identify access to underlying layers of the input program directed to the at least one program target.

22. A machine accessible medium including instructions that when executed cause the machine to:

execute an input program;

observe the behavior of the input program according to at least one program target; and

generate a report to identify access to underlying layers of the input program directed to the at least one program target.

23. The machine accessible medium of claim 22, wherein to observe the behavior, the machine is further to:

detect a method call directed to the program target within a calling method;

determine a stack trace for the detected method call; and

register the detected method call and stack trace.

24. The machine accessible medium of claim 23, wherein to determine the stack trace, the machine is further to:

extract a path from a method within an upper layer of the input program to the calling method to invoke the program target.

25. The machine accessible medium of claim 22, wherein to observe the behavior, the machine is further to:

check each method invocation issued by the input program against the at least one program target; and

identify each issued method invocation directed to the program target.

26. The machine accessible medium of claim 25, wherein to identify each issued method invocation, the machine is further to:

output, for each identified method invocation, a signature of a calling method that issued the identified method invocation, a signature of a called method by the method invocation and arguments passed to the called method.

27. A system, comprising:

an execution module to execute an input program;

a downcall module to detect each downcall issued by the input program and directed to at one user supplied program target; and

a report module to output, for each identified downcall, a signature of a calling module that issued the identified downcall, a signature of a called module by the identified module invocation and arguments passed to the called module.

28. The system of claim 27, further comprising:

an execution module to execute the input program to invoke each method within the input program

29. The system of claim 27, further comprising:

an aspect module to create at least one aspect within the input program to identify each downcall issued during execution of the input program and direct to the program target.

30. The system of claim 29, wherein the aspect module is further to adding advice to the at least one aspect within the input program to export a path from a method within an upper layer of the input program to the calling method that invoked the program target.