Debugging of business flows deployed in production servers
First Claim
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:
- receiving a first service request and a second service request to be processed according to said business flow;
receive data representing a set of break points associated with said second service request, each break point corresponding to one of a plurality of activities defining said business flow;
processing concurrently said first service request in a normal mode and said second service request in a debug mode according to said business flow in said production server,wherein a set of activities are performed according to an execution flow while processing said second service request in said debug mode,wherein a control block in said production server monitors said execution flow and pauses said execution flow to transfer control to said control block at each of the activities corresponding to said set of break points, wherein execution is resumed after each pause only upon receiving a user input,wherein said execution flow of processing of said second service request is not paused and control is not transferred to said control block at the remaining ones of said set of activities that do not correspond to any of said set of breakpoints.
1 Assignment
0 Petitions
Accused Products
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.
63 Citations
31 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:
-
receiving a first service request and a second service request to be processed according to said business flow; receive data representing a set of break points associated with said second service request, each break point corresponding to one of a plurality of activities defining said business flow; processing concurrently said first service request in a normal mode and said second service request in a debug mode according to said business flow in said production server, wherein a set of activities are performed according to an execution flow while processing said second service request in said debug mode, wherein a control block in said production server monitors said execution flow and pauses said execution flow to transfer control to said control block at each of the activities corresponding to said set of break points, wherein execution is resumed after each pause only upon receiving a user input, wherein said execution flow of processing of said second service request is not paused and control is not transferred to said control block at the remaining ones of said set of activities that do not correspond to any of said set of breakpoints. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A non-transitory machine readable storage 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. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
-
-
18. A production server facilitating debugging of a business flow executing in said production server, said business flow defined using a plurality of activities, said production server comprising:
-
a processor; a random access memory (RAM); and a machine readable medium storing a plurality of instructions, which when retrieved into said RAM and executed by said processor causes said production server to process a second service request in a debug mode according to said business flow in said production server, said plurality of instructions comprising; a first set of instructions representing a logic for performing each of said plurality of activities; a second set of instructions to receive data representing said business flow and to generate a third set of instructions designed to invoke said first set of instructions to perform each of a set of activities according to an execution flow while processing said second service request in said debug mode, said set of activities being contained in said plurality of activities and representing said business flow; a fourth set of instructions representing a control block, said control block to receive data representing a set of break points, each break point corresponding to one of said set of activities in said execution flow, wherein said control block monitors said execution flow and pauses said execution flow to transfer control to said control block at each of the activities corresponding to said set of break points, wherein said execution flow of processing of said second service request is not paused and control is not transferred to said control block at the remaining ones of said set of activities that do not correspond to any of said set of breakpoints. - View Dependent Claims (19, 20, 21, 22)
-
-
23. A non-transitory machine readable storage medium storing instructions, which when executed by a production server causes the production server to process service requests according to a business flow deployed on a production server, wherein execution of said instructions by one or more processors contained in said production server causes said production server to perform the actions of:
-
receiving a first service request and a second service request to be processed according to said business flow; receive data representing a set of break points associated with said second service request, each break point corresponding to one of a plurality of activities defining said business flow; processing concurrently said first service request in a normal mode and said second service request in a debug mode according to said business flow in said production server, wherein a set of activities are performed according to an execution flow while processing said second service request in said debug mode, wherein a control block in said production server monitors said execution flow and pauses said execution flow to transfer control to said control block at each of the activities corresponding to said set of break points, wherein execution is resumed after each pause only upon receiving a user input, wherein said execution flow of processing of said second service request is not paused and control is not transferred to said control block at the remaining ones of said set of activities that do not correspond to any of said set of breakpoints. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31)
-
Specification