System for handling asynchronous database transactions in a web based environment

Abstract

A system and computer readable medium for handling asynchronous database transactions in a web based environment is disclosed. The system and computer readable medium comprise providing a first ID from a device via a dedicated persistent connection and generating a second ID in an application server upon receipt of the first ID. The system and computer readable medium also include utilizing the first ID and second ID to obtain the appropriate data from a database system and to send the appropriate data to the device. A system and computer readable medium in accordance with the present invention uses a database resource adapter, which runs inside an application server, to generate a socket ID internally for every input transaction running with the dedicated persistent socket connection and also saves the customer-specified client ID for database queue creation and legacy application. This operation is transparent to the customers' client application.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS[0001]Under 35 USC §120, this application is a continuation application and claims the benefit of priority to U.S. patent application Ser. No. 11 / 226,812 filed Sep. 13, 2005, entitled “METHOD AND SYSTEM FOR HANDLING ASYNCHRONOUS DATABASE TRANSACTIONS IN A WEB BASED ENVIRONMENT”, all of which is incorporated herein by reference.FIELD OF THE INVENTION[0002]The present invention relates generally to databases and more specifically to handling database transactions in web based environments.BACKGROUND OF THE INVENTION[0003]Sysplex (multiprocessor cluster-based) enabled infrastructures are utilized extensively for workflow of client applications. For example, they are utilized in automatic teller machine (ATM) transactions. It has been found that some banking customers have experienced significant operational issues when accessing data in such an infrastructure.[0004]Any customer who has a sysplex-enabled infrastructure that uses a web application s...

AI Technical Summary

Problems solved by technology

It has been found that some banking customers have experienced significant operational issues when accessing data in such an infrastructure.

Any customer who has a sysplex-enabled infrastructure that uses a web application server, such as WebSphere, with a TCP / IP gateway (for example, IMS Connect) to access a database and sends their asynchronous transactions using dedicated persistent socket will receive a duplicate client ID problem.

When the duplicate socket ID problem is generated, the transaction request that was sent will either hang, return an error message, or become lost.

This is a severe problem because the customer's clients potentially will be left standing at an ATM machine waiting for a transaction that cannot be completed.

Another scenario that generates the duplicated client ID problem is if the customer uses one application server and creates multiple servant regions within that server.

This problem increases exponentially if any customer has a sysplex structure where there are multiple application servers and each of those servers have multiple servant regions.

However, with this method, the customers must rewrite their client applications and not specify a customer-specified client ID to an application server.

This eliminates the capability of using the customer-specified client ID for tracking, security, and maintenance purposes.

Furthermore, with this solution, using the sharable persistent socket increases the number of IMS output queues, thus impacting IMS storage requirements.

Images