Using AMQP for replication

• US 8,768,886 B2
• Filed: 10/29/2012
• Issued: 07/01/2014
• Est. Priority Date: 06/14/2010
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Megginson, Richard Allen
• Primary Examiner(s): Ehichioya, Fred I
• Assistant Examiner(s): OWYANG, MICHELLE N
• Application Number:
  US13/662,806
• Publication Number:
  US 20130054525A1
• Time in Patent Office: 610 Days
• Field of Search: 707609-610, 707620-623, 707734-765, 707/640, 707/661, 707/672, 707/705, 707/790, 707/802, 709201-253
• US Class Current: 707/622
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

A first directory server computer system subscribes to update data published by directory servers via an advanced message queuing protocol (AMQP) server. The first directory server receives update data that indicates an update for a LDAP-based database associated with the first directory server. When the received update data is from the AMQP server, the first directory server converts the received update data into an LDAP data format and updates the LDAP-based database using the LDAP formatted update data. When the received update data is not from the AMQP server, the first directory server updates the LDAP-based database using the received update data, converts the received update data into a wire level data format, and publishes the wire level formatted update data to the AMQP server. The AMQP server allows a second directory server that subscribes to the AMQP server to obtain data representing the update.

Claims

1. A method comprising:

subscribing to update data published by a plurality of directory servers via an advanced message queuing protocol (AMQP) server, the update data indicating changes made to lightweight directory access protocol (LDAP)-based databases managed by the directory servers;

receiving update data, by a processor of a first directory server, the received update data indicating an update for a LDAP-based database associated with the first directory server;

when the received update data is from the AMQP server, converting, by the processor, the received update data into an LDAP data format and updating the LDAP-based database associated with the first directory server using the LDAP formatted update data; and

when the received update data is not from the AMQP server, updating, by the processor, the LDAP-based database associated with the first directory server using the received update data, converting the received update data into a wire level data format, and publishing the wire level formatted update data to the AMQP server, wherein the AMQP server allows a second directory server that subscribes to the AMQP server to obtain data representing the update.

2. The method of claim 1, wherein the first directory server and second directory server are LDAP-based directory servers.

3. The method of claim 1, further comprising:

examining an Internet Protocol (IP) address corresponding to the received update data to determine whether the received update data is from the AMQP server.

4. The method of claim 1, wherein converting the received update data into the wire level data format comprises:

converting the received update data into at least one of a Qpid™

data format, a directory services markup language (DSML) format, or an LDAP data interchange format (LDIF).

5. The method of claim 1, wherein publishing the received update data to the AMQP server comprises:

associating the received update data with a list stored on the first directory server; and

sending the wire level formatted update data to an exchange, hosted by the AMQP server, that corresponds to the list.

6. The method of claim 1, further comprising:

storing the received update data with an indicator that the received update data is from the AMQP server when the received update data is from the AMQP server.

7. The method of claim 1, further comprising:

maintaining a replication agreement with a legacy directory server; and

sending the LDAP formatted update data to the legacy server when the received update data is from the AMQP server.

8. A system comprising:

a memory to store a lightweight directory access protocol (LDAP)-based database associated with a first directory server computer system; and

a processor of the first directory server computer system is coupled to the memory and is configured to;

subscribe to update data published by a plurality of directory servers via an advanced message queuing protocol (AMQP) server, the update data indicating changes made to LDAP-based databases managed by the directory servers;

receive update data indicating an update to be made to the LDAP-based database associated with the first directory server computer system;

when the received update data is from the AMQP server, convert the received update data into an LDAP data format and update the LDAP-based database associated with the first directory server computer system using the LDAP formatted update data; and

when the received update data is not from the AMQP server, update the LDAP-based database associated with the first directory server computer system using the received update data, convert the received update data into a wire level data format, and publish the wire level formatted update data to the AMQP server, wherein the AMQP server allows a second directory server computer system that subscribes to the AMQP server to obtain data representing the update.

9. The system of claim 8, wherein the first directory server computer system and the second directory server computer system are LDAP-based directory server computer systems.

10. The system of claim 8, wherein the processor is further configured to:

examine an Internet Protocol (IP) address corresponding to the received update data to determine whether the update data is received from the AMQP server.

11. The system of claim 8, wherein converting the received update data into the wire level data format comprises:

converting the received update data into at least one of a Qpid™

data format, a directory services markup language (DSML) format, or an LDAP data interchange format (LDIF).

12. The system of claim 8, wherein publishing the received update data to the AMQP exchange comprises:

storing a list, that is associated with an exchange hosted on the AMQP server, in the persistent storage unit;

associating the received update data with the list; and

sending the wire level formatted update data to the exchange corresponding to the list.

13. The system of claim 8, wherein the memory is further to store a log for managing updates made to the LDAP-based database and wherein the processor is further to add the received update data to the log with an indicator that the received update data is from the AMQP server when the received update data is from the AMQP server.

14. The system of claim 8, wherein the processor is further configured to:

maintain a replication agreement with a legacy directory server; and

send the LDAP formatted update data to the legacy server when the received update data is from the AMQP server.

15. A non-transitory computer-readable medium including instructions that, when executed by a processor of a first directory server, cause the processor to perform operations comprising:

subscribing to update data published by a plurality of directory servers via an advanced message queuing protocol (AMQP) server, the update data indicating changes made to lightweight directory access protocol (LDAP)-based databases managed by the directory servers;

receiving update data, by the processor of the first directory server, the received update data indicating an update for a LDAP-based database associated with the first directory server;

when the received update data is from the AMQP server, converting, by the processor, the received update data into an LDAP data format and updating the LDAP-based database associated with the first directory server using the LDAP formatted update data; and

when the received update data is not from the AMQP server, updating, by the processor, the LDAP-based database associated with the first directory server using the received update data, converting the received update data into a wire level data format, and publishing the wire level formatted update data to the AMQP server, wherein the AMQP server allows a second directory server that subscribes to the AMQP server to obtain data representing the update.

16. The non-transitory computer-readable medium of claim 15, wherein the first directory server and second directory server are LDAP-based directory servers.

17. The non-transitory computer-readable medium of claim 15, the operations further comprising:

examining an Internet Protocol (IP) address corresponding to the received update data to determine whether the received update data is from the AMQP server.

18. The non-transitory computer-readable medium of claim 15, wherein converting the received update data into the wire level data format comprises:

converting the received update data into at least one of a Qpid™

data format, a directory services markup language (DSML) format, or an LDAP data interchange format (LDIF).

19. The non-transitory computer-readable medium of claim 15, the operations further comprising:

storing the received update data with an indicator that the received update data is from the AMQP server when the received update data is from the AMQP server.

20. The non-transitory computer-readable storage medium of claim 15, the operations further comprising:

maintaining a replication agreement with a legacy directory server; and

sending the LDAP formatted update data to the legacy server when the received update data is from the AMQP server.