Method and system for object replication in a content management system

• US 7,054,887 B2
• Filed: 11/09/2001
• Issued: 05/30/2006
• Est. Priority Date: 01/30/2001
• Status: Expired due to Term

• Current Assignee: X Corp. (f/k/a Twitter, Inc.) (X Holdings Corp.)
• Original Assignee: International Business Machines Corporation
• Inventors: Kozina, Gerald Edward
• Primary Examiner(s): Wassum, Luke S
• Assistant Examiner(s): Black, Linh
• Application Number:
  US10/011,181
• Publication Number:
  US 20020174200A1
• Time in Patent Office: 1,663 Days
• Field of Search: 707 1-1041, 707200-204
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• 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

A system and method in accordance with the present invention provides for replication in a content management system. Replication is provided by utilizing the library server to track the objects to be replicated within the system. The replication is accomplished by adding two tables to the library server, a copies table and replicate table. The copies tables includes three new parts flags. A first flag identifies an ending as a copied part. A second flag identifies that other copies of this part exist. Finally a third flag identifies that a part is not yet available.

Claims

1. A method for replicating an object, in a content management system, wherein the content management system comprises at least one target object server, at least one source object server and a library server;

the method comprising the steps of;

(a) receiving a request for an object to be replicated by the at least one source object server by the at least one target object server;

(b) committing the replica by the at least one the source object server; and

(c) authorizing the replication by the library server after steps (a) and (b) wherein a three valued logic is utilized for replication of an object, wherein the three valued logic comprises (1) part does not exist, (2) part will exist and (3) part exists.

2. The method of claim 1 wherein the at least one object server includes a replicate table.

3. The method of claim 2 wherein the library server searches for replicas in the replicate table.

4. The method of claim 3 wherein the replication table includes an object server name and a collection name.

5. The method of claim 4 wherein the library server obtains the object server name and collection name tuple from the replication table for replicas.

6. The method of claim 1 wherein the library server includes a copies table and a replication table.

7. The method of claim 6 wherein the copies table includes a first flag that identifies an entry as a copied part, a second flag that identifies that other copies of a part exist and a third flag that identifies that a copy of the part is not available.

8. The method of claim 7 wherein a plurality of actions are defined by a replicate type.

9. A computer readable medium containing program instructions for replicating an object in a content management system, wherein the content management system comprises at least one target object server, at least one source object server and a library server;

the program instructions for;

(a) receiving a request for an object to be replicated by the at least one source object server by the at least one target object server;

(b) committing the replica by the at least one the source object server; and

(c) authorizing the replication by the library server after steps (a) and (b) wherein a three valued logic is utilized for replication of an object, wherein the three valued logic comprises (1) part does not exist, (2) part will exist and (3) part exists.

10. The computer readable medium of claim 9 wherein the at least one object server includes a replicate table.

11. The computer readable medium of claim 10 wherein the library server searches for replicas in the replicate table.

12. The computer readable medium of claim 11 wherein the replication table includes an object server name and a collection name.

13. The computer readable medium of claim 12 wherein the library server obtains the object server name and collection name tuple from the replication table for replicas.

14. The computer readable medium of claim 9 wherein the library server includes a copies table and a replication table.

15. The computer readable medium of claim 14 wherein the copies table includes a first flag that identifies an entry as a copied part, a second flag that identifies that other copies of a part exist and a third flag that identifies that a copy of the part is not available.

16. The computer readable medium of claim 15 wherein a plurality of actions are defined by a replicate type.

17. A content management system comprising:

a client;

a library server for communicating with the client, wherein the library server tracks objects to be replicated in the system; and

at least one object server for communicating with the client and the library server, wherein a two phase commit protocol is utilized for an operation, wherein a three valued logic is utilized for replication of an object, wherein the three valued logic comprises (1) part does not exist, (2) part will exist and (3) part exists.

18. The content management system of claim 17 wherein the library server obtains the object server name and collection name tuple from the replication table for replicas.

19. The content management system of claim 17 wherein the copies table includes a first flag that identifies an entry as a copied part, a second flag that identifies that other copies of a part exist and a third flag that identifies that a copy of the part is not available.

20. The content management system of claim 19 wherein a plurality of actions are defined by a replicate type.