Establishing transaction metadata

Patent metadata

Field	Value
Publication number	US-11500855-B2
Application number	US-201514955136-A
Country	US
Kind code	B2
Filing date	Dec 1, 2015
Priority date	Mar 20, 2015
Publication date	Nov 15, 2022
Grant date	Nov 15, 2022

Abstract

A computer-implemented method of establishing metadata associated with a transaction in a transaction processing system having application logic for executing the transaction, the computer-implemented method includes receiving, from a requestor, request data associated with the transaction, the request data comprising data and metadata. The method also includes peeking, during receiving the request data, of the request data looking for the metadata associated with the transaction and responsive to finding metadata associated with the transaction, directly instantiating an instance of application logic.

First claim

The invention claimed is:

1. A computer-implemented method of establishing metadata associated with a transaction in a transaction processing system having application logic for executing the transaction, the computer-implemented method comprising:
receiving, by a notification layer of an online transaction processing system (OTPS) from a requestor, request data associated with the transaction, the transaction being an online transaction, the request data comprising data and metadata, the notification layer that initially received the request data being configured to start an application logic and to start an establish layer according to the metadata, wherein the request data is received in a plurality of chunks by the notification layer, the plurality of chunks being blocks of the request data;
based on the notification layer determining that a first chunk of the plurality of chunks has been received and the notification layer determining that a first line of a hypertext transfer protocol (HTTP) request has been received in the first chunk, reading, by the notification layer of the OTPS, the request data looking for the metadata associated with the transaction during receiving the request data to determine whether identification of the application logic of a plurality of application logics is present, wherein the metadata associated with the transaction comprises at least one of a transaction ID, a user ID and security credentials, wherein the request data comprises a format having the HTTP request;
responsive to the notification layer that initially received the request data searching in the request data and finding the metadata associated with the transaction, directly instantiating by the notification layer an instance of the application logic having been identified to process the request, directly instantiating the instance of the application logic comprising the notification layer starting the application logic, wherein the notification layer determines which system resource is to serve the request data and sends the metadata to the application logic, wherein the instance of the application logic is determined at least in part based on the metadata associated with the transaction; and
responsive to the notification layer that initially received the request data not finding the identification of the application logic to be selected for instantiation from the plurality of application logics in the metadata associated with the transaction where the metadata is received from the requestor, passing by the notification layer the request data to the establish layer on the OTPS to establish the metadata associated with the transaction, the establish layer having been passed the request data from the notification layer being different from the requestor.

2. The computer-implemented method of claim 1 , wherein reading the request data does not find the metadata associated with the transaction because the request data was encrypted.

3. The computer-implemented method of claim 1 , wherein reading the request data does not find the metadata associated with the transaction because insufficient data in the request has arrived from the requestor.

4. The computer-implemented method of claim 1 , wherein passing the request data from the notification layer to the establish layer to establish the metadata associated with the transaction is further responsive to determining that the request data is not encrypted and determining that sufficient data in the request data has arrived from the requestor.

5. The computer-implemented method of claim 1 , further comprising:
receiving, by the instantiated application logic, all of the request data;
executing, by the instantiated application logic, all of the request data; and
returning, by the instantiated application logic, a response to the requestor.

6. A system for establishing metadata associated with a transaction in a transaction processing system having application logic for executing the transaction, the system comprising:
a memory having computer readable instructions; and
a processor coupled to the memory for executing the computer readable instructions, the computer readable instructions configured to cause the processor to:
receive, by a notification layer from a requestor, request data associated with the transaction, the request data comprising data and metadata, the transaction being an online transaction, the notification layer that initially received the request data being configured to start an application logic and to start an establish layer according to the metadata, wherein the request data is received in a plurality of chunks by the notification layer, the plurality of chunks being blocks of the request data;
monitor an amount of data that has been received from the requestor;
based on the notification layer determining that a first chunk of the plurality of chunks has been received and the notification layer determining that a first line of a hypertext transfer protocol (HTTP) request has been received in the first chunk, read by the notification layer the received request data looking for metadata associated with the transaction to determine whether identification of the application logic of a plurality of application logics is present, wherein the metadata associated with the transaction comprises at least one of a transaction ID, a user ID and security credentials, wherein the request data comprises a format having the HTTP request; and
responsive to the notification layer that initially received the request data searching in the request data and finding the metadata associated with the transaction, instantiate by the notification layer an instance of the application logic having been identified to process the request, directly instantiating the instance of the application logic comprising the notification layer starting the application logic, wherein the notification layer determines which system resource is to serve the request data and sends the metadata to the application logic, wherein the instance of the application logic is determined at least in part based on the metadata associated with the transaction; and
responsive to the notification layer that initially received the request data not finding the identification of the application logic to be selected for instantiation from the plurality of application logics in the metadata associated with the transaction where the metadata is received from the requestor, pass by the notification layer the request data to the establish layer to establish the metadata associated with the transaction, the establish layer having been passed the request data from the notification layer being different from the requestor.

7. The system of claim 6 , wherein reading the request data does not find the metadata associated with the transaction because the request data was encrypted.

8. The system of claim 6 , wherein reading the request data does not find the metadata associated with the transaction because insufficient data in the request has arrived from the requestor.

9. The system of claim 6 , wherein passing the request data from the notification layer to the establish layer to establish the metadata associated with the transaction is further responsive to determining that the request data is not encrypted and determining that sufficient data in the request data has arrived from the requestor.

10. The system of claim 6 , wherein the application logic receives all of the request data, executes all of the request data, and returns a response to the requestor.

11. A computer program product for establishing metadata associated with a transaction in a transaction processing system having application logic for

Assignees

• IBM

Inventors

• Bohm Fraser P
• Brooks Michael D
• Cocks Martin W
• He Jenny J
• Horn Julian C

Classifications

• G06F16/252

  between a Database Management System and a front-end application · CPC title

• G06F16/2379 Primary

  Updates performed during online database operations; commit processing · CPC title

• G06F16/2365

  Ensuring data consistency and integrity · CPC title