Rapid application integration

• US 7,225,425 B2
• Filed: 12/13/2002
• Issued: 05/29/2007
• Est. Priority Date: 08/29/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Foerg, Karl-Heinz, Kompalli, Prasad, Pauly, Heinz
• Primary Examiner(s): Steelman; Mary
• Assistant Examiner(s): DENG, ANNA CHEN
• Application Number:
  US10/318,405
• Publication Number:
  US 20040044987A1
• Time in Patent Office: 1,628 Days
• Field of Search: 717104-109, 717/111, 717/113, 717/121, 717/126, 717/165, 717/166, 719/328, 719/330, 719/319, 719/329, 709/203, 709/204, 709/207, 709/219, 709/224, 709/227, 709/212, 709/213, 709/231, 709/232, 718/101, 715/765
• US Class Current: 717/108
• CPC Class Codes: G06F 8/20 Software design

Abstract

Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software. Such an application integration workstation may reduce the time required to construct or maintain application integration software, which may be referred to as “rapid application integration.”

Claims

1. A computer system for use in the design of application integration software that performs data exchange between at least two application systems, the computer system comprising a processor connected to a storage device and at least one input/output device, wherein the processor is operable to execute:

a design modulate configured to design, based on user input, a declarative integration workflow that includes predefined integration design patterns that collectively describe a data exchange between at least two application systems, wherein;

an integration design pattern identifies integration functions used in the data exchange between at least two application systems,

an integration function identifies a process used in data transfers, and

the at least two application systems each use a database capable of storing data related to business transactions and instructions, that when executed, cause data related to the business transactions to be processed;

a sequencing module configured to specify, based on user input, a sequence for performing the integration design patterns to cause the data exchange; and

a storage module configured to store the declarative integration workflow such that the declarative integration workflow is to be used to generate software codes that, when executed, performs the data exchange.

3. The computer system of claim 1 wherein at least one predefined integration design pattern includes at least one of a pattern for validating a data collection for mandatory information, a pattern for splitting data from one data collection into separate data collections, a pattern for invoking a key mapping function, a pattern for invoking a data transformation function, a pattern for invoking a connectivity function for a particular application system, and a pattern for invoking a connectivity function for invoking a particular service.

4. The computer system of claim 1 wherein the design module is further configured to represent at least one integration design pattern that decomposes into two or more integration design patterns and from which a user may select to be included in the declarative integration workflow.

5. The computer system of claim 1 wherein the design module is further configured to represent at least two application systems between which data is to be exchanged in a declarative integration workflow.

6. The computer system of claim 1 wherein the design module is further configured to represent at least two application services between which data is to be exchanged in a declarative integration workflow.

7. The computer system of claim 6 wherein the design module is further configured to associate an application service with an application system.

8. The computer system of claim 1 wherein the design module is further configured to represent the data to be exchanged between at least two application systems.

9. The computer system of claim 8 wherein the design module is further configured to represent at least one type of data.

10. The computer system of claim 8 wherein the design module is further configured to represent at least one data collection to be exchanged.

11. The computer system of claim 10 wherein the design module is further configured to represent at least one of an object, an object type, an object instance, a database table, a database segment, a database table row, a document capable of being accessed thorough a format that may be transmitted by an Internet Protocol, an XML-document, a text file, a binary file, and a message.

12. The computer system of claim 1 further comprises a generative module configured to generate application integration software based on the declarative integration workflow.

13. The computer system of claim 12 herein the generative module is further configured to generate a template for application integration software.

14. The computer system of claim 12 herein the generative module is further configured to generate source code.

15. The computer system of claim 12 wherein the generative module is further configured to generate executable instructions for a computer.

16. The computer system of claim 12 wherein the generative module is further configured to permit a user to modify the generated application integration software.

17. The computer system of claim 12 wherein the generative module is further configured to associate the generated application integration software with the declarative integration workflow.

