Just-in-time wrapper synchronization

• US 9,219,706 B2
• Filed: 09/29/2010
• Issued: 12/22/2015
• Est. Priority Date: 09/29/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hom, Richard V., Nelson, Eric M., North, James C.
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): KRISHNAN, RAJESHWARI
• Application Number:
  US12/893,437
• Publication Number:
  US 20120079077A1
• Time in Patent Office: 1,910 Days
• Field of Search: 709/219, 709/230, 709/231, 709/223, 709201-206, 709225-227, 709/246, 707/694, 707/769, 707/610, 707/740, 707/781, 707/E17.005, 707/E17.014, 706/47, 711/103, 711/133, 711/141, 711/130, 719/320, 726 2- 7, 726/21, 717101-102
• US Class Current: 1/1
• CPC Class Codes: G06F 12/121 using replacement algorithms
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

The invention is directed to just-in-time (JIT) retrieval of directory information to reduce network traffic and load on directory servers and/or data sources by requesting only the information that is currently needed from the directory server. In the invention, a wrapper operating with a directory server and an application programming interface (API) provides this capability. The wrapper is configured to receive a request from a client and to determine a location corresponding to a set of current attribute values for responding to the request. The wrapper retrieves the set of current attribute values in a JIT manner from at least one of the following: the directory server and an external source. A set of current attributes is returned to the client from the wrapper. By propagating information in a JIT manner, only the information that will be currently used is propagated across the network.

Claims

1. A method for just-in-time (JIT) retrieval of directory information, the method comprising:

providing a directory server and a repository, the directory server operating with an application programming interface (API) and a wrapper, wherein the repository is a cache capable of receiving refreshed attributes from an external source, and wherein the external source comprises a lightweight directory application protocol (LDAP) provider;

intercepting, by the wrapper, a request made from a client application intended for the directory server, wherein the wrapper integrates with the repository only when the request is made, and wherein following the making of the request, the client application interfaces with the wrapper instead of the repository;

identifying by the wrapper a set of attribute values of an entry in the repository for responding to the request;

determining by the wrapper, a location corresponding to the set of attribute values for responding to the request, wherein the determining the location comprises;

evaluating whether the set of attribute values have been refreshed in the repository within a first predetermined period of time;

in the case that the set of attribute values have been refreshed in the repository within the first predetermined period of time, determining, based on the evaluation, the repository as the location corresponding to the set of attribute values;

in the case that the set of attribute values in the repository have not been refreshed within the first predetermined period of time, determining whether the external source can satisfy the request, and determining the external source as the location corresponding to the set of attribute values, based on the determination that the external source can satisfy the request;

in the case that the external source is unable to satisfy the request, determining whether the set of attribute values in the repository have been refreshed within a second predetermined period of time, and determining the repository as the location corresponding to the set of attribute values, based on the determination that the set of attribute values in the repository have been refreshed within the second predetermined period of time;

retrieving the set of attributes values from the determined location and responding to the request;

updating the repository by caching the set of attribute values in the repository and associating a refresh date with the set of attribute values as determined by the wrapper, in the case that the set of attribute values is retrieved from the external source.

2. The method according to claim 1, further comprising:

returning the set of attributes to the client from the wrapper;

asynchronously caching the set of attribute values in the repository; and

updating the refresh date for each of the set of attribute values.

3. The method according to claim 1, further comprising preloading the repository.

4. A directory apparatus for just-in-time (JIT) retrieval of directory information, comprising:

a processor; and

a memory storing computer readable instructions, which when executed by the processor, configure the directory apparatus to provide

a directory server,

an application programming interface (API),

a wrapper and

a repository,

wherein the repository is capable of receiving refreshed attributes from an external source, wherein the external source comprises a lightweight directory application protocol (LDAP) provider,

wherein the wrapper is configured to;

intercept a request made from a client application intended for the directory server, wherein the wrapper integrates with the repository only when the request is made, and wherein following the making of the request, the client application interfaces with the wrapper instead of the repository;

identify a set of attribute values of an entry in the repository for responding to the request;

determine a location corresponding to the set of attribute values for responding to the request, wherein the determining the location comprises;

evaluating whether the set of attribute values have been refreshed in the repository within a first predetermined period of time;

in the case that the set of attribute values have been refreshed in the repository within the first predetermined period of time, determining, based on the evaluation, the repository as the location corresponding to the set of attribute values;

in the case that the set of attribute values in the repository have not been refreshed within the first predetermined period of time, determining whether the external source can satisfy the request, and determining the external source as the location corresponding to the set of attribute values, based on the determination that the external source can satisfy the request;

