Enterprise Directory Service via API Wrapper
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing directory service technologies do not adequately address the unique needs of software applications within business enterprises for real-time or periodic directory information queries, despite advancements in user query systems and privacy protection.
Innovation Solution
An enterprise directory service system comprising a data store with directory entries, a web server with an API coupled to the data store, and a wrapper that accepts queries from user applications, facilitating efficient query processing and response delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If existing directory service technologies are used, then user query functionality is provided, but software applications cannot efficiently access directory information in real-time or periodically
Solution Approach 1:
The patent introduces a directory service system that acts as an intermediary between software applications and directory data. The system includes a directory server that receives queries from applications, processes them against the directory information tree, and returns results. This mediator enables applications to access directory information efficiently without direct coupling to the directory structure.
Solution Approach 2:
The patent segments the directory service into distinct functional components: a directory server for processing queries, a directory information tree for data organization, and application programming interfaces for client access. This segmentation allows independent optimization of each component and enables real-time query processing without affecting the entire system.
2Ease of operation
If directory service is provided to user applications, then directory lookup functionality is achieved, but changes in data store structures affect user applications
Solution Approach 1:
The directory server acts as a stable intermediary layer between applications and the directory information tree. When the data store structure changes, only the directory server needs to be updated to handle new structures, while applications continue to use the same interfaces. This mediator absorbs structural changes and maintains application compatibility.
Solution Approach 2:
The system provides universal access to directory information through standardized programming interfaces that work with different data store structures. The directory server implements multiple access methods and protocols, allowing applications to query the directory without being tied to specific data store implementations or structural changes.
3Measurement precision
If strict name spelling is required for directory lookup, then accurate matching is achieved, but user convenience and flexibility are reduced
Solution Approach 1:
The directory server implements partial matching capabilities that go beyond exact spelling requirements. It can perform substring searches, prefix matches, and fuzzy matching to retrieve directory entries that partially match the query string. This partial action approach maintains accuracy for exact matches while providing flexibility for approximate matches.
Solution Approach 2:
The system allows dynamic adjustment of matching parameters such as case sensitivity, wildcard usage, and similarity thresholds. The directory server can switch between strict exact-matching mode and flexible partial-matching mode based on query requirements, enabling both high precision and user convenience as needed.
Data Source
AI summary
An apparatus and method provides directory service to software applications throughout an enterprise. Directory entries are kept in a data store. A web server having one or more API's is coupled to the data store. The web server may have an API locator for selecting an appropriate API. An enterprise software application such as a purchasing or accounts payable transaction requests directory information by sending a query to an appropriate wrapper based on the programming language, protocol or format of the application. The wrapper sends the request to the appropriate API which then sends a request to the data store. A directory entry is received and returned to the enterprise.