18. The computer system of claim 17 wherein the generative module is further configured to associate at least one portion of the generated application integration software with the at least one portion of the declarative integration workflow, each particular portion of the generated application integration software being associated with a particular portion of the declarative integration workflow.

19. The computer system of claim 12 wherein the generative module is further configured to generate application integration software based on a layer of application integration.

20. The computer system of claim 19 wherein the generative module is further configured to generate application integration software based on at least one of a business process layer, an integration design pattern layer, a functional atom layer, a data transformation rule layer, a data layer, and a physical connection layer.

21. The computer system of claim 20 wherein the business process layer identifies at least one application system with which an application integration function is to be performed.

22. The computer system of claim 20 wherein the business process layer identifies at least one service, each service being associated with an identified application system.

23. The computer system of claim 20 wherein the integration design pattern layer specifies at least one declarative design pattern that identifies an integration function used during an application integration function.

24. The computer system of claim 20 wherein the functional atom layer identifies at least one functional atom that declaratively describe an action that relates to an application integration function.

25. The computer system of claim 20 wherein the data transformation rule layer specifies data transformation logic that describes how data is transformed.

26. The computer system of claim 25 wherein the data transformation logic comprises a data transformation rule.

27. The computer system of claim 20 wherein the data layer that specifies data included in an application integration function.

28. The computer system of claim 27 wherein the data included in an application integration function comprises at least one of an object instance, an attribute, an attribute value and control data included in an application integration function.

29. The computer system of claim 20 wherein the physical connection layer comprises a physical connection layer that identifies or includes s physical connection and network that is used to connect two computer systems involved in an application integration function.

2. The computer system of claim wherein the design module is further configured to represent predefined integration patterns from which a user may select to be included in the declarative integration flow.

30. A design workstation and accompanying user interface for use in the design of application integration software that performs data exchange between at least two application systems, the software design work station comprising a processor connected to a storage device and at least one input/output device, wherein the processor is operable to execute:

a design module configured to design, based on user input, a declarative integration workflow that includes predefined integration design patterns that collectively describe a data exchange between at least two application systems, wherein;

an integration design pattern identifies functions used in the data exchange between at least two application systems,

an integration function identifies a process used in data transfers, and

the at least two application systems each use a database capable of storing data related to business transactions and instructions, that when executed, cause data related to the business transactions to be processed;

a sequencing module configured to specify based on user input, a sequence for performing the integration design patters to cause the data exchange; and

a storage module configured to store the declarative integration workflow such that the declarative integration workflow is able to be used to generate software code that, when executed, performs the data exchange.

31. The design workstation of claim 30 wherein the design module is further configured to generate a user interface used to design, a declarative integration workflow.

32. The design workstation of claim 30 wherein at least one predefined integration design pattern includes at least one of a pattern for validating a data collection for mandatory information, a pattern for splitting data from one data collection into separate data collections, a pattern for invoking a key mapping function, a pattern for invoking a data transformation function, a pattern for invoking a connectivity function for a particular application system, and a pattern for invoking a connectivity function for invoking a particular service.

33. The design workstation of claim 30 wherein the design module is further configured to represent at least one integration design pattern that decomposes into at least two integration design patterns and from which a user may select to be included in the declarative integration workflow.

34. A computer-readable storage medium having embodied thereon a computer program configured for use in the design of application integration software that performs data exchange between at least two application systems, the medium comprising:

design code segment configured to design, based on user input, a declarative integration workflow that includes predefined integration design patterns that collectively describe a data exchange between at least two application systems, wherein;

an integration design pattern identifies integration functions used in the data exchange between at least two application systems,

an integration function identities a process used in data transfers, and

the at least two application systems each use a database capable of storing data related to business transactions and instructions, that when executed, cause data related to the business transactions to be processed;

a specifying code segment configured to specify, based on user input, a sequence for performing the integration design patterns to cause the data exchange; and

a storage code segment configured to store the declarative integration workflow such that the declarative integration workflow is able to be used to generate software code that, when executed, performs the data exchange.

