Rapid application integration using functional atoms

• US 7,257,818 B2
• Filed: 12/13/2002
• Issued: 08/14/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): Zhen; Wei
• Assistant Examiner(s): Truong; LeChi
• Application Number:
  US10/318,364
• Publication Number:
  US 20040044729A1
• Time in Patent Office: 1,705 Days
• Field of Search: 719/310
• US Class Current: 719/310
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

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 system for use in application system integration of a first software application program and a second software application program, the system comprising:

computer-readable storage storing a map scenario, wherein;

the map scenario defines a configured collection of reusable functional atoms, the configured collection identifies a path of connectivity between the functional atoms to perform a data exchange of application data between the first and second software application programs, wherein;

the functional atoms describe one or more of a data processing functional atom, a data persistency functional atom, and a helper atom, and

the one or more of a data processing functional atom describes one or more of a transformation functional atom, a branch functional atom, an unbranch functional atom, a split functional atom, and a join functional atom,

each functional atom represents a unit of integration that is performed completely during the data exchange, and

at least one functional atom represents a type of application data transformation that is performed during the data exchange; and

an integration processor configured to access the map scenario from the computer-readable storage and execute the configured collection of reusable functional atoms to perform the data exchange between the first and second software application programs, wherein the integration processor executing a transformation functional atom is configured to;

receive an application data collection and a data transformation rule;

transform the received application data collection by applying the data transformation rule identified by the transformation functional atom to the recieved application data collection; and

produce a transformed application data collection.

2. The system of claim 1 wherein the first and second software application programs reside on different computer systems.

3. The system of claim 1 wherein the computer-readable storage comprises a map scenario repository that stores map scenarios.

4. The system of claim 1 wherein the functional atoms describe one or more of a call atom and an include atom.

5. The system of claim 1 wherein the data transformation rule comprises multiple transformation components.

6. The system of claim 1 wherein the integration processor executing a branch functional atom is configured to:

receive an application data collection; and

transform the received application data collection based on data values within the received application data collection; and

produce at least one data collection based on the received application data.

7. The system of claim 1 wherein the integration processor executing an unbranch functional atom is configured to:

receive at least two application data collections; and

produce a new application data collection based on the received application data collections.

8. The system of claim 1 wherein the integration processor executing a split functional atom is configured to:

received an application data collection;

transformed the received application data collection based on repeating data within the received application data collection; and

produce at least two application data collections based on the received data collection.

9. The system of claim 1 wherein the integration processor executing a join functional atom is configured to:

receive at least one application data collection with each application data collection including a particular type of data, and

produce an application data collection based on the at least one data application collection received.

10. The system of claim 1 wherein the integration processor executing a validate functional atom is configured to:

received an application data collection and a data validation rule,

validate the received application data collection by applying the data validation rule to the received application data collection, and

produce a validation result.

11. The system of claim 10 wherein the data validation rule comprises multiple validation components.

12. The system of claim 1, wherein the first software application program comprises a groupware software application program, and the integration processor is configured to:

receive groupware data associated with the groupware software application program;

use the functional atoms to transform the received groupware data into a first data format; and

send the received groupware data in the first data format to a computer system on which the second software application program resides.

13. The system of claim 12 wherein using the functional atoms comprises using a transformation functional atom to transform a received data collection by applying a data transformation rule to the received data collection.

14. The system of claim 1, wherein the first software application program comprises a groupware software application program, further comprising a groupware adapter connected to a groupware connector wherein:

the groupware adapter is configured to;

receive groupware data associated with the groupware software application program, use the functional atoms to transform the received groupware into a first data format, and send the received groupware data in the first data format to the groupware connector; and

the groupware connector is configured to;

receive groupware data in the first data format from the groupware adapter, use the functional atoms to transform the received groupware data into a second data format, and send the received groupware, data in the second data format to a groupware server.

15. A computer-readable medium having embodied thereon a computer program configured to perform data exchanges, the medium comprising one or more code segments, that when executed, perform data exchanges between a first software application program and a second software application program using a map scenario stored in computer-readable storage, wherein:

the map scenario defines a configured collection of reusable functional atoms, the configured collection identifies a path of connectivity between the functional atoms to perform a data exchange of application data between the first and second application programs, wherein;

the functional atoms describe one or more of a data processing functional atom, a data persistency functional atom, and a helper functional atom, and

the one or more of a data processing functional atom describes one or more of a transformation functional atom, a branch functional atom, an unbranch functional atom, a split functional atom, and a join functional atom;

each functional atom represents a unit of integration that is performed completely during a data exchange of application data between the first and second application programs, and

at least one functional atom represents a type of application data transformation that is performed during the data exchange; and

the one or more code segments are configured to access the map scenario from the computer-readable storage and execute the configured collection of reusable functional atoms to perform the data exchange, wherein the one or more code segments comprise a transformation functional atom configured to;

receive an application data collection and a data transformation rule;

transform the received application data collection by applying the data transformation rule identified by the transformation functional atom to the received application data collection; and

produced a transformed application data collection.

16. The medium of claim 15 wherein the first and second software application programs reside on different computer systems.

17. The medium of claim 15 wherein the computer-readable storage stores a map repository that stores map scenarios.

18. The medium of claim 15 wherein the functional atoms describes one or more of a call atom and an include atom.

19. The medium of claim 15 wherein the data transformation rule comprises a multiple transformation components.

20. The medium of claim 15 wherein the one or more code segments further comprises a branch functional atom configured to:

receive an application data collection;

transform the received application data collection based in data values within the received application data collection; and

