Adapter framework

• US 7,865,606 B1
• Filed: 09/30/2003
• Issued: 01/04/2011
• Est. Priority Date: 12/13/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Tewes, Martin, Fitzer, Joachim
• Primary Examiner(s): Burgess; Barbara N
• Application Number:
  US10/677,095
• Time in Patent Office: 2,653 Days
• Field of Search: 709/206, 709/207, 709/203, 709/230, 709/223, 709/224, 709/227
• US Class Current: 709/230
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A framework for communicating between central message exchange server and one or more heterogeneous external data sources includes an adapter engine. The adapter engine includes an instantiation of one or more adapters. Each adapter is configured to connect, via messaging, an external data source operating using a native message format and the central message exchange server using an extensible markup language (XML) messaging format.

Claims

1. A method comprising:

receiving, at an exchange infrastructure implemented on one or more processors, data from a heterogeneous external data source implemented on one or more other machines, the data comprising a data format that is native to the heterogeneous external data source and not compliant with any of one or more extensible markup language protocols used by an integration server of the exchange infrastructure;

instantiating, using an adapter engine implemented on the exchange infrastructure, an inbound adapter based on the data format used by the heterogeneous external data source, the adapter engine configured to dynamically instantiate and host a plurality of inbound and outbound adapter pairs, each of the plurality of inbound and outbound pairs being instantiated for an associated data format used by one of a plurality, of heterogeneous external data sources, each of the instantiated inbound and outbound adapter pairs adapted to be configured, created, started, stopped, and terminated;

generating, at the inbound adapter, a message that conforms to at least one of the one or more extensible markup language protocols used by the integration server, the message comprising at least part of the data received at the exchange infrastructure;

persisting, at the inbound adapter, a message identifier that identifies the message for re-sending of the message in case delivery of the message to the integration server fails;

passing, through the inbound adapter, the message to the integration server;

receiving, at the inbound adapter from the integration server, a confirmation acknowledgement confirming receipt of the message by the integration server; and

processing, at the inbound adapter, the confirmation acknowledgment to prevent the message from being resent.

2. The method in accordance with claim 1, wherein the message generated by the inbound adapter is an XML message.

3. The method in accordance with claim 1, further comprising:

instantiating, at the one or more processors, an outbound adapter based on the data format used by the heterogeneous external data source;

converting, by the outbound adapter, an outbound message from the integration server to the heterogeneous external data source, the converting comprising converting the outbound message from one of the one or more extensible markup language protocols used by the integration server to the data format that is native to the heterogeneous external data source; and

sending the outbound message from the outbound adapter to the heterogeneous external data source.

4. The method in accordance with claim 3, wherein the outbound message from the integration server is an XML message.

5. The method in accordance with claim 1, wherein the heterogeneous external data source and the exchange infrastructure communicate via a hypertext transport protocol (HTTP).

6. The method in accordance with claim 1, wherein the exchange infrastructure operates using a simple object access protocol (SOAP).

7. The method in accordance with claim 1, wherein the heterogeneous external data source includes a sending application.

8. The method in accordance with claim 1, further comprising:

monitoring operation of each inbound adapter and presenting monitoring information to a graphic user interface (GUI), by an adapter monitor.

9. The method in accordance with claim 8, further comprising:

generating the GUI and displaying the monitoring information, by a GUI engine.

10. The method in accordance with claim 8, further comprising:

logging the monitoring information by an information log.

11. The method in accordance with claim 8, further comprising:

logging message identifiers of messages communicated through the inbound adapter by an identification log.

12. The method in accordance with claim 1, further comprising:

receiving, at the exchange infrastructure, second data from a second heterogeneous external data source, the second data comprising a second data format that is native to the second heterogeneous external data source and not compliant with any of the one or more extensible markup language protocols used by the integration server;

instantiating, by the integration server on the one or more processors, a second inbound adapter based on the second data format used by the second heterogeneous external data source;

generating, at the second inbound adapter, a second message that conforms to at least one of the one or more extensible markup language protocols used by the integration server, the second message comprising at least part of the second data received at the exchange infrastructure;

persisting, at the second inbound adapter, a second message identifier that identifies the second message for re-sending of the second message in case delivery of the second message to the integration server fails;

