Method and system for supplanting a first name base with a second name base

• US 6,108,649 A
• Filed: 03/03/1998
• Issued: 08/22/2000
• Est. Priority Date: 03/03/1998
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Anderson, Brady A., Lasky, Michael E., Ferguson, Daniel T., McKinney, Travis W., Young, Russell T., Cardoza, Bryan J.
• Primary Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US09/034,602
• Time in Patent Office: 903 Days
• Field of Search: 707/4, 707/10, 707/200, 707/3, 395/200.31, 395/683, 395/676, 395/200.49
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A method and system for supplanting a first name base with a second name base. The system consolidates name bases from different network operating systems into a single name base administrable from a single administration utility. Existing first name base applications continue to execute without modification, as communications are transparently translated and redirected to the second name base, and responses translated and communicated back into a format associated with the first name base. The method and system simplify administration of the network, and consolidate multiple name bases into a single name base.

Claims

1. A method for redirecting a request directed to a first name base to a second name base, comprising:

receiving a request initiated by a process that is directed to a first name base;

translating the request from a first name base format to a second name base format suitable for communications with a second name base, wherein the name bases include information regarding one or more network entities;

generating a translated request;

calling the second name base with the translated request;

receiving a response to the translated request from the second name base;

translating the response from the second name base format to the first name base format suitable for communications with the first name base, generating a translated response; and

returning the translated response to the requesting process.

2. A method according to claim 1, further comprising moving a plurality of objects from the first name base to the second name base before the receiving a request step.

3. A method according to claim 2, wherein the moving step further comprises extending classes associated with the second name base for containing representations of data from the first name base.

4. A method according to claim 1, wherein the translating the request step comprises moving portions of data from a parameter list in the request in the first name base format to a parameter list in the translated request in the second name base format.

5. A method according to claim 1, wherein the redirection of a request directed to the first name base to the second name base is transparent to the process.

6. A method according to claim 1, wherein the second name base is associated with a computer network server which is different from a computer network server with which the first name base is associated.

7. A method for replacing a first name base with a second name base, comprising:

moving and storing existing representations stored in a first name base to a second name base, wherein the name bases include information regarding one or more network entities;

receiving a request directed by a requestor to the first name base;

forwarding the request to the second name base; and

returning a response from the second name base to the requester in a first name base format.

8. A method according to claim 7, wherein the moving step comprises reading attributes of objects from the first name base, creating corresponding objects in the second name base, and storing the attribute data read from the first name base into attributes associated with the corresponding objects in the second name base.

9. A method according to claim 7, further comprising translating the request from a first format suitable for communications with the first name base to a second format suitable for communications with the second name base before the request is forwarded to the second name base.

10. A method according to claim 9, wherein the returning step further comprises translating data associated with the response from the second format suitable for communications with the second name base to the first format suitable for communications with the first name base.

11. A method according to claim 7, wherein the replacement of the first name base with the second name base is transparent to at least some processes attempting to communicate with the first name base.

12. A method according to claim 7, wherein the first name base and the second name base are located on different computer servers.

13. A method according to claim 7, wherein the receiving step further comprises replacing a first process associated with the first name base with a second process operative to provide the same external interface that is associated with the first process.

14. A system for replacing a first name base with a second name base, comprising:

a migration and storing process operative to migrate and store data from a first name base to a second name base, wherein the name bases include information regarding one or more network entities;

a receiving process operative to receive a request from a first process to the first name base;

a first translation mechanism coupled to the receiving process operative to translate the request from a first name base format to a second name base format;

a second name base;

a redirection mechanism coupled to the first translation mechanism operative to communicate the request in the second name base format to the second name base; and

the second name base being operative to receive the request from the redirection mechanism.

15. A system according to claim 14, wherein the migration process extends a class associated with the second name base, the extended class being operative to store data associated with objects from the first name base.

16. A system according to claim 14, wherein the first process is located on a computer coupled to a network, the first name base is associated with a first computer server coupled to the network, and the second name base is associated with a second computer server coupled to the network.

17. A system according to claim 14, wherein the receiving process comprises a second function process associated with the second name base that replaces a first function process associated with the first name base, the second function process having an interface which is operative to communicate with the same processes with which the first function process is able to communicate.

18. A system according to claim 14, wherein the redirection mechanism is further operative to receive a response generated by the second name base in response to the request from the redirection mechanism, and is operative to direct the response to the first process.

19. A system according to claim 18, further comprising a second translation mechanism coupled to the redirection mechanism, the second translation mechanism operative to translate the response from the second name base format to the first name base format.

20. A method for consolidating a plurality of first name bases into a consolidated second name base, comprising:

receiving a request directed by a requesting process to one of a plurality of first name bases;

translating the request from a first name base format to a consolidated second name base format suitable for communications with a second name base, wherein the name bases include information regarding one or more network entities generating a translated request;

calling the consolidated second name base with the translated request;

receiving a response to the translated request from the second consolidated name base;

translating the response from the consolidated second name base format to the first name base format suitable for communications with the first name base, generating a translated response; and

returning the translated response to the requesting process.

21. A method for redirecting a request directed to a first name base to a second name base, comprising:

receiving a request initiated by a process that is directed to a first name base, developing a replacement library having entry points suitable for communication with the process, and replacing an existing library associated with the first name base with the replacement library;

translating the request from a first name base format to a second name base format suitable for communications with a second name base, generating a translated request;

calling the second name base with the translated request;

receiving a response to the translated request from the second name base;

translating the response from the second name base format to the first name base format suitable for communications with the first name base, generating a translated response; and

returning the translated response to the requesting process.

22. A method according to claim 21, further comprising moving a plurality of objects from the first name base to the second name base before the receiving a request step.

23. A method according to claim 22, wherein the moving step further comprises extending classes associated with the second name base for containing representations of data from the first name base.

24. A method according to claim 21, wherein the translating the request step comprises moving portions of data from a parameter list in the request in the first name base format to a parameter list in the translated request in the second name base format.

25. A method according to claim 21, wherein the redirection of a request directed to the first name base to the second name base is transparent to the process.

26. A method according to claim 21, wherein the second name base is associated with a computer network server which is different from a computer network server with which the first name base is associated.