Abstract: Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

Abstract: Methods and systems for distributed transaction processing include assigning portions of a logical unit of work to one or more transaction participants. Resource usage information relating to the portions of the logical unit of work is tracked from the respective one or more transaction participants. A last participant is determined based on the tracked resource usage information using a processor. The logical unit of work is resolved. Resolving the logical unit of work includes sending a prepare flow to each of the transaction participants except the last participant to optimize resolution efficiency.

Abstract: Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

Abstract: Embodiments include methods, systems and computer program products for performing a two-phase commit conformance test for a cloud based online transaction processing system (OLTP). Aspects include receiving, by a test case manager of the OLTP from a transaction manager of the OLTP, a transaction event including metadata regarding a transaction and determining a state of the transaction. Aspects also include identifying a test case based on the metadata and the state of the transaction and issuing state events to the transaction manager, wherein the state events are determined based on the test case. Aspects further include obtaining log information from the transaction manager and determining compliance by the transaction manager with the two-phase commit conformance test based at least in part on the log information.

Abstract: A method, computer program product, and a system to globally serialize transactions where a processor(s) establishes a communications connection a (serialization) resource and a resource manager for a distributed computing system. The processor(s) obtains a first request from an application executing on the resource for access to a global resource managed by the resource manager, for executing a transaction. The processor(s) implements a lock for the global resource in an object store of the resource manager over the communications connection. The processor(s) communicates the lock to the application, which executes the transaction and the processor(s) updates a memory with a record comprising attributes of the lock. The processor(s) obtains a second request from the application to terminate the lock, obtains, identifies the lock for the transaction, in the object store, and updates the object store to delete the lock.

Abstract: Techniques for handling transactions are provided. A first transaction is received at an application system of a distributed system. The first transaction is completed, where completing the first transaction comprises writing a record to a queue. A response is generated by an application resource monitor (ARM) of the application system, where the response identifies the record and the application system. The response is transmitted to a transaction distribution system, where the transaction distribution system distributes transactions among application systems in the distributed system. A second transaction is received at the application system. Upon determining that the second transaction is a trigger transaction, the ARM determines a plurality of records that are associated with the second transaction, where the plurality of records includes the record. The ARM retrieves the record from the queue, and completes the second transaction based at least in part on the record.

Abstract: A method, computer program product, and a system to globally serialize transactions where a processor(s) establishes a communications connection a (serialization) resource and a resource manager for a distributed computing system. The processor(s) obtains a first request from an application executing on the resource for access to a global resource managed by the resource manager, for executing a transaction. The processor(s) implements a lock for the global resource in an object store of the resource manager over the communications connection. The processor(s) communicates the lock to the application, which executes the transaction and the processor(s) updates a memory with a record comprising attributes of the lock. The processor(s) obtains a second request from the application to terminate the lock, obtains, identifies the lock for the transaction, in the object store, and updates the object store to delete the lock.

Abstract: Techniques for handling transactions are provided. A first transaction is received at an application system of a distributed system. The first transaction is completed, where completing the first transaction comprises writing a record to a queue. A response is generated by an application resource monitor (ARM) of the application system, where the response identifies the record and the application system. The response is transmitted to a transaction distribution system, where the transaction distribution system distributes transactions among application systems in the distributed system. A second transaction is received at the application system. Upon determining that the second transaction is a trigger transaction, the ARM determines a plurality of records that are associated with the second transaction, where the plurality of records includes the record. The ARM retrieves the record from the queue, and completes the second transaction based at least in part on the record.

Abstract: A method, system and computer program is provided for enabling varying computer applications that are running in Enterprise Information System to send request to a cluster of Java Enterprise Server (J2EE server) cluster. One or more computers provide an application server environment including one or more servers operating within the application server environment to run an application. The computers create a cluster of resource adapters and create a cluster thread for each of the resource adapters to read a cluster port from configured properties, wherein the cluster thread for each of the resource adapters enables an enterprise information system to participate in a cluster of J2EE runtime servers.

