| Disparate data store services catalogued for unified access -> Monitor Keywords |
|
|
 
Disparate data store services catalogued for unified accessRelated Patent Categories: Data Processing: Database And File Management Or Data Structures, Database Or File AccessingDisparate data store services catalogued for unified access description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20060294042, Disparate data store services catalogued for unified access. Brief Patent Description - Full Patent Description - Patent Application Claims
PRIORITY CLAIM [0001] This application is a Continuation-In-Part under 35 U.S.C. .sctn.120 of U.S. patent application Ser. No. 11/165,748 filed on Jun. 23, 2005, which is incorporated by reference herein in its entirety. TECHNICAL FIELD [0002] The disclosed technology relates generally to data processing and, more particularly, to enabling clients to discover and interact with one or more entities in one or more registered data store services in a number of ways using one or more uniform access interfaces. BACKGROUND [0003] Organizations may often use or desire using line-of-business ("LOB") systems to carry out daily operations, for example. Further, many organizations may implement a number of different types of LOB systems to perform particular tasks, such as SAP, SIEBLE and other types of LOB systems. While these LOB systems may potentially offer a great deal of benefits, at the same time organizations may find themselves unexpectedly devoting other resources just to be able to utilize these systems. [0004] For instance, an organization's developer(s) may need to familiarize themselves with the semantics for interacting with each type of different LOB system. While SAP and SIEBLE were mentioned above as examples of LOB systems, any one organization may desire employing other types of LOB systems. Moreover, organizations may desire utilizing several instantiations of a particular LOB system (e.g., SAP) each dedicated to handling particular business related operations in addition to those other types of systems mentioned above. As a result, still more of an organization's resources would need to be invested to be able to leverage those systems. SUMMARY [0005] The following presents a simplified summary of the subject matter disclosed in further detail herein to provide a basic understanding to the reader. This summary is not an exhaustive or limiting overview of the disclosed subject matter, and is not provided for identifying key and/or critical elements of the subject matter or delineating the scope of the claimed subject matter. Thus, the scope of the claimed subject matter should not be limited in any way by this summary. Its sole purpose is to present some of the concepts in a simplified form as an introduction to the more detailed description that is presented later. [0006] The present example provides a data store catalogue service model that may be implemented as a data store catalogue service system 56 in the manner described herein with regard to FIGS. 5 and 7. The data store catalogue service model may be implemented to expose one or more disparate data store related services to one or more clients without requiring the clients to have explicit knowledge on how to interact with each or any of the disparate services. The data store catalogue service system 56 may maintain interaction details for the data store related services, which the clients may access for interacting with those services. In particular, the data store catalogue service system 56 may implement a metadata data store 50 that may describe the different types of services available for accessing by clients, the data types used by those services, how to access the data provided by the services, and how to communicate semantically with the services for accessing the service's data. The clients may issue one or more requests to access those particular services defined in the metadata data store via one or more application program interfaces ("APIs") exposed to the clients by a data store service catalogue system in a unified manner. [0007] Many of the attendant features will be more readily appreciated as the same becomes better understood by reference to the following detailed description considered in connection with the accompanying drawings. DESCRIPTION OF THE DRAWINGS [0008] The foregoing summary will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein: [0009] FIG. 1 is a block diagram of at least a portion of a system for registering data store services in cataloguing systems to provide clients with access to disparate data store services in a unified manner; [0010] FIG. 2 is a block diagram of an application server that may be used in the system illustrated in FIG. 1; [0011] FIG. 3 is a block diagram of a computer that may be used in the system illustrated in FIG. 1; [0012] FIG. 4 is a block diagram of a client service access portal application and a data store service catalogue system that may be implemented in the system illustrated in FIG. 1; [0013] FIG. 5 is a diagram of at least a portion of a metadata data store that may be implemented in the data store service catalogue system illustrated in FIG. 4; [0014] FIG. 6 is a functional block diagram illustrating at least a portion of a process for registering data store services in cataloguing systems to provide clients with access to disparate data store services in a unified manner; [0015] FIG. 7 is a flow chart of a process for registering data store services in cataloguing systems to provide clients with access to disparate data store services in a unified manner; [0016] FIG. 8 is a flow chart of a process for enabling clients to discover and interact with one or more entities in one or more registered data store services; and [0017] FIGS. 9-16 are diagrams one or more other portions of a metadata data store that may be implemented in the data store service catalogue system illustrated in FIG. 4 that may be used in accordance with the process for enabling clients to discover and interact with one or more entities in one or more registered data store services. [0018] Like reference numerals are used to designate like parts in the accompanying drawings. DETAILED DESCRIPTION Continue reading about Disparate data store services catalogued for unified access... Full patent description for Disparate data store services catalogued for unified access Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Disparate data store services catalogued for unified access patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Disparate data store services catalogued for unified access or other areas of interest. ### Previous Patent Application: Data centric workflows Next Patent Application: File migration history controls updating or pointers Industry Class: Data processing: database and file management or data structures ### FreshPatents.com Support Thank you for viewing the Disparate data store services catalogued for unified access patent info. IP-related news and info Results in 0.42273 seconds Other interesting Feshpatents.com categories: Qualcomm , Schering-Plough , Schlumberger , Seagate , Siemens , Texas Instruments , 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