produce at least one application data collection based on the received application data collection.

21. The medium of claim 15 wherein the one or more code segments further comprise an unbranch functional atom configured to:

receive at least two application data collections; and

produce a new application data collection based on the data collections received.

22. The medium of claim 15 wherein the one or more code segments further comprise a split functional atom configured to:

receive an application data collection;

transform the received application data collection based on repeating data within the received application data collection; and

produce at least one application data collection based on the received application data collection.

23. The medium of claim 15 wherein the one or more code segments further comprise a join functional atom configured to:

receive at least one application data collection with each application data collection including a particular type of data; and

produce an application data collection based on the at least one application data collection received.

24. The medium of claim 15 wherein the one or more code segments further comprise a validate functional atom configured to:

receive an application data collection and a data validation rule,

validate the received application data collection by applying the data validation rule to the received application data collection; and

produce a validation result.

25. The medium of claim 24 wherein the data validation rule comprises multiple validation components.

26. The medium of claim 15, wherein the first software application program comprises a groupware software application and the one or more code segments are configured to:

receive groupware data from the groupware software application;

use the functional atoms to transform the received groupware data into a first data format; and

send the received groupware data in the first data format to the second software application program.

27. The medium of claim 26 wherein using the functional atoms comprises using a transformation functional atom to transform a received data collection by applying a data transformation rule to the received data collection.

28. The medium of claim 15, wherein:

the first software application program comprises a groupware software application, the one or more code segments are configured for use in groupware integration, and

further comprise one or more code segments configured for a groupware adapter and one or more code segments configured for a groupware connector,

the one or more code segments configured for the groupware adapter are configured to;

receive groupware data associated with the groupware software application program,

use the functional atoms to transform the received groupware into a first data format, and

send the received groupware data in the first data format to the groupware connector, and

the one or more code segments configured for the groupware connector are configured to;

receive groupware data in the first data format from the groupware adapter,

use the functional atoms to transform the received groupware data into a second data format, and

send the received groupware data in the second data format to a groupware server.

29. A method for use in application system integration, the method comprising using a map scenario to perform data exchanges between a first software application programs and a second software application program, wherein:

a map scenario defines a configured collection of reusable functional atoms, the configured collection identifies a path of connectivity between the functional atoms to perform a data exchange of application data between the first and second software application programs, wherein;

the functional atoms describe one or more of a data processing functional atom, a data persistency functional atom, and a helper functional atom, and

the one or more of a data processing functional atom describes one or more of a transformation functional atom, a branch functional atom, an unbranch functional atom, a split functional atom, and a join functional atom;

each functional atom represents a unit of integration that is performed completely during the data exchange, and

at least one functional atom represents a type of application data transformation that is performed during the data exchange; and

using the map scenario perform data exchanges comprises;

accessing the map scenario from computer-readable storage, and

executing the configured collection of reusable functional atoms to perform the data exchange between the first and second software application programs, wherein the map scenario includes a transformation functional atom and the method further comprises;

receiving an application data collection and a data transformation rule;

transforming the application received data collection by applying the data transformation rule to the received application data collection; and

producing a transformed application data collection.

30. The method of claim 29 wherein the data exchanges are performed between the first and second software application programs that reside on different computer systems.

31. The method of claim 29 wherein the functional atoms describe one or more of a call atom and an include atom.

32. The method of claim 29 wherein the data transformation rule comprises multiple transformation components.

33. The method of claim 29 wherein the map scenario includes a branch functional atom and the method further comprises:

receiving an application data collection;

transforming the received application data collection based in data values within the received application data collection; and

producing at least one application data collection based on the received application data collection.

34. The method of claim 29 wherein the map scenario includes an unbranch functional atom and the method further comprises:

receiving at least one application data collection; and

producing an application data collection based on the application data collections received.

35. The method of claim 29 wherein the map scenario includes a split functional atom and the method further comprises:

received an application data collection;

transforming the received application data collection based on repeating data within the received application data collection; and

producing at least one application data collection based on the received application data collection.

36. The method of claim 29 wherein the map scenario includes a join functional atom and the method further comprises:

receiving at least one application data collection with each application data collection including a particular type of data; and

producing an application data collection based on the at least one application data collection received.

37. The method of claim 29 wherein the map scenario includes a validate functional atom and the method further comprises:

receiving an application data coalition and a data validation rule,

validating the received application data collection by applying the data validation rule to the received application data collection; and

producing a validation result.

38. The met of claim 37 wherein the data validation rule comprises multiple validation components.

39. The method of claim 29 wherein:

the first software application program comprises a groupware software application program, and

using a map scenario to perform data exchanges comprises performing a data exchange for use in groupware integration, the method further comprises;

receiving groupware data from the groupware software application program;

using the functional atoms to transform the received groupware data into a first data format; and

sending the received groupware data in the first data format to the second software application program.

40. The method of claim 39 wherein using a map scenario to perform data exchanges comprises using a transformation functional atom to transform a received application data collection by applying a data transformation rule to the received application data collection.

41. The method of claim 29 wherein:

the first software application program comprises a groupware software application program, and

using a map scenario to perform data exchanges comprises performing a data exchange for use in groupware integration, the method further comprises;

receiving groupware data from the groupware application program at a groupware adapter;

using the functional atoms to transform the received groupware data into a first data format;

sending the received groupware data in the first data format to a groupware connector;

receiving groupware data in the first data format at the groupware connector,

using the functional atoms to transform the received groupware data into a second data format; and

sending the received groupware data in the second data format to a groupware server.