# US 2017/0286274 A1 · Transaction stitching definitions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286274 A1
- Document ID: US20170286274A1
- Status: Published application
- Kind: A1
- Application number: 15/087,102
- Filed: 2016-03-31
- Published: 2017-10-05
- Earliest claimed: 2016-03-31
- Assignees: CA, Inc.
- Applicants: CA, Inc.
- Inventors: Rich J. Lau; Rui Zhong Zhou
- Web page: https://patentgrep.com/patent/US20170286274A1

## CPC

- G06F 11/3668: Testing of software
- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Transaction data is accessed that describes a plurality of transactions and includes a plurality of frames, with each frame describing a respective portion of a corresponding one of the plurality of transactions. A user-defined stitching definition is accessed that is related to a particular one of the plurality of transactions. Correlations between respective transaction portions described in the plurality of transaction frames are determined with a particular correlation between first and second transaction portions determined based on the user-defined stitching definition. A transaction path of the particular transaction is determined based at least in part on the particular correlation determined between the first and second transaction portions. The particular transaction includes the first and second transaction portions and the first transaction portion is determined to immediately precede the second transaction portion in the transaction path of the particular transaction based on the determined particular correlation.

## Claims

### Claim 1

A method comprising:
accessing transaction data describing a plurality of transactions involving a plurality of software components, wherein the transaction data comprises a plurality of transaction data frames and each of the transaction data frames describes attributes of a respective portion of a corresponding one of the plurality of transactions;
accessing data comprising a user-defined stitching definition related to a particular one of the plurality of transactions;
determining correlations between respective transaction portions described in the plurality of transaction frames based on the described attributes, wherein a particular correlation between a first one of the transaction portions and a second one of the transaction portions is determined based on the user-defined stitching definition; and
determining a transaction path of the particular transaction based at least in part on the particular correlation determined between the first and second transaction portions, wherein the particular transaction comprises the first and second transaction portions and the first transaction portion is determined to immediately precede the second transaction portion in the transaction path of the particular transaction based on the determined particular correlation.

### Claim 2 (depends on 1)

The method of claim 1, wherein each transaction portion comprises one of a request sent from a respective requesting software component in one of the plurality of transactions, a request received at a respective responding software component in one of the plurality of transactions, a response to a corresponding request sent from a respective responding component in one of the plurality of transactions, and a response to a corresponding request received by a respective requesting component in one of the plurality of transactions.

### Claim 3 (depends on 1)

The method of claim 1, further comprising generating a test case based on the transaction path to test correct operation of a subset of the plurality of software components participating in a test instance of the particular transaction.

### Claim 4 (depends on 1)

The method of claim 1, further comprising determining that the first transaction portion and the second transaction portion comprise a common request sent within the particular transaction based on the particular correlation.

### Claim 5 (depends on 4)

The method of claim 4, wherein the particular transaction comprises a plurality of transaction fragments, each transaction fragment comprises a respective request and a corresponding response to the respective request, and the method further comprises generating a graphical representation of the particular transaction comprising a plurality of graphical blocks each representing a respective software component involved in the particular transaction and a plurality of graphical connector elements each representing a respective one of the transaction fragments of the particular transaction, wherein a particular one of the plurality of graphical connector elements represents a particular one of the plurality of transaction fragments, the particular transaction fragment comprises the common request, the particular graphical connector element interconnects a first one of the plurality of graphical blocks representing a first one of the plurality of software components detected as sending the common request to a second one of the plurality of graphical blocks representing a second one of the plurality of software components detected as receiving the common request from the first software component in the particular transaction.

### Claim 6 (depends on 1)

The method of claim 1, further comprising determining that the user-defined stitching definition is to be accessed to determine the particular correlation based on attributes described for the first transaction portion in a particular one of the plurality of transaction data frames.

### Claim 7 (depends on 6)

The method of claim 6, wherein determining that the user-defined stitching definition is to be accessed to determine the particular correlation is based on an identity of a particular software component involved in the first transaction portion.

### Claim 8 (depends on 6)

The method of claim 6, wherein the first transaction portion comprises a particular request by a particular one of the plurality of software components, and determining that the user-defined stitching definition is to be accessed to determine the particular correlation is based on a detecting that the particular request is a request of a particular type.

### Claim 9 (depends on 6)

The method of claim 6, wherein the first transaction portion comprises a particular request by a particular one of the plurality of software components, and determining that the user-defined stitching definition is to be accessed to determine the particular correlation is based on content of the particular request.

### Claim 10 (depends on 1)

The method of claim 1, wherein the user-defined stitching definition comprises a defined parent-child key pair defining a basis for determining a correlation between transaction portions described in two transaction data frames.

### Claim 11 (depends on 10)

The method of claim 10, wherein the parent-child key pair comprises a parent key value to be observed in content of a corresponding transaction portion at a software component sending the corresponding transaction portion, and the parent-child key pair further comprises a corresponding child key value to be observed in content of the corresponding transaction at a software component receiving the corresponding transaction portion.

### Claim 12 (depends on 1)

The method of claim 1, wherein a default set of stitching criteria is used to determine other correlations between transaction portions described in the plurality of transaction frames based on the described attributes.

### Claim 13 (depends on 12)

The method of claim 12, wherein correlations based on the default set of stitching criteria comprise correlations based at least in part on one of common timing attributes between transaction portions, common component addresses between transaction portions, and common payload sizes sent and received between software components.

### Claim 14 (depends on 12)

The method of claim 12, wherein correlations between other transaction portions of the particular transaction are determined based on the default set of stitching criteria.

### Claim 15 (depends on 12)

The method of claim 12, wherein determining a correlation using the default set of stitching criteria fails for the correlation between the first and second transaction portions of the particular transaction.

### Claim 16 (depends on 16)

The method of claim 16, wherein determining a correlation using the default set of stitching criteria fails for the correlation between the first and second transaction portions based on presence of an intermediate routing process between two components participating in the particular transaction.

### Claim 17 (depends on 12)

The method of claim 12, wherein determining the correlations between respective transaction portions described in the plurality of transaction frames comprises attempting to identify correlations based on any one of the default set of stitching criteria and the user-defined stitching definition.

### Claim 18

A computer program product comprising a computer readable storage medium comprising computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to receive, from a plurality of agents instrumented on a plurality of software components, transaction data describing a plurality of transaction portions of a plurality of transactions involving the plurality of software components as observed by the plurality of agents;
computer readable program code configured to identify a particular one of a plurality of user-defined stitching definitions;
computer readable program code configured to determine a particular correlation between a first one of the transaction portions and a second one of the transaction portions based on the user-defined stitching definition;
computer readable program code configured to determine another correlation between transaction portions of a particular transaction based on another criteria, wherein the particular transaction further comprises the first and second transaction portions; and
computer readable program code configured to determine a transaction path of the particular transaction based at least in part on the determined particular correlation and the other correlation.

### Claim 19

A system comprising:
a data processor;
a memory;
a transaction path engine, executable to:
access transaction data describing a plurality of transaction portions in a plurality of transactions involving a plurality of software components;
identify a user-defined stitching definition corresponding to a particular one of the plurality of transactions;
determine a particular correlation between a first one of the transaction portion and a second one of the transaction portions based on the user-defined stitching definition;
determine that a particular one of the plurality of transactions comprises the first and second transaction portions; and
determine a transaction path of the particular transaction based at least in part on the determined particular correlation.

### Claim 20 (depends on 19)

The system of claim 19, further comprising a plurality of agents instrumented on at least a portion of the plurality of software components, wherein at least a portion of the transaction data is based on monitoring of the plurality of transactions by the plurality of agents.
