Generating an internet application for accessing a hierarchical database

• US 6,128,619 A
• Filed: 04/30/1998
• Issued: 10/03/2000
• Est. Priority Date: 04/30/1998
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Fogarasi, Attila Joseph, McBride, Kevin Michael, Ho, Shyh-Mei Fang, Ling, Wai-Yee Doris
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): JUNG, DAVID YIUK
• Application Number:
  US09/070,227
• Time in Patent Office: 887 Days
• Field of Search: 707/1-206, 707/4, 707/101, 707/102, 707/103, 707/10, 709/315, 709/107, 345/335, 717/2, 717/5
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A method, apparatus, and article of manufacture for generating an application for accessing a hierarchical database. A database description and a record layout associated with the hierarchical database are captured and associated to define a specification for the database. Class definitions are then generated from the database specification, wherein the class definitions are instantiated as objects in an objects framework that encapsulate data retrieved from the database. Display forms are also generated from the database specification, wherein the display forms are used to display the data encapsulated by the instantiated objects in the objects framework.

Claims

1. A computerized method for generating an application for accessing a hierarchical database, comprising the steps of:

(a) capturing a database description associated with the hierarchical database;

(b) capturing a record layout associated with the hierarchical database;

(c) associating the database description with the record layout to define a specification for the database;

(d) generating one or more class definitions from the database specification, wherein the class definitions are instantiated as objects in an objects framework that encapsulate data retrieved from the database, wherein the objects framework provides a layered processing model that corresponds to application views, database definitions, and data defined and stored in the hierarchical database; and

(e) generating one or more display forms from the database specification, wherein the display forms are used to display the data encapsulated by the instantiated objects in the objects framework.

2. The method of claim 1, wherein the display forms are HyperText Markup Language display forms.

3. The method of claim 1, wherein the display forms are selected from a group comprising input forms and output forms.

4. The method of claim 3, wherein the input forms include a hidden target data object class name.

5. The method of claim 4, further comprising the step of retrieving an object using the class name.

6. The method of claim 3, wherein the input forms include one or more retrieval contexts.

7. The method of claim 6, further comprising the step of retrieving an object using a qualified search when the retrieval contexts are specified in the input form.

8. The method of claim 6, wherein the retrieval contexts comprise key names for higher level segments in a hierarchical search path.

9. The method of claim 6, further comprising the step of retrieving an object using a non-qualified search when the retrieval contexts are not specified in the input form.

10. The method of claim 3, wherein the input forms include one or more attributes for the target data object.

11. The method of claim 3, wherein the input forms include one or more attributes for the target data object.

12. The method of claim 3, further comprising the step of dynamically building the output form from a skeleton output form combined with one or more attributes from the target data object.

13. The method of claim 3, further comprising the step of generating an output form containing fields associated with a specific data object.

14. The method of claim 1, further comprising the step of storing the database specification in a catalog.

15. The method of claim 1, wherein the objects framework comprises a C++ class library that interfaces to the application program.

16. A computerized apparatus for generating an application for accessing a hierarchical database, comprising:

(a) a computer;

(b) means, performed by the computer, for capturing a database description associated with the hierarchical database;

(c) means, performed by the computer, for capturing a record layout associated with the hierarchical database;

(d) means, performed by the computer, for associating the database description with the record layout to define a specification for the database;

(e) means, performed by the computer, for generating one or more class definitions from the database specification, wherein the class definitions are instantiated as objects in an objects framework that encapsulate data retrieved from the database, wherein the objects framework provides a layered processing model that corresponds to application views, database definitions, and data defined and stored in the hierarchical database; and

(f) means, performed by the computer, for generating one or more display forms from the database specification, wherein the display forms are used to display the data encapsulated by the instantiated objects in the objects framework.

17. The apparatus of claim 16, wherein the display forms are HyperText Markup Language display forms.

18. The apparatus of claim 16, wherein the display forms are selected from a group comprising input forms and output forms.

19. The method of claim 18, wherein the input forms include a hidden target data object class name.

20. The apparatus of claim 19, further comprising means for retrieving an object using the class name.

21. The apparatus of claim 18, wherein the input forms include one or more retrieval contexts.

22. The apparatus of claim 21, further comprising means for retrieving an object using a qualified search when the retrieval contexts are specified in the input form.

23. The apparatus of claim 21, wherein the retrieval contexts comprise key names for higher level segments in a hierarchical search path.

24. The apparatus of claim 21, further comprising means for retrieving an object using a non-qualified search when the retrieval contexts are not specified in the input form.

25. The apparatus of claim 18, wherein the input forms include one or more attributes for the target data object.

26. The apparatus of claim 18, wherein the input forms include one or more attributes for the target data object.

27. The apparatus of claim 18, further comprising means for dynamically building the output form from a skeleton output form combined with one or more attributes from the target data object.

28. The apparatus of claim 18, further comprising means for generating an output form containing fields associated with a specific data object.

29. The apparatus of claim 16, further comprising means for storing the database specification in a catalog.

30. The apparatus of claim 16, wherein the objects framework comprises a C++ class library that interfaces to the application program.

31. An article of manufacture comprising a computer program carrier embodying one or more instructions that, when executed by a computer, causes the computer to perform method steps for generating an application for accessing a hierarchical database, the method comprising the steps of:

(a) capturing a database description associated with the hierarchical database;

(b) capturing a record layout associated with the hierarchical database;

(c) associating the database description with the record layout to define a specification for the database;

(d) generating one or more class definitions from the database specification, wherein the class definitions are instantiated as objects in an objects framework that encapsulate data retrieved from the database, wherein the objects framework provides a layered processing model that corresponds to application views, database definitions, and data defined and stored in the hierarchical database; and

(e) generating one or more display forms from the database specification, wherein the display forms are used to display the data encapsulated by the instantiated objects in the objects framework.

32. The method of claim 31, wherein the display forms are HyperText Markup Language display forms.

33. The method of claim 31, wherein the display forms are selected from a group comprising input forms and output forms.

34. The method of claim 33, wherein the input forms include a hidden target data object class name.

35. The method of claim 34, further comprising the step of retrieving an object using the class name.

36. The method of claim 33, wherein the input forms include one or more retrieval contexts.

37. The method of claim 36, further comprising the step of retrieving an object using a qualified search when the retrieval contexts are specified in the input form.

38. The method of claim 36, wherein the retrieval contexts comprise key names for higher level segments in a hierarchical search path.

39. The method of claim 36, further comprising the step of retrieving an object using a non-qualified search when the retrieval contexts are not specified in the input form.

40. The method of claim 33, wherein the input forms include one or more attributes for the target data object.

41. The method of claim 33, wherein the input forms include one or more attributes for the target data object.

42. The method of claim 33, further comprising the step of dynamically building the output form from a skeleton output form combined with one or more attributes from the target data object.

43. The method of claim 33, further comprising the step of generating an output form containing fields associated with a specific data object.

44. The method of claim 31, further comprising the step of storing the database specification in a catalog.

45. The method of claim 31, wherein the objects framework comprises a C++ class library that interfaces to the application program.