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 first request to a first thread-based server from a first thread-based client is detected. The first request is derived by the first thread-based client in response to a first call from a first user program running on process-based middleware. The first request is intercepted from a communication pathway. The first request is converted to a merged request. The merged request is intended for a merged thread-based server of the thread-based middleware. The merged request is sent to the merged thread-based server.

Abstract: A method for dynamic transaction request grouping and allocation in a distributed transaction processing system. The method may implement interconnected transaction process monitors to manage the handling and servicing of transaction requests with respect to networked computing platforms of the distributed transaction processing system.

Abstract: An embodiment of the invention may include a method, computer program product and system for processing a transaction. The embodiment may include receiving a transaction request by a first transaction processing monitor from a plurality of transaction processing monitors. The transaction request contains details for updating a global database. The embodiment may include determining whether the global database has begun updating based on the transaction request. Determining whether the global database has begun updating includes checking a transaction state database. The embodiment may include determining that the global database has not begun updating, and updating an entry in the global database based on the details contained in the transaction request.

Abstract: A technique relates to dynamically determining a transaction coordinator. A transaction processing middleware (TPM) coordinator receives TPM weightages of TPM participants, where the TPM coordinator has a TPM coordinator weightage, and where the TPM coordinator and TPM participants are executing a transaction instance. The TPM coordinator individually compares the TPM coordinator weightage to each of the TPM weightages of the TPM participants. In response to not one of the TPM weightages of the TPM participants being greater than the TPM coordinator weightage, the TPM coordinator is kept unchanged. In response to a given TPM weightage of the TPM weightages of the TPM participants being greater than the TPM coordinator weightage, the TPM coordinator changes a TPM coordinator function to a given TPM participant having the given TPM weightage such that the given TPM participant is an interim TPM coordinator for the transaction instance.

Abstract: Aspects of the present invention include methods, systems and computer program products.

Abstract: A coordinator transaction processing monitor determines a transaction coordinator identifier associated with a transaction that spans transaction processing monitors distributed between transaction processing systems. The coordinator transaction processing monitor attaches the transaction coordinator identifier as part of a transaction request of an application flow of the transaction. The transaction request from the coordinator transaction processing monitor is transmitted to a next transaction processing monitor to sequentially propagate through the transaction processing monitors. A response from the next transaction processing monitor is received. The response includes a transaction resolution endpoint identifier for each of the transaction processing monitors participating in the transaction.

Abstract: Systems and methods for sharing transactional context between Java and traditional language applications are disclosed. In embodiments, a method comprises: receiving, by a computing device, a transaction request to execute a program, wherein the program comprises non-Java program components and Java program components; executing, by a transaction middleware of the computing device, the non-Java program components; contacting, by the transaction middleware, a resource manager server and registering with the resource manager server using global transaction ID data; transferring, by the transaction middleware of the computing device, the Java program components to a transaction coordinator of the computing device, along with thread ID data and the global transaction ID data; and storing, by the transaction coordinator, the thread ID data and global transaction ID data in a recoverable transaction log store.

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: Method and apparatus for predicting a transaction's outcome in a transaction processing environment are provided. A transaction request is received by a transaction processing monitor (TPM), where the transaction request comprises a plurality of tags. The TPM identifies historical prior transactions corresponding to the transaction request, and determines a plurality of historical tags associated with those historical transactions. The TPM then determines whether a predicted execution time exceeds the transaction request's timeout, and proceeds accordingly. If the predicted execution time exceeds the timeout value, the transaction is immediately returned as failed. The tags associated with a given transaction request are repeatedly updated as the request traverses the transaction processing system, and the transaction is repeatedly verified to ensure that it can still be completed successfully.

Abstract: Map files associated with a terminal-based legacy application, such as a Customer Information Control System (CICS) application, are converted to views and models of a web-based application, such as an application implemented with a Java Platform Enterprise Edition (JEE) compliant server. A hybrid application server executes the legacy application in a first runtime, such as a CICS runtime, in response to a user request received through the web-based application executing in a second runtime, such as a JEE runtime. When a terminal command is identified in the executing legacy application, data associated with the terminal command is packetized and forwarded to the web-based application through an established socket without creating a data stream. The web-based application invokes the models associated with the terminal command and presents a web page responsive to the terminal command to the user.

Abstract: A first request to a first thread-based server from a first thread-based client is detected. The first request is derived by the first thread-based client in response to a first call from a first user program running on process-based middleware. The first request is intercepted from a communication pathway. The first request is converted to a merged request. The merged request is intended for a merged thread-based server of the thread-based middleware. The merged request is sent to the merged thread-based server.

Abstract: An embodiment of the invention may include a method, computer program product and system for processing a transaction. The embodiment may include receiving a transaction request by a first transaction processing monitor from a plurality of transaction processing monitors. The transaction request contains details for updating a global database. The embodiment may include determining whether the global database has begun updating based on the transaction request. Determining whether the global database has begun updating includes checking a transaction state database. The embodiment may include determining that the global database has not begun updating, and updating an entry in the global database based on the details contained in the transaction request.

Abstract: Map files associated with a terminal-based legacy application, such as a Customer Information Control System (CICS) application, are converted to views and models of a web-based application, such as an application implemented with a Java Platform Enterprise Edition (JEE) compliant server. A hybrid application server executes the legacy application in a first runtime, such as a CICS runtime, in response to a user request received through the web-based application executing in a second runtime, such as a JEE runtime. When a terminal command is identified in the executing legacy application, data associated with the terminal command is packetized and forwarded to the web-based application through an established socket without creating a data stream. The web-based application invokes the models associated with the terminal command and presents a web page responsive to the terminal command to the user.

Abstract: Map files associated with a terminal-based legacy application, such as a Customer Information Control System (CICS) application, are converted to views and models of a web-based application, such as an application implemented with a Java Platform Enterprise Edition (JEE) compliant server. A hybrid application server executes the legacy application in a first runtime, such as a CICS runtime, in response to a user request received through the web-based application executing in a second runtime, such as a JEE runtime. When a terminal command is identified in the executing legacy application, data associated with the terminal command is packetized and forwarded to the web-based application through an established socket without creating a data stream. The web-based application invokes the models associated with the terminal command and presents a web page responsive to the terminal command to the user.

Abstract: Map files associated with a terminal-based legacy application, such as a Customer Information Control System (CICS) application, are converted to views and models of a web-based application, such as an application implemented with a Java Platform Enterprise Edition (JEE) compliant server. A hybrid application server executes the legacy application in a first runtime, such as a CICS runtime, in response to a user request received through the web-based application executing in a second runtime, such as a JEE runtime. When a terminal command is identified in the executing legacy application, data associated with the terminal command is packetized and forwarded to the web-based application through an established socket without creating a data stream. The web-based application invokes the models associated with the terminal command and presents a web page responsive to the terminal command to the user.