Method for native program to inherit same transaction context when invoked by primary program running in separate environment

• US 9,760,583 B2
• Filed: 05/03/2013
• Issued: 09/12/2017
• Est. Priority Date: 06/30/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ananthapadmanabh, Madhu B., Kurian, John, Mitchell, Ian J., Sood, Ajay, Venkitachalam, Hariharan
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): CHEUNG, HUBERT G
• Application Number:
  US13/886,471
• Publication Number:
  US 20130246864A1
• Time in Patent Office: 1,593 Days
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Native applications inherit transaction contexts when invoked by primary applications running in separate hosting environments, by: receiving, by an interface of a native application server in a first hosting environment, a unique transaction context identifier for an invocation of the native application at the native application server by the primary application at a primary application server in a second hosting environment; receiving a SQL statement from the native application by the interface of the native application server; sending the SQL statement and the unique transaction context identifier to the primary application server for execution by the interface of the native application server; receiving a result of the execution of the SQL statement and the unique transaction context identifier from the primary application server by the interface of the native application server; and sending the result to the native application by the interface of the native application server.

Claims

1. A method for a native application to inherit a transaction context when invoked by a primary application running in a separate hosting environment, comprising:

receiving an invocation of the native application to run at a native application server in a first hosting environment separate from a second hosting environment, the invocation initiated by the primary application running at a primary application server in the second hosting environment;

in response to the invocation, receive, by a query transceiver at the native application server, a unique transaction context identifier for the invocation, wherein the unique transaction context identifier is generated in the primary application server when a transaction context is established;

in response to encountering a query statement embedded in the native application during the execution of the native application, send the query statement from the native application to the query transceiver at the native application server;

send the query statement and the unique transaction context identifier from the query transceiver to the primary application server for execution on a database by the primary application server, wherein the database resides on the primary application server;

receive, by the query transceiver, a result of the execution of the query statement and the unique transaction context identifier from the primary application server;

send, by the query transceiver, the result to the native application; and

wherein, the query statement embedded in the native application is executed on the database on the primary application server and the execution of the native application at the native application server in the first hosting environment are performed sharing the same database connection, and without modifying the native application, by passing the unique transaction context identifier along with the query statement, and passing the unique transaction context identifier along with the result of the execution of the query statement.

2. The method of claim 1, wherein the sending the query statement from the native application to the transceiver, further comprises:

converting the query statement to a format of the second hosting environment.

3. The method of claim 1, wherein the receiving the result of the execution of the query statement from the primary application server, further comprises:

converting the result to a format of the first hosting environment.

4. The method of claim 1, wherein the receiving, the invocation of the native application to run at the native application server in the first hosting environment from the primary application running at the primary application server in the second hosting environment, further comprises:

invoking the native application to run at the native application server in the first hosting environment by the primary application running at the primary application server in the second hosting environment;

transferring program control to the first hosting environment by the primary application server; and

sending the unique transaction context identifier for the invocation to the native application server by the primary application server.

5. The method of claim 1, wherein the sending the query statement from the query transceiver to the primary application server for execution on the database by the primary application server, further comprises:

receiving the query statement by the primary application server;

delegating the execution of the query statement to a thread of the primary application server by the primary application server;

executing the query statement on a database by the thread; and

returning the result of the execution of the query statement and the unique transaction context identifier to the native application server by the primary application server.

6. The method of claim 1, wherein the receiving the result of the execution of the query statement from the primary application server, further comprises:

determining, whether the result comprises an error in the execution of the query statement; and

in response to determining that the result comprises the error, converting the error to a format of the first hosting environment.

7. The method of claim 1, further comprising:

determining whether an execution of the native application has terminated;

in response to determining that the execution of the native application has terminated, determining whether the termination of the native application execution is normal; and

in response to determining that the termination of the native application execution is not normal, notifying the primary application server of the abnormal termination.

8. A method for a native application to inherit a transaction context when invoked by a primary application running in a separate hosting environment, comprising:

receiving, by an interface of a native application server in a first hosting environment, a unique transaction context identifier for an invocation of the native application to run at the native application server in a first hosting environment separate from a second hosting environment, the invocation initiated by the primary application at a primary application server in the second hosting environment;

in response to the invocation, receiving a query statement from the native application by the interface of the native application server;

sending the query statement and the unique transaction context identifier to the primary application server for execution by the interface of the native application server;

in response to receiving the query statement from the interface of the native application server by a second interface of the primary application server, delegating the execution of the query statement to a thread of the primary application server by the second interface of the primary application server;

executing the query statement on a database on the primary application server and returning the result of the execution to the second interface by the thread of the primary application server, wherein the query statement embedded in the native application executed on the database on the primary application server and the execution of the native application at the native application server in the first hosting environment are performed sharing the same database connection, and without modifying the native application, by passing the unique transaction context identifier along with the query statement, and passing the unique transaction context identifier along with the result of the execution of the query statement;

returning the result of the execution of the query statement and the unique transaction context identifier to the interface of the native application server by the second interface of the primary application server; and

in response to receiving the result of the execution of the query statement and the unique transaction context identifier from the primary application server by the interface of the native application server, sending the result to the native application by the interface of the native application server.

9. The method of claim 8, wherein the receiving, by the interface of the native application server in the first hosting environment, the unique transaction context identifier for the invocation of the native application to run at the native application server in the first hosting environment separate from the second hosting environment, the invocation initiated by the primary application at the primary application server in the second hosting environment, further comprises:

invoking the native application by the primary application at the primary application server;

transferring program control to the first hosting environment by the primary application server; and

sending the unique transaction context identifier for the invocation to the interface of the native application server by the primary application server.

10. The method of claim 8, wherein the receiving the result of the execution of the query statement and the unique transaction context identifier from the primary application server by the interface of the native application server, further comprises:

determining, by the interface of the native application server, whether the result comprises an error in the execution of the query statement; and

in response to determining that the result comprises the error, converting the error to a format of the first hosting environment by the interface of the native application server.

11. The method of claim 8, further comprising:

determining whether an execution of the native application has terminated by the interface of the native application server;

in response to determining that the execution of the native application has terminated, determining whether the termination of the native application execution is normal by the interface of the native application server; and

in response to determining that the termination of the native application execution is not normal, notifying the primary application server of the abnormal termination by the interface of the native application server.