DEBUGGING OF BUSINESS FLOWS DEPLOYED IN PRODUCTION SERVERS

• US 20110047415A1
• Filed: 12/29/2009
• Published: 02/24/2011
• Est. Priority Date: 08/19/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Nanjundaswamy, Vijay Kyathanahalli
• Granted Patent: US 8,122,292 B2
• Time in Patent Office: Days
• US Class Current: 714/37
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

Abstract

Facilitating debugging of business flows deployed on a production server. An aspect of the present invention processes some service requests (received from a client system) in a normal mode and some other service requests in a debug mode concurrently, all according to a business flow. According to another aspect, the debug mode supports a single step debug operation, in which each step corresponds to a single activity of the business flow. Accordingly, an administrator of the production server is enabled to better determine, the problems in the execution of business flows deployed on a production server at runtime.

Claims

1. A method of processing service requests according to a business flow deployed on a production server, said method being performed in said production server, said method comprising:

processing concurrently a first service request in a normal mode and a second service request in a debug mode according to said business flow in said production server.

2. The method of claim 1, wherein said debug mode supports a single step debug operation, wherein each step corresponds to a single activity of said business flow.

3. The method of claim 2, wherein said first service request is processed using a first instance of said business flow in said normal mode and said second service request is processed using a second instance of said business flow in said debug mode.

4. The method of claim 3, further comprising:

specifying, by a user, a breakpoint at a first activity in said business flow;

creating said second instance upon receiving said second service request;

maintaining a second data structure indicating a second set of breakpoints for said second instance, wherein said breakpoint is included in said second set of breakpoints;

examining, before performing an activity, said second data structure for presence of a corresponding breakpoint identifying said activity; and

entering said debug mode for said second service request at said activity if the corresponding breakpoint identifying said activity is present in said second data structure,

whereby said second instance enters said debug mode at said first activity.

5. The method of claim 4, wherein the data forming said first service request and said second service request are received from an external client system.

6. The method of claim 2, wherein said business flow comprises a plurality of activities, wherein said processing in said single step debug operation comprises:

pausing before execution of each activity in an execution path; and

waiting for a user input to continue execution of the paused activity in said execution path.

7. The method of claim 6, wherein each of said activities is either a basic activity or a compound activity, wherein said compound activity comprises multiple basic activities, said method further comprising:

receiving a second user input indicating whether a step is to equal entire compound activity or each basic activity in the compound activity; and

if said second user input indicates that the step equals each basic activity, performing said pausing before execution of each basic activity in a compound activity when processing said second service request according to said business flow,

if said second user input indicates that the step equals entire compound activity, performing all the basic activities contained in the compound activity, and then only performing said pausing.

8. The method of claim 2, wherein said business flow is specified according to web service business process execution language (BPEL).

9. The method of claim 3, further comprising:

generating a plurality of activity blocks containing the program logic to perform a plurality of activities forming said business flow; and

executing said plurality of activity blocks concurrently as said first instance in said normal mode and as said second instance in said debug mode,

wherein said plurality of activity blocks contain no additional instructions for facilitating execution in said debug mode.

10. A machine readable medium storing one or more sequences of instructions for causing a production server to facilitate processing of service requests according to a business flow deployed on said production server, said business flow comprising a plurality of activities, said one of more sequences of instructions comprising:

a first set of instructions representing a plurality of activity blocks, each activity block contains program logic to perform one of said plurality of activities in said business flow; and

a second set of instructions representing an activity execution block to execute said plurality of activity blocks to process a service request,

each of said plurality of activity blocks to generate a token indicating a next activity which is to be performed, wherein each of said plurality of activity blocks is designed to execute the corresponding program logic to perform corresponding activity only upon availability of a corresponding token from said activity execution block,

said activity execution block to withhold availability of said token for said next activity until reception of a continue indication from a user if a breakpoint is specified for said next activity, and to make available said token for said next activity otherwise.

11. The machine readable medium of claim 10, wherein said production server further comprises a breakpoint table to store a set of breakpoints, each breakpoint specifying the identifier of a corresponding one of a set of activities at which the execution of said business flow is required to be paused, said set of activities being contained in said plurality of activities,

wherein said activity execution block withholds availability of said token for said next activity if the identifier of said next activity matches the identifier of one of said set of activities stored in said breakpoint table, and to make available said token for said next activity if there is no match.

12. The machine readable medium of claim 11, wherein a corresponding breakpoint table is maintained for each instance of said business flow processing a corresponding service request,

wherein the breakpoint table corresponding to a first instance is empty, whereby said first instance processes a first service request without entering a debug mode,

wherein the breakpoint table corresponding to a second instance stores the identifier of at least one activity, whereby said second instance enters said debug mode while processing a second service request.

13. The machine readable medium of claim 12, wherein said first service request is processed concurrent with said second service request when said second instance is in said debug mode.

14. The machine readable medium of claim 11, wherein said one or more sequences of instructions further comprising a third set of instructions representing a debug control block, said debug control block to receive identifier of each activity at which the execution of said business flow is required to be paused, and to store said identifier as one of the identifiers in said breakpoint table.

15. The machine readable medium of claim 14, wherein said debug control block is further designed to receive said continue indication from said user and to remove the identifier of said next activity in said breakpoint table to cause said activity execution block to make available said token for said next activity, thereby causing continuation of execution of said business flow from said next activity.

16. The machine readable medium of claim 15, said debug control block is further designed to check whether said continue indication is a single-step indication, if said continue indication is said single-step indication, said debug control block to add the identifier of said next activity to a single step table,

on completion of execution of said next activity by a next activity block, said activity execution block to determine whether the identifier for said next activity is in said single step table and a second token for a subsequent activity is generated by said next activity block, wherein subsequent activity is to be executed following said next activity,

if said identifier for said next activity is determined to be in said single step table and said second token for said subsequent activity is generated by said next activity block, said activity execution block further designed to insert the identifier of said subsequent activity in said breakpoint table such that said activity execution block withholds availability of said second token for said subsequent activity until reception of a corresponding continue indication,

whereby said business flow is executed in a single step debug operation.

17. The machine readable medium of claim 10, wherein said activity execution block is a part of a run-time environment shared for execution of multiple business flows deployed in said production server,

wherein processing of said service request enters a debug mode upon encountering said breakpoint in an execution path,

wherein a sequence of procedures executed within each of said activity blocks is the same, whether processing of said service request enters said debug mode or not.

18. A production server facilitating debugging of a business flow executing in said production server, said business flow containing a plurality of activities, said production server comprising:

a processor;

a random access memory (RAM); and

a machine readable medium storing a set of instructions, which when retrieved into said RAM and executed by said processor causes said production server to perform the actions of;

processing concurrently a first service request in a normal mode and a second service request in a debug mode according to said business flow in said production server.

19. The production server of claim 18, wherein said business flow comprises a plurality of activities, wherein said debug mode supports a single step debug operation, wherein each step corresponds to a single activity of said business flow, wherein said processing in said single step debug operation comprises:

pausing before execution of each activity in an execution path; and

waiting for a user input to continue execution of the paused activity in said execution path.

20. The production server of claim 19, wherein said pausing is designed to pause before execution of an activity if the corresponding identifier is present in a breakpoint table,

wherein each activity upon execution is designed to indicate a next activity to be executed in said execution path, said processing in said single step debug operation further comprising:

inserting into said breakpoint table, the identifier of said next activity after indication of said next activity,

whereby execution is paused before said next activity, thereby executing said business flow in said single step debug operation.