Service-Oriented Architecture Debugger for Runtime Event Visualization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a lack of convenient integration between run-time events generated by business processes and previously designed Service-oriented architecture (SOA) software models, making it difficult for developers to visualize and modify business processes effectively during debugging or reengineering.
Innovation Solution
A method and system for capturing and displaying run-time events in a graphical and textual format, allowing users to visualize the events relative to the SOA model, with features such as event collection, analysis, and modification, and real-time visualization, using metadata to link events with the corresponding process flow and translating events into a universal programming language like XML.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If developers focus on run-time events directly without using SOA models, then they can observe actual execution behavior, but they lose the ability to visualize events in the context of the designed process model
Solution Approach 1:
The patent introduces an intermediary system that maps run-time events to their corresponding SOA model elements. This intermediary layer connects the raw event data with the visual process model, allowing developers to see events both as actual execution data and in the context of the designed model, thus resolving the contradiction between accurate observation and ease of visualization
Solution Approach 2:
The system creates a visual copy of the run-time events overlaid on the SOA process model. By copying event information and presenting it in the context of the original process design, developers can maintain accuracy of event data while gaining the visualization benefits of the model context
2Productivity
If developers abandon the previously generated SOA model in favor of focusing on run-time events, then they can work with actual execution data, but they cannot conveniently integrate this data with the designed process model for debugging
Solution Approach 1:
The patent employs an intermediary mapping mechanism that automatically correlates run-time events with SOA model elements using metadata and identifiers. This intermediary layer handles the complex integration work behind the scenes, allowing developers to work with actual execution data while maintaining automatic linkage to the process model without manual integration effort
3Loss of information
If the system displays detailed run-time events with full SOA model context, then developers can understand event positioning, but the interface becomes complex and requires programming language knowledge
Solution Approach 1:
The patent applies local quality by providing different levels of detail in different parts of the interface. The SOA model visualization provides high-level contextual information that is easily understandable, while detailed event information is available on-demand or in simplified formats, allowing users to access complete context without being overwhelmed by complexity
Data Source
AI summary
Methods, systems, and computer program products for performing the method are provided. The method includes collecting specified events generated during a run-time operation of a designed computing process flow having a model that defines, at a service-oriented architecture level, which of several predefined computing services are used in the computing process flow and relationships among the predefined computing services that are used in the process flow. The method also includes generating, on a display device, a visual display that shows visual representations of all or a portion of the service-oriented architecture-level model for the computing process flow, and of the collected specified events and where, relative to the model, the collected specified events were generated.