Abstract: Systems, methods, and apparatuses to perform an operation receiving, by a first workload manager in a first middleware environment, state information for a plurality of applications executing in a second middleware environment defining, by the first workload manager based on the received state information, a first routing rule in the first middleware environment, and, based on the first routing rule: identifying, by a first application of a plurality of applications executing in the first middleware environment, a second application of the plurality of applications executing in the second middleware environment, and forwarding, by the first application of the plurality of applications executing in the first middleware environment, a first workload to the second application of the plurality of applications executing in the second middleware environment.

Abstract: Methods and systems for distributed transaction processing include assigning portions of a logical unit of work to one or more transaction participants. Resource usage information relating to the portions of the logical unit of work is tracked from the respective one or more transaction participants. A last participant is determined based on the tracked resource usage information using a processor. The logical unit of work is resolved. Resolving the logical unit of work includes sending a prepare flow to each of the transaction participants except the last participant to optimize resolution efficiency.

Abstract: Methods and systems for distributed transaction processing include assigning portions of a logical unit of work to one or more transaction participants. Resource usage information relating to the portions of the logical unit of work is tracked from the respective one or more transaction participants. A last participant is determined based on the tracked resource usage information using a processor. The logical unit of work is resolved. Resolving the logical unit of work includes sending a prepare flow to each of the transaction participants except the last participant to optimize resolution efficiency.

Abstract: A method, system and computer program is provided for enabling varying computer applications that are running in Enterprise Information System to send request to a cluster of Java Enterprise Server (J2EE server) cluster. One or more computers provide an application server environment including one or more servers operating within the application server environment to run an application. The computers create a cluster of resource adapters and create a cluster thread for each of the resource adapters to read a cluster port from configured properties, wherein the cluster thread for each of the resource adapters enables an enterprise information system to participate in a cluster of J2EE runtime servers.

Abstract: Methods and systems for distributed transaction processing include assigning portions of a logical unit of work to one or more transaction participants. Resource usage information relating to the portions of the logical unit of work is tracked from the respective one or more transaction participants. A last participant is determined based on the tracked resource usage information using a processor. The logical unit of work is resolved. Resolving the logical unit of work includes sending a prepare flow to each of the transaction participants except the last participant to optimize resolution efficiency.

Abstract: Systems, methods, and apparatuses to perform an operation receiving, by a first workload manager in a first middleware environment, state information for a plurality of applications executing in a second middleware environment defining, by the first workload manager based on the received state information, a first routing rule in the first middleware environment, and, based on the first routing rule: identifying, by a first application of a plurality of applications executing in the first middleware environment, a second application of the plurality of applications executing in the second middleware environment, and forwarding, by the first application of the plurality of applications executing in the first middleware environment, a first workload to the second application of the plurality of applications executing in the second middleware environment.

Abstract: A processor receives a request to perform a transaction, wherein each activity of the transaction is respectively associated with an application server process. The processor creates an entry in a mapping file, which includes at least information regarding the transaction, one or more resource managers to perform activities of the transaction, and the resources managed by the one or more resource managers. In response to detection of a failure of a resource manager of the one or more resource managers, the processor receives a notification from a call-back function of an XA specification switch of the resource manager associated with the failure. The processor identifies an application server process associated with the failure of the resource manager, and sends an event to terminate the application server process associated with the failure of the resource manager.

Abstract: A processor receives a request to perform a transaction, wherein each activity of the transaction is respectively associated with an application server process. The processor creates an entry in a mapping file, which includes at least information regarding the transaction, one or more resource managers to perform activities of the transaction, and the resources managed by the one or more resource managers. In response to detection of a failure of a resource manager of the one or more resource managers, the processor receives a notification from a call-back function of an XA specification switch of the resource manager associated with the failure. The processor identifies an application server process associated with the failure of the resource manager, and sends an event to terminate the application server process associated with the failure of the resource manager.

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.

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.

Abstract: A processor receives a request to perform a transaction, wherein each activity of the transaction is respectively associated with an application server process. The processor creates an entry in a mapping file, which includes at least information regarding the transaction, one or more resource managers to perform activities of the transaction, and the resources managed by the one or more resource managers. In response to detection of a failure of a resource manager of the one or more resource managers, the processor receives a notification from a call-back function of an XA specification switch of the resource manager associated with the failure. The processor identifies an application server process associated with the failure of the resource manager, and sends an event to terminate the application server process associated with the failure of the resource manager.