35. The computer-readable storage medium of claim 34 wherein the design code segment is further configured to represent at least one integration pattern that describes a function included in a particular data exchange between at least two application systems.

36. The computer-readable storage medium of claim 34 wherein the design code segment is further configured to represent at least one integration design pattern that includes at least one of a pattern for validating a data collection for mandatory information, a pattern for splitting data from one data collection into separate data collections, a pattern for invoking a key mapping function, a design pattern for invoking a data transformation function, a pattern the invoking a connectivity function for a particular application system, and a pattern for invoking a connectivity function for invoking a particular service.

37. The computer-readable medium of claim 34 wherein the design code segment is further configured to represent at least one of an integration design pattern that decomposes into at least two integration design patterns.

38. The computer-readable storage medium or signal of claim 34 further comprising a generative code segment configured to generate application integration software based on the declarative integration workflow.

39. The computer-readable storage medium of claim 38 wherein the generative code segment configured to generate a template for application integration software.

40. The computer-readable storage medium of claim 38 wherein the generative code segment is configured to associate one or more portions of the generated application integration software with one or more portions of the declarative integration workflow, each particular portion of the generated application integration software being associated with a particular portion of the declarative integration workflow.

41. The computer-readable storage medium of claim 38 wherein the generative code segment is further configured to generate application integration software based on at least one layer of application integration.

42. The computer-readable storage medium of claim 41 wherein the generative code segment is further configured to generate application integration software based on at least one of a business process layer, an integration design pattern layer, a functional atom layer, a data transformation rule layer, a data and a physical connection layer.

43. The computer-readable storage medium of claim 42 wherein the functional atom layer comprises a functional atom layer that identifies at least one functional atom that declaratively describes a discrete action that relates to an application integration function.

44. A method for use in the design of application integration software that performs data exchange between at least two application systems comprising:

designing, based on user input, a declarative integration workflow that includes predefined integration design patterns that collectively describe a data exchange between at least two application systems, wherein;

an integration design pattern identifies integration functions used in the data exchange between at least two application systems,

an integration function identifies a process used in data transfers, and

the at least two application systems each use a database capable of storing data related to business transactions and instructions that when executed, cause data related to the business transactions to be processed;

specifying a sequence, based on user input, for performing the integration design patterns to cause the data exchange and

storing the declarative integration workflow such that the declarative integration workflow is able to be used to generate software code that, when executed, performs the data exchange.

45. The method of claim 44 further comprising representing predefined integration patterns from which a user may select to be included in the declarative integration workflow.

46. The method of claim 45 wherein representing at least one integration pattern comprises representing at least one integration design pattern includes at least one of a pattern for validating a data collection for mandatory information, a pattern for splitting data from one data collection into separate data collections, a pattern for invoking a key mapping function, a pattern for invoking a data transformation function, a pattern for invoking a connectivity function for a particular application system, and a integration design pattern for invoking a connectivity function for invoking a particular service.

47. The method of claim 45 wherein representing at least one integration pattern comprises representing at least one an integration design pattern that decomposes into at least two integration design patterns.

48. The method of claim 44 further comprising generating application integration software based on the declarative integration workflow.

49. The method of claim 48 wherein generating application integration software comprises generating a template for application integration software.

50. The method of claim 48 wherein associating the generated application integration software with the declarative integration workflow comprises associating at least one portion of the generated application integration software with at least one portion of the declarative integration workflow, each particular portion of the generated application integration software being associated with a particular portion of the declarative integration workflow.

51. The method of claim 48 wherein generating application integration software based on the declarative integration workflow comprises generating application integration software based on one or more layers of application integration.

52. The method of claim 51 wherein generating application integration software based on at least one layer of application integration comprises generating application integration software based on at least one of a business process layer, an integration design pattern layer, a functional atom layer, a data transformation rule layer, a data layer, and a physical connection layer.

53. The method of claim 52 wherein the functional atom layer comprises a functional atom layer that identifies at least one functional atom that declaratively describes a discrete action that relates to an application integration function.