Adapter framework for line-of-business application integration

• US 20050228803A1
• Filed: 07/30/2004
• Published: 10/13/2005
• Est. Priority Date: 04/02/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Farmer, Donald, Hathi, Kamal
• Application Number:
  US10/909,025
• Publication Number:
  US 20050228803A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The present invention provides a framework to facilitate interoperability and interactions with a plurality of line-of-business (LOB) applications. In particular, maps are populated with application or system design information such as semantic and technical data. The maps are subsequently employed by the framework to enable users to interact with common and consistent semantic terminologies over a common and consistent implementation technology. Consequently, users and/or client data applications are able interact effortlessly with semantically meaningful data from a plurality of heterogeneous LOB sources.

Claims

1. A data access system for accessing data from a line-of-business system comprising:

a data model system to provide a pre-made data model to a user, the pre-made data model modeling the line-of-business system into common business semantics;

a map generation system to generate a map that aliases source metadata to common business semantics according to the pre-made data model; and

a data exaction system that utilizes the map to extract data from the line-of-business system.

2. The system of claim 1, wherein the map comprises both semantic and technical mappings.

3. The system of claim 1, wherein the data model is presented to a user in a data source view.

4. The system of claim 1, wherein the map is an XSLT document.

5. The system of claim 1, wherein the map generation system includes;

a data model library to store data models and mapping information;

a data model access component to retrieve data from the library; and

a map builder component to generate the map at least in part from information retrieved from the library.

6. The system of claim 5, wherein the data model access component is implemented as a web service.

7. The system of claim 5, wherein the map builder component is implemented as a user interface to allow the user to customize the pre-made data model.

8. The system of claim 7, wherein the interface is a map component wizard.

9. The system of claim 5, wherein generated maps can be saved to the data model library for search and retrieval.

10. The system of claim 1, wherein the data extraction system comprises:

a data provider component; and

a connection cartridge component, wherein the data provider component extracts data from the line-of-business system utilizing the connection cartridge component.

11. The system of claim 10, wherein a map component identifies the appropriate connection cartridge component based on the data to be retrieved and the source.

12. The system of claim 10, wherein the connection cartridge component connects to line-of-business APIs and/or schemas and passes mappings to them in a form of queries defined by client applications.

13. A line-of-business data integration and interaction system comprising:

a data model component to provide a pre-built data model to a user, the pre-built data model modeling a data schema into common business semantics;

a map component that aliases non-descriptive source data to the common business semantics according to the pre-built data model and provides technical information to enable interaction with one or more line-of-business applications; and

an extraction system that utilizes information provided by the map component to connect to the one or more applications and retrieve data in response to client application queries.

14. The system of claim 13, wherein the map component is employed to facilitate customization of the pre-built data model.

15. The system of claim 13, wherein the extraction system utilizes map component information to identify and employ a connection cartridge component associated with the client application to retrieve data.

16. The system of claim 13, wherein the map component employs a data source view.

17. A computer readable medium having stored thereon computer executable components of claim 13.

18. A system for interacting with line-of-business data comprising:

a means for providing a pre-made data model to a user, the pre-made data model modeling the line-of-business data into common business semantics;

a means for providing a mapping between complex source metadata and common business semantics according to the pre-made data model; and

a means for exposing line of business source data to client applications utilizing the mapping.

19. The system of claim 18, further comprising a means for system integrators to publish data models.

20. The system of claim 18, wherein the mapping is utilized to codify system integrator deployments.

21. The system of claim 18, further comprising a means for mapping disparate line-of-business technologies to a single execution platform.

22. A method for accessing data organized in a schema comprising:

providing a pre-built data model to a user, the pre-built data model modeling the schema into business domain terms;

generating a map component to map esoteric source metadata to business domain terms according to the pre-built data model; and

extracting data from a line-of-business source utilizing the map component and a connection cartridge component identified thereby.

23. The method of claim 22, wherein the pre-built data model is customized by the user employing an interactive wizard.

24. The method of claim 22, wherein the map component maps data to a single common technical platform.

25. The method of claim 22, wherein the map component is an XSLT document.

26. The method of claim 22, wherein the map component is a data source view.

27. The method of claim 22, wherein the pre-built data model is provided by a data model access service.

28. The method of claim 27, wherein the data model access service is a web service that accesses a library of published line-of-business data models.

29. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 22.

30. An enterprise data access methodology comprising:

providing a pre-made data model to a user, the pre-made data model modeling a schema of the enterprise data into common business terms;

receiving a request for data from an enterprise resource data client;

accessing a data map in response to the request, the data map generated in accordance with the pre-made data model; and

extracting data from at least one heterogeneous data source in accordance with the data map, the map exposing data to a client by aliasing obscure source metadata to common business terms.

31. The method of claim 30;

where data map includes a protocol-mapping portion that identifies a connection cartridge that can be utilized to interface with a source SDK and/or API to retrieve data.

32. The method of claim 30, wherein the request is received from the data client via a data provider.

33. The method of claim 32, wherein the data provider is ADO.NET.

34. The method of claim 30, wherein the mapping component includes data model objects from more than one line-of-business data model.

35. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 30.

36. An enterprise data access methodology comprising:

providing pre-defined line-of-business application data models to a user, the pre-defined line-of-business application data models mapping a schema of the enterprise data according to common business terms;

presenting mapped schema to a data provider component, the mapped schema aliasing complex application metadata to common business semantics in accordance with the pre-defined line-of-business application data models;

receiving a query from a client via the data provider component;

utilizing information provided by a map component to determine data access protocols; and

retrieving data from at least one enterprise source.

37. The method of claim 36, further comprising returning results to the client via the data provider component.

38. The method of claim 36, wherein the mapping component is defined utilizing a wizard.

39. The method of claim 38, wherein the wizard exposes predefined line-of-business application data models to users and enables them to select amongst objects associated with each respective model to include in the mapping component, the mapping component defining a customized pre-defined line-of-business application data model.

40. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 36.