System and method for accessing a directory services respository

• US 6,016,499 A
• Filed: 07/21/1997
• Issued: 01/18/2000
• Est. Priority Date: 07/21/1997
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Ferguson, Daniel T.
• Primary Examiner(s): Fetting, Anton W.
• Assistant Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US08/897,526
• Time in Patent Office: 911 Days
• Field of Search: 707/101, 707/104, 707/100, 707/10, 707/102, 707/1
• 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/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

Methods and systems are provided for database-style access to a directory services repository stored on a computer network. A directory services application programming interface is controlled by a driver. The driver translates relational database language statements, such as ODBC-compliant SQL statements, into an executable API sequence that produces an API result. The driver also translates the API result into a relational database result. The repository may be a Novell Directory Services repository or an X.500 directory services repository. The invention maps an effective class of the repository to a table identified in the relational database language statement. Each object that is an instance of the effective class is mapped to a row in the table, and each attribute maps to a column of the table. As a result, the invention allows database tools such as report generators to work with the information stored in the repository.

Claims

1. A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising:

a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; and

a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database result,

wherein the directory services repository component includes an effective class and an object having a context the relational database language statement identifies a table and a subset restriction, and the driver and the API together map the effective class to the table and also map the context to the subset restriction.

2. The system of claim 1, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.

3. The system of claim 1, wherein the API includes a Lightweight Directory Access Protocol API.

4. The system of claim 1, wherein the API includes a Java Naming and Directory Interface API.

5. The system of claim 1, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.

6. The system of claim 1, further comprising a NetWare Core Protocol API, also known as the NCP API, wherein the driver is also capable of translating a relational database language statement into an executable NCP API sequence that includes a call to a callable element of the NCP API and produces an NCP API result, and the driver is also capable of translating the NCP API result into a relational database result.

7. The system of claim 1, wherein the relational database language statement is written in a Structured Query Language format.

8. The system of claim 1, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.

9. The system of claim 1, wherein the driver provides read-only access to the directory services repository.

10. The system of claim 1, wherein the driver provides read and write access to the directory services repository.

11. The system of claim 1, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.

12. The system of claim 1, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more date" indication is returned because each object, if any, has been accessed.

13. The system of claim 1, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the driver and the API together map the attribute to the column.

14. The system of claim 13, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.

15. The system of claim 1, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.

16. The system of claim 1, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic object name to the column.

17. The system of claim 1, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.

18. A method for providing access to a directory services repository which is stored on a server computer in a computer network, the method comprising the steps of:

interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called;

providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result;

mapping an effective class in the directory services repository to a table identified in the relational database language statement;

mapping an object that is an instance of the effective class to a row in the table; and

mapping a context of the object to a subset restriction in the relational database language statement; and

requesting access to the repository by passing the relational database language statement to the driver.

19. The method of claim 18, wherein the requesting step passes a Structured Query Language statement to the driver.

20. The method of claim 18, further including the step of mapping an attribute in the directory services repository to a column of a table identified in the relational database language statement.

21. A computer storage medium having a configuration that represents data and instructions which will cause at least a portion of a computer system to perform method steps for providing access to a directory services repository which is stored on a server computer in a computer network, the method steps comprising the steps of:

interfacing with a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called;

providing a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result;

mapping an effective class in the directory services repository to a table identified in the relational database language statement;

mapping an object that is an instance of the effective class to a row in the table; and

mapping a context of the object to a subset restriction in the relational database language statement; and

requesting access to the repository by passing the relational database language statement to the driver.

22. The storage medium of claim 21, wherein the requesting step passes a Structured Query Language statement to the driver.

23. The storage medium of claim 21, wherein the method further includes the step of mapping an attribute in the directory services repository to a column of a table identified in the relational database language statement.

24. A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising:

a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called, the API including a Java Naming and Directory Interface API; and

a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database results,

wherein the directory services repository component includes an effective class and an object having a context the relational database language statement identifies a table and a subset restriction, and the driver and the API together map the effective class to the table and also map the context to the subset restriction.

25. The system of claim 24, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.

26. The system of claim 24, wherein the API includes a Lightweight Directory Access Protocol API.

27. The system of claim 24, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.

28. The system of claim 24, further comprising a NetWare Core Protocol API, also known as the NCP API, wherein the driver is also capable of translating a relational database language statement into an executable NCP API sequence that includes a call to a callable element of the NCP API and produces an NCP API result, and the driver is also capable of translating the NCP API result into a relational database result.

