Data interoperability between open standard directory service and proprietary database

• US 20040167866A1
• Filed: 02/26/2003
• Published: 08/26/2004
• Est. Priority Date: 02/26/2003
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: AOL LLC (Apollo Global Management, Inc.)
• Inventors: Kaw, Bindu Kaul, Smith, Mark Christopher
• Granted Patent: US 7,184,995 B2
• Time in Patent Office: Days
• US Class Current: 707/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• 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/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method of providing interoperability between an open standard directory service and a proprietary database. The directory is represented as a mapping tree, consistent with directory service protocols such as X.500 or LDAP. The mapping tree node associated with the proprietary database is configured as a null suffix mapping tree entry, so that database mapping tree node replaces root of the mapping tree and the proprietary database the default backend of the directory service. The core server of the directory service is configured to recognize the null suffix mapping tree entry. All directory service operations are routed to a pre-operation plug-in that handles operations in the proprietary database, and remaining operations are redirected to the core server, preserving default functionality of the directory service. Normal data constraints are suspended for operations performed in the proprietary database.

Claims

1. A method of providing interoperability between an open standard directory service and a proprietary database comprising the steps of:

configuring a mapping tree node associated with said proprietary database to replace root of said mapping tree and to replace default backend of said service with said proprietary database;

configuring a core server of said directory service to recognize said mapping tree node associated with said proprietary database as root of said mapping tree;

routing all directory service operations to an object that handles operations in said proprietary database; and

redirecting remaining operations to said core server by said object, so that default server functionality is preserved.

2. The method of claim 1, wherein said step of configuring said mapping tree node associated with said proprietary database comprises configuring said mapping tree node as a null suffix mapping tree entry.

3. The method of claim 2, wherein said step of configuring said core server comprises configuring said server to recognize said null suffix mapping tree entry.

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

suspending at least one data model constraint imposed by said open standard for operations in said proprietary database, so that operations in said proprietary data base can be performed even if said proprietary database doesn'"'"'t conform to said data model constraint.

5. The method of claim 4, wherein said at least one constraint comprises the requirement of a well-formed tree.

6. The method of claim 4, wherein said step of suspending at least one data model constraint imposed by said open standard for operations in said proprietary database comprises invoking said plug-in before said constraints are applied by said server.

7. The method of claim 1, wherein said step of redirecting remaining operations to said core server comprises the steps of:

recognizing naming contexts reserved for exclusive use of said server by said object; and

redirecting operations in these naming contexts to said server.

8. The method of claim 1, further comprising the step of suspending access control checking for actions handled by said object.

9. The method of claim 8, said step of suspending access control checking comprising the steps of:

providing a flag in a data structure of an operation to be handled by said object, wherein setting said flag disables access control; and

setting said flag by said object.

10. The method of claim 1, wherein said object that handles operations in said proprietary database comprises a pre-operation plug-in.

11. The method of claim 1, wherein said open standard comprises any of:

X.500;

LDAP (lightweight directory access protocol); and

DNS.

12. A computer program product comprising computer readable code embodied on a tangible medium or a carrier wave, said code including code means for performing the steps of a method of providing interoperability between an open standard directory service and a proprietary database, the method comprising the steps of:

configuring a mapping tree node associated with said proprietary database to replace root of said mapping tree and to replace default backend of said service with said proprietary database;

configuring a core server of said directory service to recognize said mapping tree node associated with said proprietary database as root of said mapping tree;

routing all directory service operations to an object that handles operations in said proprietary database; and

redirecting remaining operations to said core server by said object, so that default server functionality is preserved.

13. The method of claim 12, wherein said step of configuring said mapping tree node associated with said proprietary database comprises configuring said mapping tree node as a null suffix mapping tree entry.

14. The method of claim 13, wherein said step of configuring said core server comprises configuring said server to recognize said null suffix mapping tree entry.

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

suspending at least one data model constraint imposed by said open standard for operations in said proprietary database, so that operations in said proprietary data base can be performed even if said proprietary database doesn'"'"'t conform to said data model constraint.

16. The method of claim 15, wherein said at least one constraint comprises the requirement of a well-formed tree.

17. The method of claim 15, wherein said step of suspending at least one data model constraint imposed by said open standard for operations in said proprietary database comprises invoking said object before said constraints are applied by said server.

18. The method of claim 12, wherein said step of redirecting remaining operations to said core server comprises the steps of:

recognizing naming contexts reserved for exclusive, use of said server by said object; and

redirecting operations in these naming contexts to said server.

19. The method of claim 12, further comprising the step of suspending access control checking for actions handled by said object.

20. The method of claim 19, said step of suspending access control checking comprising the steps of:

providing a flag in a data structure of an operation to be handled by said object, wherein setting said flag disables access control; and

setting said flag by said object.

21. The method of claim 12, wherein said object that handles operations in said proprietary database comprises a pre-operation plug-in.

22. The method of claim 12, wherein said open standard comprises any of:

X.500;

LDAP (lightweight directory access protocol); and

DNS (domain name service).