# US 2019/0379737 A1 · System and method for data payload collection monitoring and analysis in a transaction processing environment

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

- Number: US 2019/0379737 A1
- Document ID: US20190379737A1
- Status: Published application
- Kind: A1
- Application number: 16/527,606
- Filed: 2019-07-31
- Published: 2019-12-12
- Earliest claimed: 2015-10-22
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Hui Chen; Todd Little; Xiangdong Li; Jim Yongshun Jin
- Web page: https://patentgrep.com/patent/US20190379737A1

## CPC

- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 41/20: {Network management software packages}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A self-describing data format capable of carrying payload information, such as Tuxedo payload information, as well as filter information. The data format can allow for expression of some or all of Tuxedo Typed Buffers, including STRING, CARRAY, MBSTRING, VIEW, VIEW32, FML, and FML32. The data format is also capable of supporting nesting and error-checking. The proposal of user payload collection can allow customers to siphon off user/payload data to be used in applications, such as Business Intelligence applications, without the need for additional information to be passed with the payload data.

## Claims

### Claim 1

A method for supporting data payload collection in a transactional middleware machine environment, comprising:
providing, a monitoring framework, including a data collection engine, the monitoring framework monitoring a transaction within the middleware machine environment;
capturing, at the monitoring framework, transactional procedure data of the monitored transaction;
writing the transactional procedure data in a self-describing format to a buffer, wherein the self-describing format carries filter information and user payload data; and
filtering, based on the filter information, the user payload data from the self-describing data format.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
passing the filtered user payload data to an analysis application.

### Claim 3 (depends on 1)

The method of claim 1,
wherein the self-describing data format expresses a plurality of typed buffers.

### Claim 4 (depends on 3)

The method of claim 3,
wherein the self-describing data format provides an error checking mechanism for the user payload data carried by the self-describing data format.

### Claim 5 (depends on 1)

The method of claim 1,
wherein the self-describing format comprises a header.

### Claim 6 (depends on 5)

The method of claim 5, wherein the header comprises a block holding a fixed value used to determine if the user payload data is corrupt, a block identifying a data type and a block identifying a sub-data type.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
providing, at the monitoring framework, a user interface; and
receiving the filter information from an instruction received at the user interface.

### Claim 8

A system for supporting data payload collection in a transaction processing environment, the system comprising:
one or more microprocessors; and
a processor, running on the one or more microprocessors, wherein the processor operates to perform steps comprising:
providing, a monitoring framework, including a data collection engine, the monitoring framework monitoring a transaction within the middleware machine environment;
capturing, at the monitoring framework, transactional procedure data of the monitored transaction;
writing the transactional procedure data in a self-describing format to a buffer, wherein the self-describing format carries filter information and user payload data; and
filtering, based on the filter information, the user payload data from the self-describing data format.

### Claim 9 (depends on 8)

The system of claim 8, the steps further comprising:
passing the filtered user payload data to an analysis application.

### Claim 10 (depends on 8)

The system of claim 8,
wherein the self-describing data format expresses a plurality of typed buffers.

### Claim 11 (depends on 10)

The system of claim 10,
wherein the self-describing data format provides an error checking mechanism for the user payload data carried by the self-describing data format.

### Claim 12 (depends on 8)

The system of claim 8,
wherein the self-describing format comprises a header.

### Claim 13 (depends on 12)

The system of claim 12, wherein the header comprises a block holding a fixed value used to determine if the user payload data is corrupt, a block identifying a data type and a block identifying a sub-data type.

### Claim 14 (depends on 8)

The system of claim 8, further comprising:
providing, at the monitoring framework, a user interface; and
receiving the filter information from an instruction received at the user interface.

### Claim 15

A non-transitory machine readable storage medium having instructions stored thereon for supporting data payload collection in a transaction processing environment that when executed cause a system to perform steps comprising:
providing, a monitoring framework, including a data collection engine, the monitoring framework monitoring a transaction within the middleware machine environment;
capturing, at the monitoring framework, transactional procedure data of the monitored transaction;
writing the transactional procedure data in a self-describing format to a buffer, wherein the self-describing format carries filter information and user payload data; and
filtering, based on the filter information, the user payload data from the self-describing data format.

### Claim 16 (depends on 15)

The non-transitory machine readable storage medium of claim 15, the steps further comprising:
passing the filtered user payload data to an analysis application.

### Claim 17 (depends on 15)

The non-transitory machine readable storage medium of claim 15,
wherein the self-describing data format expresses a plurality of typed buffers.

### Claim 18 (depends on 17)

The non-transitory machine readable storage medium of claim 17,
wherein the self-describing data format provides an error checking mechanism for the user payload data carried by the self-describing data format.

### Claim 19 (depends on 15)

The non-transitory machine readable storage medium of claim 15,
wherein the self-describing format comprises a header.

### Claim 20 (depends on 19)

The non-transitory machine readable storage medium of claim 19, wherein the header comprises a block holding a fixed value used to determine if the user payload data is corrupt, a block identifying a data type and a block identifying a sub-data type.