29. The system of claim 24, wherein the relational database language statement is written in a Structured Query Language format.

30. The system of claim 24, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.

31. The system of claim 24, wherein the driver provides read-only access to the directory services repository.

32. The system of claim 24, wherein the driver provides read and write access to the directory services repository.

33. The system of claim 24, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.

34. The system of claim 24, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.

35. The system of claim 24, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the driver and the API together map the attribute to the column.

36. The system of claim 35, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.

37. The system of claim 24, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.

38. The system of claim 24, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the nonmnemonic object name to the column.

39. The system of claim 24, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.

40. The system of claim 28, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.

41. The system of claim 28, wherein the API includes a Lightweight Directory Access Protocol API.

42. The system of claim 28, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.

43. The system of claim 28, wherein the relational database language statement is written in a Structured Query Language format.

44. The system of claim 28, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.

45. The system of claim 28, wherein the driver provides read-only access to the directory services repository.

46. The system of claim 28, wherein the driver provides read and write access to the directory services repository.

47. The system of claim 28, wherein the directory services repository component includes an effective class, the relational database language statement identifies a table, and the drive and API together map the effective class to the table.

48. The system of claim 47, wherein the directory services repository component inlcudes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.

49. The system of claim 47, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.

50. The system of claim 47, wherein the directory services repository component includes an object having a context, the relational database language statement identifies a subset restriction, and the driver and the API together map the context to the subset restriction.

51. The system of claim 28, wherein the directory services repository component includes an attribute, the relational database language statement identifies a column of a table, and the drive and the API together map the attribute to the column.

52. The system of claim 51, wherein the attribute has a plurality of simultaneous values, and the driver and the API together map each value to a separate row in the table, thereby presenting a one-to-many relation.

53. The system of claim 28, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.

54. The system of claim 28, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic object name to the column.

55. The system of claim 28, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.

56. A system providing access to a directory services repository which is stored on a computer system, the claimed system comprising:

a directory services application programming interface, also known as the API, which includes at least one callable element that is capable of accessing a component of the directory services repository in response to being called; and

a driver which is capable of translating a relational database language statement into an executable API sequence that includes a call to the callable element and produces an API result, the driver also being capable of translating the API result into a relational database result,

wherein the directory services repository component includes an attribute which has a plurality of simultaneous values, the relational database language statement identifies a column of a table, the driver and the API together map the attribute to the column, and the driver and the API together map each value of the attribute to a separate row in the table, thereby presenting a one-to-many relation.

57. The system of claim 56, wherein the directory services repository includes a Novell Directory Services repository and the API includes a Novell Directory Services API.

58. The system of claim 56, wherein the API includes a Lightweight Directory Access Protocol API.

59. The system of claim 56, wherein the directory services repository includes an X.500 directory services repository and the API includes an X.500 directory services API.

60. The system of claim 56, wherein the relational database language statement is written in a Structured Query Language format.

61. The system of claim 56, wherein the relational database language statement conforms with at least one version of the Open Database Connectivity standard.

62. The system of claim 56, wherein the driver provides read-only access to the directory services repository.

63. The system of claim 56, wherein the driver provides read and write access to the directory services repository.

64. The system of claim 56, wherein the directory services repository component includes an effective class, the relational database language statement identifies a table, and the driver and the API together map the effective class to the table.

65. The system of claim 64, wherein the directory services repository component includes an object that is an instance of the effective class, the relational database language statement identifies a row in the table, and the driver and the API together map the object to the row.

66. The system of claim 64, wherein the driver and the API allow an application program to discover the number of rows of the table by visiting each object, if any, which is an instance of the effective class, until a "no more data" indication is returned because each object, if any, has been accessed.

67. The system of claim 56, wherein the directory services repository component includes a distinguished name attribute, the relational database language statement requests identification of a column that is most efficient for repositioning to a row, and the driver and the API together respond to the statement by identifying the column that is mapped to the distinguished name attribute.

68. The system of claim 56, wherein the directory services repository component includes a non-mnemonic object name, the relational database language statement identifies a column of a table, and the driver and the API together map the nonmnemonic object name to the column.

69. The system of claim 56, wherein the directory services repository component includes a non-mnemonic tree name, the relational database language statement identifies a column of a table, and the driver and the API together map the non-mnemonic tree name to the column.