in the case that the external source is unable to satisfy the request, determining whether the set of attribute values in the repository have been refreshed within a second predetermined period of time, and determining the repository as the location corresponding to the set of attribute values, based on the determination that the set of attribute values in the repository have been refreshed within the second predetermined period of time;

retrieve the set of attribute values from the determined location and responding to the request;

update the repository by caching the set of attribute values in the repository and associating a refresh date with the set of attribute values as determined by the wrapper, in the case that the set of attribute values is retrieved from the external source.

5. The directory apparatus according to claim 4, wherein the wrapper is further configured for asynchronously caching the set of attribute values and updating the refresh date for each of the set of attribute values.

6. The directory apparatus according to claim 4, further comprising preloading the repository.

7. A non-transitory computer-readable medium storing computer instructions, which when executed, enables a computer system operating with a directory server, an application programming interface (API), and a wrapper, to provide just-in-time (JIT) retrieval of directory information, the computer instructions comprising:

providing a repository with the directory server, wherein the repository is a cache capable of receiving refreshed attributes from an external source, and wherein the external source comprises a lightweight directory application protocol (LDAP) provider;

intercepting, by the wrapper, a request made from a client application intended for the directory server, wherein the wrapper integrates with the repository only when the request is made, and wherein following the making of the request, the client application interfaces with the wrapper instead of the repository;

identifying, by the wrapper, a set of attribute values of an entry in the repository for responding to the request;

determining, by the wrapper, a location corresponding to the set of attribute values for responding to the request, wherein the determining the location comprises;

evaluating whether the set of attribute values have been refreshed in the repository within a first predetermined period of time;

in the case that the set of attribute values have been refreshed in the repository within the first predetermined period of time, determining, based on the evaluation, the repository as the location corresponding to the set of attribute values;

in the case that the set of attribute values in the repository have not been refreshed within the first predetermined period of time, determining whether the external source can satisfy the request, and determining the external source as the location corresponding to the set of attribute values, based on the determination that the external source can satisfy the request;

in the case that the external source is unable to satisfy the request, determining whether the set of attribute values in the repository have been refreshed within a second predetermined period of time, and determining the repository as the location corresponding to the set of attribute values, based on the determination that the set of attribute values in the repository have been refreshed within the second predetermined period of time;

retrieving the set of attributes values from the determined location and responding to the request;

updating the repository by caching the set of attribute values in the repository and associating a refresh date with the set of attribute values as determined by the wrapper, in the case that the set of attribute values is retrieved from the external source.

8. The non-transitory computer-readable medium according to claim 7, further comprising computer instructions for:

returning the set of attributes to the client from the wrapper;

asynchronously caching the set of attribute values in the repository; and

updating the refresh date for each of the set of attribute values.

9. The non-transitory computer-readable medium according to claim 7, further comprising computer instructions for preloading the repository.

10. A method for deploying a wrapper for use in a computer system to provide just-in-time (JIT) retrieval of directory information, comprising:

providing a computer infrastructure operating with a directory server, an application programming interface (API), a wrapper, and a repository, wherein the repository is a cache capable of receiving refreshed attributes from an external source, and wherein the external source comprises a lightweight directory application protocol (LDAP) provider;

intercepting, by the wrapper, a request made from a client application intended for the directory server, wherein the wrapper integrates with the repository only when the request is made, and wherein following the making of the request, the client application interfaces with the wrapper instead of the repository;

identifying, by the wrapper, a set of attribute values of an entry in the repository for responding to the request;

determining, by the wrapper, a location corresponding to the set of attribute values for responding to the request, wherein the determining the location comprises;

evaluating whether the set of attribute values have been refreshed in the repository within a first predetermined period of time;

in the case that the set of attribute values have been refreshed in the repository within the first predetermined period of time, determining, based on the evaluation, the repository as the location corresponding to the set of attribute values;

in the case that the set of attribute values in the repository have not been refreshed within the first predetermined period of time, determining whether the external source can satisfy the request, and determining the external source as the location corresponding to the set of attribute values, based on the determination that the external source can satisfy the request;

in the case that the external source is unable to satisfy the request, determining whether the set of attribute values in the repository have been refreshed within a second predetermined period of time, and determining the repository as the location corresponding to the set of attribute values, based on the determination that the set of attribute values in the repository have been refreshed within the second predetermined period of time;

retrieving the set of attributes values from the determined location and responding to the request;

updating the repository by caching the set of attribute values in the repository and associating a refresh date with the set of attribute values as determined by the wrapper, in the case that the set of attribute values is retrieved from the external source.

11. The method according to claim 10, the computer infrastructure further operable to asynchronously cache the set of attribute values and update the refresh date for each of the set of attribute values.