Integration of legacy database management systems with ODBC-compliant application programs

• US 6,052,685 A
• Filed: 08/13/1997
• Issued: 04/18/2000
• Est. Priority Date: 08/13/1997
• Status: Expired due to Term

• Current Assignee: Avaya Incorporated
• Original Assignee: Mosaix, Inc. (Nokia Corporation)
• Inventors: Miskin, Gregory K., Eastwick, Michael W.
• Primary Examiner(s): Alam, Hosain T.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/910,765
• Time in Patent Office: 979 Days
• Field of Search: 707/1, 707/10, 707/103
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A database integrator is provided to an application program that utilizes the ODBC interface so as to enable the application program to access the data in a legacy DBMS. The application program ("the client program") is located on a workstation, and the legacy DBMS is located on a host computer. The legacy DBMS is used primarily by an application program ("the server program"). The database integrator receives ODBC commands from the client program, and unlike database drivers interacting with non-legacy DBMSs that send SQL statements to the DBMS, the database integrator instead converts these commands into server program-specific commands to manipulate the user interface of the server program, establishes a connection with the server program over a terminal emulation session, and issues the server program-specific commands to the server program by using the terminal emulator. These server program-specific commands manipulate the server program'"'"'s user interface to display the appropriate data so that the database integrator can then access it. In this manner, the database integrator accesses the data in the legacy DBMS indirectly by issuing user interface commands to the server program, because the database integrator cannot typically access the legacy DBMS directly. This indirect access enables the client program to gain access to the data in a database that it would not otherwise be able to access.

Claims

1. A method in a data processing system for providing a client application program running on a workstation with access to data stored in a Database Management System (DBMS) of a host computer running a server application program that maintains the DBMS, comprising:

the client application program issuing a first ODBC command to a database integrator component;

the database integrator component receiving the first ODBC command and forming a connection with the server application program over a terminal emulation session with the host computer created by a terminal emulator that emulates the host computer;

the client application program issuing a second ODBC command to the database integrator component, the second ODBC command requesting access to the data stored in the DBMS;

the database integrator component receiving the second ODBC command, converting the second ODBC command into user interface commands that control a user interface of the server application program, with the user interface providing access to at least a portion of the data of the DBMS, and issuing the user interface commands to the server application program via the terminal emulation session to provide the access to the data;

the server application program receiving the user interface commands and accessing the data responsive to receiving the user interface commands;

the client application program issuing a third ODBC command to the database integrator component; and

the database integrator component receiving the third ODBC command and terminating the connection with the server application program responsive to receiving the third ODBC command.

2. The method of claim 1 wherein the second ODBC command performs functionality, wherein the workstation contains a database with user interface commands that perform the functionality of the second ODBC command, and wherein converting the second ODBC command includes accessing the database and identifying the user interface commands that perform the functionality of the second ODBC command.

3. The method of claim 1, wherein the user interface displays the data of the DBMS at a location on the user interface, wherein the method further includes creating a database containing user interface commands by a navigator program receiving an indication of the location of where the data is displayed on the user interface, wherein converting the second ODBC command includes accessing the database to determine the location of where the data is displayed on the user interface, and wherein issuing the user interface commands includes issuing the user interface commands to access the data at the determined location on the user interface.

4. The method of claim 3 wherein the user interface has a plurality of screens, wherein the data is displayed on one of the plurality of screens which is not accessible, and wherein issuing the user interface commands includes issuing the user interface commands to render accessible the one screen on which the data is displayed.

5. The method of claim 1 wherein issuing the user interface commands includes issuing the user interface commands using WinHLLAPI functions.

6. The method of claim 1 wherein the server application program accessing the data includes reading the data and returning the read data to the client application program via the database integrator component.

7. The method of claim 1 wherein the server application program accessing the data includes updating the data.