XML-LDAP adapters and methods therefor

• US 20040148305A1
• Filed: 01/29/2003
• Published: 07/29/2004
• Est. Priority Date: 01/29/2003
• Status: Active Grant

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Bollich, Brooks
• Granted Patent: US 7,076,488 B2
• Time in Patent Office: Days
• US Class Current: 707/101
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

An arrangement for transforming data between an XML (extensible markup language) data source and an LDAP (Lightweight Directory Access Protocol) interface is disclosed. The arrangement includes a XML-LDAP adapter for transforming first data into second data. The first data is represented in a first XML format and includes information pertaining to at least a subset of third data. The third data represents an XML-formatted message received from the XML data source. The second data is represented in a LDAP format and pertains to an LDAP operation affecting an LDAP directory that is coupled to receive the second data through the LDAP interface, whereby the LDAP operation is represented by an operation object that implements both a first functionality and a second functionality. The first functionality executes the LDAP operation. The second functionality restores the LDAP directory to a state that existed prior to a commencement of execution of the operation object.

Claims

1. An arrangement for transforming data between an XML (extensible markup language) data source and an LDAP (Lightweight Directory Access Protocol) interface, comprising:

a XML-LDAP adapter for transforming first data into second data, said first data being represented in a first XML format and includes information pertaining to at least a subset of third data, said third data representing an XML-formatted message received from said XML data source, said second data being represented in a LDAP format and pertaining to an LDAP operation affecting an LDAP directory that is coupled to receive said second data through said LDAP interface,

whereby said LDAP operation is represented by an operation object that implements both a first functionality and a second functionality, said first functionality executing said LDAP operation, said second functionality restoring said LDAP directory to a state that existed prior to a commencement of execution of said operation object.

2. The arrangement of claim 1 wherein said XML data source represents an LDAP directory front-end program.

3. The arrangement of claim 2 wherein said LDAP directory front-end program represents a customer relationship management (CRM) program.

4. The arrangement of claim 1 wherein said operation object represents one of an add entry object, a remove entry object, and a modify entry object.

5. The arrangement of claim 4 wherein said first functionality represents an add entry functionality and said second functionality represents a remove entry functionality.

6. The arrangement of claim 4 wherein said first functionality represents a remove entry functionality and said second functionality represents an add entry functionality.

7. The arrangement of claim 4 wherein said first functionality represents a first modify entry functionality configured to modify an entry in said LDAP directory from a first state to a second state, said second functionality represents a second modify entry functionality configured to modify said entry from said second state back to said first state.

8. The arrangement of claim 4 wherein said operation object is configured to store state data associated with said LDAP operation, said state data representing data to enable said second functionality to accomplish said restoring said LDAP directory to said state that existed prior to said commencement of execution of said operation object

9. The arrangement of claim 4 further comprising an activation engine for transforming said third data into fourth data, said fourth data having a second XML format different from said first XML format.

10. The arrangement of claim 9 wherein said transforming said third data into said fourth data employs XSLT technology.

11. The arrangement of claim 9 further comprising a transaction engine for decomposing said fourth data into a plurality of messages, each of said plurality of messages being associated with an LDAP atomic operation, one of said plurality of messages being represented by said first data.

12. A method for transforming data between an XML (extensible markup language) data source and an LDAP (Lightweight Directory Access Protocol) interface, comprising:

receiving first data, said first data pertaining at least to a subset of first information received from said XML data source;

creating an operation object using said first data; and

transforming information associated in said operation object into second data, said second data having an LDAP format and pertaining to an LDAP operation that affects an LDAP directory coupled to receive said second data through said LDAP interface, whereby said operation object implementing both a first functionality and a second functionality, said first functionality executing said LDAP operation, said second functionality restoring said LDAP directory to a state that existed prior to a commencement of execution of said operation object.

13. The method of claim 12 further comprising storing state data associated with said LDAP operation in said operation object prior to executing said LDAP operation, said state data representing data to enable said second functionality to accomplish said restoring said LDAP directory to said state that existed prior to said commencement of execution of said operation object.

14. The method of claim 13 wherein said operation object represents one of an add entry object, a remove entry object, and a modify entry object.

15. The method of claim 13 wherein said first functionality represents an add entry functionality and said second functionality represents a remove entry functionality.

16. The method of claim 13 wherein said first functionality represents a remove entry functionality and said second functionality represents an add entry functionality.

17. The method of claim 13 wherein said first functionality represents a first modify entry functionality configured to modify an entry in said LDAP directory from a first state to a second state, said second functionality represents a second modify entry functionality configured to modify said entry from said second state back to said first state.

18. The method of claim 12 further comprising:

providing a transaction engine;

receiving third data at said transaction engine, said third data pertaining to said first information, said third data having a first XML format that is different from a second XML format associated with said first information; and

decomposing said third data into a plurality of messages, each of said plurality of messages being associated with an LDAP atomic operation, one of said plurality of messages being said first data.

19. The method of claim 18 further comprising:

providing an activation engine; and

receiving said first information at said first activation engine, said activation engine being configured to transform said first information having said second XML format into said third data having said first XML format.

20. The arrangement of claim 12 wherein said XML data source represents a customer relationship management (CRM) program.

21. An arrangement for transforming data between an XML (extensible markup language) data source and an LDAP (Lightweight Directory Access Protocol) interface, comprising:

means for receiving first data from said XML data source, said first data being represented in a first XML format; and

means for transforming first information associated with said first data into second data, said second data being represented in an LDAP format and pertaining to an LDAP operation affecting a LDAP directory that is coupled to receive said second data through said LDAP interface,

whereby said LDAP operation is represented by an operation object that implements both a first functionality and a second functionality, said first functionality executing said LDAP operation, said second functionality restoring said LDAP directory to a state that existed prior to a commencement of execution of said operation object.

22. The arrangement of claim 21 wherein said XML data source represents an LDAP directory front-end program.

23. The arrangement of claim 22 wherein said LDAP directory front-end program represents a customer relationship management (CRM) program.

24. The arrangement of claim 21 wherein said operation object represents one of an add entry object, a remove entry object, and a modify entry object.

25. The arrangement of claim 24 wherein said first functionality represents an add entry functionality and said second functionality represents a remove entry functionality.

26. The arrangement of claim 24 wherein said first functionality represents a remove entry functionality and said second functionality represents an add entry functionality.

27. The arrangement of claim 24 wherein said first functionality represents a first modify entry functionality configured to modify an entry in said LDAP directory from a first state to a second state, said second functionality represents a second modify entry functionality configured to modify said entry from said second state back to said first state.

28. The arrangement of claim 24 wherein said operation object is configured to store state data associated with said LDAP operation, said state data representing data to enable said second functionality to accomplish said restoring said LDAP directory to said state that existed prior to said commencement of execution of said operation object

29. The arrangement of claim 24 further comprising an engine for transforming said first data into third data, said third data having a second XML format different from said first XML format.

30. The arrangement of claim 29 wherein said second XML format is an LDAP-oriented XML format.

31. The arrangement of claim 30 wherein said transforming said first data into said third data employs XSLT technology.

32. The arrangement of claim 30 further comprising means for decomposing said third data into a plurality of messages, each of said plurality of messages being associated with an LDAP atomic operation, one of said plurality of messages being represented by said first information associated with said first data.