System and method for transmitting and retrieving data via a distributed persistence framework

• US 20020032775A1
• Filed: 08/28/2001
• Published: 03/14/2002
• Est. Priority Date: 08/28/2000
• Status: Abandoned Application

• Current Assignee: Michael D. Harold, Ramesh Venkataramaiah
• Original Assignee: Michael D. Harold, Ramesh Venkataramaiah
• Inventors: Harold, Michael D., Venkataramaiah, Ramesh
• Application Number:
  US09/939,610
• Publication Number:
  US 20020032775A1
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers

Abstract

A method, system and apparatus allowing data processing among multiple physical locations using Lightweight Directory Access Protocol-enabled databases, effectively transforming multiple directory servers into a single logical database. The method, system and apparatus creates a dynamic, distributed database environment for processing complex data types, including data schemas, data documents and software objects. The distributed database environment is accessed either locally or remotely using a simple set of application programming interfaces, which include insert, update, delete and query capabilities. The persistence service supports commit and rollback protocols in a distributed transaction environment.

Claims

1. In a distributed computer network, a method for processing data stored in multiple locations within said network, said network including at least one directory server and at least one persistence framework service manager, and said data including at least one of data schemas, data documents and software objects, said method comprising the steps of:

dissecting, by said at least one persistence framework service manager within said network, a request for a persistence service from a user, said request including at least two request portions therein;

transmitting, by said at least one persistence framework service manager, said at least two request portions to at least two respective directory servers within said network, said directory servers each respectively storing data therein;

receiving, by said persistence framework service manager, data from said at least two respective directory servers pursuant to said at least two request portions;

transmitting, by said persistence framework service manager, the data from said at least two respective directory servers.

2. The method according to claim 1, wherein said persistence service is selected from the group consisting of storing, retrieving, modifying, updating and querying said data.

3. The method according to claim 1, wherein said at least two directory servers each comprise a Lightweight Directory Access Protocol-enabled database.

4. The method according to claim 1, wherein said distributed network is the Internet.

5. The method according to claim 1, further comprising the step of uniquely identifying stored data by using a global, network-wide naming convention.

6. The method according to claim 1, further comprising the step of using user-defined meta-data to store and retrieve data on said at least two directory servers.

7. The method according to claim 1, further comprising the step of describing said data in a complex hierarchical schema, the elements of said complex hierarchical schema being stored on said at least two directory servers.

8. The method according to claim 1, further comprising the step of processing said data and respective states of said data in binary form.

9. The method according to claim 1, further comprising the step of processing software objects with their respective states in at least one Lightweight Directory Access Protocol-enabled database.

10. The method according to claim 1, wherein software objects within said directory servers comprise system level services or complex business objects.

11. The method according to claim 1, wherein software objects are stored within said at least two directory servers as a collection of software objects.

12. The method according to claim 1, wherein each element of said software objects is stored on respective directory servers.

13. The method according to claim 12, wherein said at least two directory servers are Lightweight Directory Access Protocol-enabled databases.

14. The method according to claim 12, wherein the physical storage location of the elements of a given software object on said at least two directory servers is subject to change.

15. The method according to claim 10, wherein all of the elements of a complex business object take part in a commit/rollback protocol in which either all of the elements are changed as part of the unit of work or none of the elements are changed.

16. In a distributed computer network, a system for processing data stored in multiple locations within said network, said network including at least one directory server and at least one persistence framework service manager, and said data including at least one of data schemas, data documents and software objects, said system comprising:

a user device for generating requests for a persistence service;

a persistence framework service manager for processing persistence service requests, a given persistence service request including at lease two request portions therein;

at least two directory servers, said at least two directory servers each respectively storing data therein, said at least two directory servers forwarding data to said persistence framework service manager pursuant to said at least two request portions; and

processor means for receiving said requests for said persistence service, accessing said data from said at least two directory servers and transmitting data to the user.

17. In a distributed computer network, a persistence framework service manager comprising:

dissecting means for dissecting a request for a persistence service from a user, said request including at least two request portions therein;

first transmitting means for transmitting said at least two request portions to at least two respective directory servers within said network, said directory servers each respectively storing data therein;

receiving means for receiving data from said at least two respective directory servers pursuant to said at least two request portions; and

second transmitting means for transmitting the data from said at least two respective directory servers.