passing, through the second inbound adapter, the second message to the integration server;

receiving, at the second inbound adapter from the integration server, a second confirmation acknowledgement confirming receipt of the second message by the integration server; and

processing, at the second inbound adapter, the second confirmation acknowledgment to prevent the second message from being resent.

13. The method in accordance with claim 1, wherein the heterogeneous external data source communicates with the exchange infrastructure through a firewall.

14. The method in accordance with claim 1, further comprising:

registering, at a system landscape directory of the exchange infrastructure, an installation of the external heterogeneous data source for collaboration with the exchange infrastructure, the system landscape directory comprising a system landscape that describes internal and external components that are installed and available on certain machines that collaborate via the exchange infrastructure, the external components comprising the external heterogeneous data source;

accessing, by an integration repository of the exchange infrastructure from the system landscape directory, a design-time description of the external heterogeneous data source;

capturing, by an integration directory of the exchange infrastructure at runtime, a configuration-specific collaboration description of the external heterogeneous data source, the configuration-specific collaboration description comprising mappings and routing rules for processing messaging from the external heterogeneous data source; and

retrieving, by the integration server from the integration directory, the configuration-specific collaboration description for the external heterogeneous data source for use in instantiating the inbound adapter.

15. A system comprising:

at least one processor; and

at least one memory storing instructions that cause the at least one processor to perform operations comprising;

receiving, at an exchange infrastructure implemented on the at least one processor, data from a heterogeneous external data source implemented on one or more other machines, the data comprising a data format that is native to the heterogeneous external data source and not compliant with any of one or more extensible markup language protocols used by an integration server of the exchange infrastructure;

instantiating, using-an adapter engine implemented on the exchange infrastructure integration server on the at least one processor, an inbound adapter based on the data format used by the heterogeneous external data source, the adapter engine configured to dynamically instantiate and host a plurality, of inbound and outbound adapter pairs, each of the plurality, of inbound and outbound pairs being instantiated for an associated data format used by one of a plurality of heterogeneous external data sources, each of the instantiated inbound and outbound adapter pairs adapted to be configured, created, started, stopped, and terminated;

generating, at the inbound adapter, a message that conforms to at least one of the one or more extensible markup language protocols used by the integration server, the message comprising at least part of the data received at the exchange infrastructure;

persisting, at the inbound adapter, a message identifier that identifies the message for re-sending of the message in case delivery of the message to the integration server fails;

passing, through the inbound adapter, the message to the integration server;

receiving, at the inbound adapter from the integration server, a confirmation acknowledgement confirming receipt of the message by the integration server; and

processing, at the inbound adapter, the confirmation acknowledgment to prevent the message from being resent.

16. An article comprising a non-transitory machine-readable medium configured to provide instructions to at least one programmable processor, the instructions causing the programmable processor to perform operations comprising:

receiving, at an exchange infrastructure implemented on the programmable processor, data from a heterogeneous external data source implemented on one or more other machines, the data comprising a data format that is native to the heterogeneous external data source and not compliant with any of one or more extensible markup language protocols used by an integration server of the exchange infrastructure;

instantiating, using an adapter engine implemented on the exchange infrastructure, an inbound adapter based on the data format used by the heterogeneous external data source, the adapter engine configured to dynamically instantiate and host a plurality, of inbound and outbound adapter pairs, each of the plurality, of inbound and outbound pairs being instantiated for an associated data format used by one of a plurality of heterogeneous external data sources, each of the instantiated inbound and outbound adapter pairs adapted to be configured, created, started, stopped, and terminated;

generating, at the inbound adapter, a message that conforms to at least one of the one or more extensible markup language protocols used by the integration server, the message comprising at least part of the data received at the exchange infrastructure;

persisting, at the inbound adapter, a message identifier that identifies the message for re-sending of the message in case delivery of the message to the integration server fails;

passing, through the inbound adapter, the message to the integration server;

receiving, at the inbound adapter from the integration server, a confirmation acknowledgement confirming receipt of the message by the integration server; and

processing, at the inbound adapter, the confirmation acknowledgment to prevent the message from being resent.