DECOMPOSING APPLICATION TOPOLOGY DATA INTO TRANSACTION TRACKING DATA
First Claim
Patent Images
1. A method for generating transaction tracking data that is used to simulate a customer environment or test case scenario, the method comprising:
- receiving, by one or more processors, user input data, wherein the user input data includes, at least, an application topology constructed using a graphical user interface, wherein the application topology includes nodes that are connected by unidirectional edges and bidirectional edges, and wherein the nodes represent operating systems, middleware, and applications, wherein each of the nodes are assigned properties that describe node attributes of a respective node, wherein the node attributes include context data that describes the respective node, status information to simulate a live customer environment, volume data, and timing data, wherein the timing data is determined from a position of the nodes on the graphical user interface;
validating, by one or more processors, the user input data for, at least, supported environments of components of the application topology, wherein additional nodes and edges are created during the validation process; and
generating, by one or more processors, transaction tracking data based on, at least, the user input data.
1 Assignment
0 Petitions
Accused Products
Abstract
In an approach for generating transaction tracking data that is used to simulate a customer environment or test case scenario, a processor receives user input data, wherein the user input data includes, at least, an application topology constructed using a graphical user interface. A processor validates the user input data for, at least, supported environments of components of the application topology. A processor generates transaction tracking data based on, at least, the user input data.
4 Citations
20 Claims
-
1. A method for generating transaction tracking data that is used to simulate a customer environment or test case scenario, the method comprising:
-
receiving, by one or more processors, user input data, wherein the user input data includes, at least, an application topology constructed using a graphical user interface, wherein the application topology includes nodes that are connected by unidirectional edges and bidirectional edges, and wherein the nodes represent operating systems, middleware, and applications, wherein each of the nodes are assigned properties that describe node attributes of a respective node, wherein the node attributes include context data that describes the respective node, status information to simulate a live customer environment, volume data, and timing data, wherein the timing data is determined from a position of the nodes on the graphical user interface; validating, by one or more processors, the user input data for, at least, supported environments of components of the application topology, wherein additional nodes and edges are created during the validation process; and generating, by one or more processors, transaction tracking data based on, at least, the user input data. - View Dependent Claims (2, 5, 6, 7)
-
-
3. (canceled)
-
4. (canceled)
-
8. A computer program product for generating transaction tracking data that is used to simulate a customer environment or test case scenario, the computer program product comprising:
-
one or more computer readable storage media and program instructions stored on the one or more computer readable storage media, the program instructions comprising; program instructions to receive user input data, wherein the user input data includes, at least, an application topology constructed using a graphical user interface, wherein the application topology includes nodes that are connected by unidirectional edges and bidirectional edges, and wherein the nodes represent operating systems, middleware, and applications, wherein each of the nodes are assigned properties that describe node attributes of a respective node, wherein the node attributes include context data that describes the respective node, status information to simulate a live customer environment, volume data, and timing data, wherein the timing data is determined from a position of the nodes on the graphical user interface; program instructions to validate the user input data for, at least, supported environments of components of the application topology, wherein additional nodes and edges are created during the validation process; and program instructions to generate transaction tracking data based on, at least, the user input data. - View Dependent Claims (9, 12, 13, 14)
-
-
10. (canceled)
-
11. (canceled)
-
15. A computer system for generating transaction tracking data that is used to simulate a customer environment or test case scenario, the computer system comprising:
-
one or more computer processors, one or more computer readable storage media, and program instructions stored on the computer readable storage media for execution by at least one of the one or more processors, the program instructions comprising; program instructions to receive user input data, wherein the user input data includes, at least, an application topology constructed using a graphical user interface, wherein the application topology includes nodes that are connected by unidirectional edges and bidirectional edges, and wherein the nodes represent operating systems, middleware, and applications, wherein each of the nodes are assigned properties that describe node attributes of a respective node, wherein the node attributes include context data that describes the respective node, status information to simulate a live customer environment, volume data, and timing data, wherein the timing data is determined from a position of the nodes on the graphical user interface; program instructions to validate the user input data for, at least, supported environments of components of the application topology, wherein additional nodes and edges are created during the validation process; and program instructions to generate transaction tracking data based on, at least, the user input data. - View Dependent Claims (16, 19, 20)
-
-
17. (canceled)
-
18. (canceled)
Specification