Business Workflow Correlation via Semantic Transaction Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional transaction tracking tools, such as the Application Response Measurement (ARM) API, fail to effectively correlate business processes with IT transactions in distributed computing environments, particularly for long-running processes and asynchronous activities, due to limitations in tracking across different execution threads and remote machines, and require cumbersome modifications to business processes.
Innovation Solution
The method involves identifying instrumentation points in business processes that invoke IT resources and associating them with transaction names having business semantics, using tools like the Web Services Invocation Framework (WSIF) client to select and pass correlators, enabling correlation data to be linked between business processes and IT resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional transaction tracking tools (ARM API) are used to track IT transactions, then transaction performance can be monitored, but business processes cannot be correlated with IT transactions in distributed environments
Solution Approach 1:
The patent introduces a correlator as an intermediary data structure that bridges business processes and IT transactions. The correlator passes contextual information between business process execution and IT resource invocation, enabling correlation across distributed systems without modifying the underlying ARM API or transaction tracking infrastructure.
Solution Approach 2:
The patent segments the transaction tracking system into distinct components: business process instrumentation points, correlator data structures, and IT resource invocation points. This segmentation allows independent instrumentation of business processes and IT resources while maintaining correlation through the correlator, solving the distributed environment tracking problem.
2Loss of information
If artificial business process artifacts are inserted to extend IT tracking to business processes, then transaction correlation may be achieved for simple workflows, but the method becomes cumbersome and cannot handle long-running distributed processes
Solution Approach 1:
The correlator is designed as a universal data structure that handles multiple transaction types (synchronous, asynchronous, long-running) and distributed communication patterns (SOAP, RMI, JMS) through a single unified mechanism, eliminating the need for different instrumentation approaches for different workflow scenarios.
Solution Approach 2:
The business process engine automatically manages correlator creation, propagation, and retrieval without requiring artificial artifacts or manual instrumentation. The correlator is seamlessly integrated into the natural execution flow of business processes, making the correlation capability self-service rather than requiring additional complex instrumentation.
3Loss of information
If correlator passing is implemented at the business process level, then transaction correlation can be maintained, but implementation-specific object instances are not accessible across different execution threads and remote machines
Solution Approach 1:
The correlator acts as a thread-safe intermediary data structure that serializes correlation information suitable for transmission across execution boundaries. It carries essential correlation data (business process ID, transaction ID, activity context) in a format that can be persisted and retrieved across different threads and remote machine invocations.
Solution Approach 2:
The correlator adapts its content and format based on the execution context, transforming correlation data appropriately for different communication protocols and execution environments while maintaining the essential correlation relationship. This allows the same correlator mechanism to work across synchronous and asynchronous boundaries.
Data Source
AI summary
Methods, systems, and products are disclosed for correlating business workflows with transaction tracking, the method including identifying an instrumentation point in a business process of a business workflow that invokes an IT resource that carries out at least a portion of the business process and associating, at the instrumentation point, the business process and the IT resource with a transaction name having business semantics such that correlation data gathered about the IT resource may be linked with the business process. Correlating business workflows with transaction tracking may also include gathering correlation data about the IT resource, selecting one of the plurality of service specific correlator passing methods, and passing a correlator in accordance with the selected service specific correlator passing methods.