Method and system for accessing data in legacy applications

• US 6,836,780 B1
• Filed: 04/18/2000
• Issued: 12/28/2004
• Est. Priority Date: 09/01/1999
• Status: Expired due to Term

• Current Assignee: Software AG Ltd. (Software AG)
• Original Assignee: Jacada, Ltd.
• Inventors: Elkin, Alex, Opitz, Scott
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US09/551,704
• Time in Patent Office: 1,715 Days
• Field of Search: 358/1.16, 345/589, 345/744, 345/853, 707/200, 707/103.R, 707/203, 707/205, 707/1, 709/246, 709/223, 711/162
• US Class Current: 1/1
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A method and apparatus is presented for mapping legacy application data. The mapping process consists of trail recording, mapping, and template creation. In the trail recording phase, user interaction with the legacy application is recorded as a trail. Each trail consists of snapshots of every screen encountered, and all of the keystrokes entered by the user. After trail creation, maps of the legacy application are created by sorting the screen snapshots into screens. The sorting is done according to specific rules that are controlled by the end user. The default rules allocate snapshots according to the number, position, and location of the predefined fields found in the snapshots. Additional tags can be defined of alphanumeric text to help properly identify the screens. Templates are then created to allow direct access to the data found on the screens of the legacy application. Separate templates allow access to static fields and tabular fields. Methods are then defined to access particular data in the legacy application. One or more methods can then be defined as a service, which is compiled into a reusable software component.

Claims

1. A method for mapping data in a legacy application comprising:

a) using a terminal editor for a session with the legacy application;

b) recording snapshots of all screens received by the terminal editor;

c) forming a trail for the terminal session, each trail including a snapshot of each screen accessed; and

d) using screen identification rules to recognize snapshots that are the same screen.

2. The method of claim 1, further comprising the step of:

e) repeating steps a through c as necessary to access all screens containing data fields that are needed for the map.

3. The method of claim 1, wherein the step of using screen identification rules comprises the sub-steps of:

i) identifying preformatted fields in the screen snapshots received by the terminal editor; and

ii) dividing snapshots into screens according to the preformatted fields.

4. The method of claim 3, wherein snapshots are divided into screens by examining the number, size, and location of the preformatted fields.

5. The method of claim 3, wherein the step of using screen identification rules further comprises the sub-step of:

iii) identifying tags of alphanumeric text found on the snapshots; and

iv) dividing snapshots into screens according to tags.

6. The method of claim 1, wherein the step of using screen identification rules further comprises the sub-steps of:

i) identifying tags of alphanumeric text found on the snapshots; and

ii) dividing snapshots into screens according to tags.

7. The method of claim 1 further comprising the steps of:

f) recording all keystrokes sent to the legacy application during the session with the legacy application;

g) including in each trail the keystrokes typed during a particular snapshot and the resulting screen snapshot that was received by the terminal editor after those keystrokes were typed; and

h) generating actions associated with each screen indicating all keystrokes entered and a resulting screen.

8. The method of claim 7, wherein the step of using screen identification rules comprises the sub-steps of:

i) identifying preformatted fields in the screen snapshots received by the terminal editor; and

ii) dividing snapshots into screens according to the preformatted fields.

9. The method of claim 8, wherein snapshots are divided into screens by examining the number, size, and location of the preformatted fields.

10. The method of claim 9, wherein the step of using screen identification rules further comprises the sub-step of:

iii) identifying tags of alphanumeric text found on the snapshots; and

iv) dividing snapshots into screens according to tags.

11. The method of claim 7, wherein the step of using screen identification rules further comprises the sub-steps of:

i) identifying tags of alphanumeric text found on the snapshots; and

ii) dividing snapshots into screens according to tags.

12. The method of claim 7, further comprising the steps of:

h) associating a template of data fields with each screen.

13. The method of claim 12, wherein the template defines a table of repeating fields.

14. The method of claim 12, further comprising the step of:

i) creating a reusable software component containing a map of the legacy application, the map including the screens, the actions indicating the keystrokes necessary to move to a next screen, and the template of data fields available on the screens.

15. A software program capable of operating on a CPU containing an graphical user interface, the CPU in communication with a legacy application on a host computer through a terminal editor, the program comprising:

a) a recording mechanism for recording trails, the trails containing

i) screen snapshots received by the terminal editor;

ii) formatted fields found in the screen snapshots, and

iii) keystrokes entered at each screen snapshot;

b) a map creation mechanism for creating a map of the legacy application, the map containing

i) individual screens identified from the screen snapshots according to screen identification rules, and

ii) one or more actions associated with each screen, the actions containing keystrokes entered at each screen and a destination screen.

16. The software program of claim 15, wherein the screen identification rules comprise the arrangement of formatted fields found in the screen snapshots.

17. The software program of claim 16, further comprising:

c) a tag identification interface for selecting a region of alphanumeric text to comprise part of the screen identification rules.

18. The software program of claim 15, further comprising:

c) a data field template interface for identifying data fields in the legacy application.

19. The software program of claim 18, further comprising:

d) a method creation interface for creating methods that exchange data with the legacy application.

20. The software program of claim 19, further comprising:

e) a service creation mechanism to generate reusable software component services containing one or more methods.

21. A system for mapping a legacy application comprising:

a) a host computer operating a legacy application;

b) a data connection in communication with the host computer;

c) a CPU operating a graphical user interface and in communication with the data connection, the CPU having;

i) trail recordation means for recording trails of interaction with the legacy application;

ii) map creation means for creating a map of the legacy application based upon screen identification rules.

22. The system of claim 21, wherein the CPU is a workstation.

23. The system of claim 21, wherein the CPU further comprises:

iii) a terminal editor to interact directly with the legacy application.

24. The system of claim 21, wherein the CPU further comprises:

iii) generation means for generating a reusable software component containing the map.