Persistent storage managers for configuring client/server environments

• US 6,351,751 B1
• Filed: 05/14/1998
• Issued: 02/26/2002
• Est. Priority Date: 05/14/1998
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation, Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: International Business Machines Corporation, Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Tracey, William J., Woodward, Steve, Schmidt, Jeffrey A., Traversat, Bernard A., Saulpaugh, Thomas
• Primary Examiner(s): Black, Thomas
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US09/079,042
• Time in Patent Office: 1,384 Days
• Field of Search: 709/303, 709/301, 709/220, 709/219, 713/2, 395/500.34, 707/103, 710/3
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Innovative managers of persistent data are provided. As an example, in a client/server environment, a persistent manager object may be initialized on both the client and server subsystems. The persistent manager objects may be instances of the same persistent manager class. The persistent manager object on the client subsystem may receive a request to store persistent data and the persistent manager object on the client sends the request to the persistent manager object on the server subsystem. The persistent manager object on the server subsystem may then store the persistent data to make it subsequently be available for the client subsystem.

Claims

1. A method for initializing a client subsystem comprising:

instantiating a first persistent manager object on a client subsystem, the first persistent manager object being an instance of a persistent manager class;

the first persistent manager object on the client subsystem sending a request for initialization data to a second persistent manager object on a server subsystem, the second persistent manager object being an instance of the persistent manager class;

the second persistent manager object fulfilling the request on the server subsystem by retrieving the initialization data from a persistent storage; and

coalescing, on the client subsystem, the initialization data stored on the client subsystem with the initialization data from the persistent storage.

2. The method of claim 1, wherein the initialization data from the persistent storage includes information on hardware of the client subsystem.

3. The method of claim 2, wherein the information on the hardware of the client subsystem is retrieved at bootup.

4. The method of claim 1, wherein the initialization data from the persistent storage includes information on a user of the client subsystem.

5. The method of claim 4, wherein the information on the user of the client subsystem is retrieved when the user logs on.

6. The method of claim 1, wherein the second persistent manager object fulfilling the request includes sending the retrieved initialization data from the persistent storage to the first persistent manager object.

10. The method of claim 1, wherein the request is to retrieve the persistent data.

11. The method of claim 10, wherein the second persistent manager object fulfills the request by retrieving the persistent data from a persistent storage and sending the persistent data to the first persistent manager object.

7. A method for managing persistent data in a client/server environment having a client Java system database (JSD) and a server JSD in a system-wide JSD, comprising:

instantiating a first persistent manager object on the client JSD for managing persistent entries on the client JSD, the first persistent manager object being an instance of a persistent manager class in the system-wide JSD thereby enabling saving client entry state information in permanent storage;

the first persistent manager object on the client JSD receiving a request regarding persistent data contained in the system JSD;

first persistent manager object sending the request to a second persistent manager object on the server JSD, the second persistent manager object being an instance of the persistent manager class; and

the second persistent manager object fulfilling the request on the server JSD.

8. The method of claim 7, wherein the request is to store the persistent data.

9. The method of claim 8, wherein the second persistent manager object fulfills the request by storing the persistent data in a persistent storage.

12. The method of claim 7, further comprising instantiating the second persistent manager object on the server JSD.

13. The method of claim 7, wherein the first and second persistent manager objects serialize persistent data into a binary representation so that the persistent data may be transferred between the client JSD and the server JSD.

14. The method of claim 7, wherein the first and second persistent manager objects notify the other if there is a change to the persistent data.

15. The method of claim 7, wherein the client JSD does not have non-volatile storage for writing.

16. A computer program product for managing persistent data in a client/server environment having a client Java system database (JSD) and a server JSD in a system-wide JSD, comprising:

computer code that instantiated a first persistent manager object on the client JSD for managing persistent entries on the client JSD, the first persistent manager object being an instance of a persistent manager class;

computer code of the first persistent manager object on the client JSD that receives a request regarding persistent data contained in the system JSD;

computer code of the first persistent manager object that sends the request to a second persistent manager object on the server JSD, the second persistent manager object being an instance of the persistent manager class; and

a computer readable medium that stores the computer codes.

17. The computer product of claim 16, wherein the computer readable medium is selected from the group consisting of CD-ROM, floppy disk, tape, flash memory, system memory, hard drive, and data signal embodied in a carrier wave.

18. A computer program product for initializing a client subsystem, comprising:

computer code that instantiates a first persistent manager object on a client subsystem, the first persistent manager object being an instance of a persistent manager class;

computer code of the first persistent manager object on the client subsystem that sends a request for initialization data to a second persistent manager object on a server subsystem, the second persistent manager object being an instance of the persistent manager class;

computer code of the first persistent manager object that receives the initialization data from the second persistent manager object;

computer code that coalesces, on the client subsystem, initialization data stored on the client subsystem with the received initialization data from the second persistent manager object; and

a computer readable medium that stores the computer codes.

19. The computer program of claim 18, wherein the computer readable medium is selected from the group consisting of CD-ROM, floppy disk, tape, flash memory, system memory, hard drive, and data signal embodied in a carrier wave.