Interaction between a client process and software applications

• US 20040054640A1
• Filed: 09/12/2002
• Published: 03/18/2004
• Est. Priority Date: 09/12/2002
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Weigt, Matthias, Reichel, Uwe, Tatzel, Steffen
• Application Number:
  US10/242,683
• Publication Number:
  US 20040054640A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A generic interaction layer is an interface between a client device and APIs associated with accessible applications. The generic interaction layer allows the client to access each of the APIs in a generic and consistent way, without having to know the details of those APIs or the underlying data structure of the associated applications. The generic layer maintains models of the data structures of the associated applications and allows a user interface to access the models to determine the location, within a data structure, of data for which the user interface is searching. Using the model, the generic interaction layer prepares a data container in response to a request from the user interface and transmits the container to component modules associated with the specific application(s).

Claims

1. A method comprising

enabling a client to access data in applications using

a command that is defined independently of the applications in which the data are accessed,

a model representing a data structure of the applications;

and

a data container that conforms with the model and accords with the command.

2. The method of claim 1 wherein the command is associated with data handling.

3. The method of claim 1 wherein the command is associated with a query.

4. The method of claim 1 wherein the command is associated with a method defined by a data unit.

5. The method of claim 1 wherein the command is associated with management of a requested transaction.

6. The method of claim 1 wherein the command comprises one of read, modify, create, delete, get_query_result, exec_method, init, lock, save, rollback, and commit.

7. The method of claim 1 wherein the model comprises an XML file.

8. The method of claim 1 wherein the model comprises a table.

9. The method of claim 1 further comprising:

requesting data needed to populate portions of the data container from the applications; and

receiving from the applications data responsive to the request.

10. The method of claim 9 further comprising responding to the command using the data received from the applications.

11. The method of claim 9 wherein requesting further comprises determining API commands to interact with the applications.

12. The method of claim 1 further comprising generating the model by defining a data type for a first data unit of the data structure and defining a relationship between the first data unit and a second data unit.

13. The method of claim 12 wherein the data type comprises a root data unit, an access data unit, a dependent data unit, or a query data unit.

14. The method of claim 12 wherein the relationship comprises an aggregation, a composition, or an association.

15. The method of claim 12 wherein the first data unit comprises an object.

16. The method of claim 12 wherein the second data unit comprises an object.

17. The method of claim 12 wherein the relationship is uni-directional.

18. An interface layer comprising:

an interface layer module configured to receive a request from a client;

an application model module in communication with the interface layer module, the application model module having a first model portion corresponding to a first application and second model portion corresponding to a second application;

a first component module in communication with the interface layer module, the first component module corresponding to the first application; and

a second component module in communication with the interface layer module, the second component module corresponding to the second application.

19. The interface layer of claim 18 further comprising a data container module in communication with the interface layer module, the data container module configured to generate a data container in compliance with the first and second model portions.

20. The interface layer of claim 18 wherein the first model portion comprises an XML file.

21. The interface layer of claim 18 wherein the first model portion comprises a table.

22. The interface layer of claim 18 wherein the first and second component modules are each further configured to determine an API command to interact with its corresponding application.

23. The interface layer of claim 18 wherein the first model portion comprises a first data unit having a data type and a defined association with a second data unit.

24. The interface layer of claim 23 wherein the data type comprises a root data unit, an access data unit, a dependent data unit, or a query data unit.

25. The interface layer of claim 23 wherein the association comprises a uni-directional relationship.

26. The interface layer of claim 23 wherein the association comprises a composition relationship, an aggregation relationship, or an association relationship.

27. The interface layer of claim 23 wherein the first data unit represents an object.

28. The interface layer of claim 23 wherein the second data unit represents an object.

29. A model comprising:

a first data unit including a type;

a second data unit including a type; and

a relationship between the first data unit and the second data unit, the relationship including a unique name, a first cardinality value for the first data unit and a second cardinality value for the second data unit.

30. The model of claim 29 wherein the data type comprises a root data unit, an access data unit, a dependent data unit, or a query data unit.

31. The model of claim 29 wherein the relationship comprises an aggregation, a composition, or an association.

32. The model of claim 29 wherein the first data unit comprises an object.

33. The model of claim 29 wherein the second data unit comprises an object.

34. The model of claim 29 wherein the relationship is uni-directional.

35. An article comprising a machine-readable medium that stores executable instruction signals that cause a machine to

enable a client to access data in two applications using

a command that is defined independently of the two applications in which the data is accessed,

a model representing a data structure of the applications in which the data is accessed;

and

a data container that complies with the model and accords with the command.