US 10,540,190 B2Granted

Generic connector module capable of integrating multiple applications into an integration platform

AssigneeInternational Business Machines Corporation

InventorsAditya M. Burli, Subramanian Krishnan, Ramya Rajendiran, Nagarjuna Surabathina

Life of this patent

Estimating the term…

Loading patent…

Abstract

A generic connector module of an integration-platform system reconciles the system's application-independent canonical API with each application-specific API used by an endpoint application. The system generates a software library of application-specific configuration files each capable of enabling the connector to translate commands between one application-specific API format and the canonical-API format. Applications may be added to the system, removed, or updated without revising the connector. When the connector receives an application-specific request from an application or a canonical request from the integration platform, the connector selects an application-specific configuration file that lets the connector translate the received request into its complementary API format. The connector then forwards the translated request to its intended recipient. A converse process occurs when receiving an application-specific or canonical response to the translated request. Translations can be performed dynamically, in real time, without requiring a distinct connector module dedicated to each application.

Claims17

Dependent claims

A generic connector module of an integration-platform system comprising a processor, a memory coupled to the processor, and a computer-readable hardware storage device coupled to the processor, the storage device containing program code configured to be run by the processor via the memory to implement a method for integrating a set of endpoint applications into a computing platform, the method comprising:

receiving, from the integration-platform system, a canonical service request generated by the integration-platform system,
where the canonical service request is configured in compliance with conventions of a canonical application programming interface,
where the canonical service request was generated in response to the integration-platform system intercepting a communication sent by the computing platform,
where the communication was originally directed to a first application of the set of endpoint applications, and
where the canonical service request is associated with first identifying information capable of identifying the first application;
selecting, as a function of the first identifying information, a first configuration file of a set of application-specific configuration files;
extracting first configuration data from the first configuration file, where the first configuration data is specific to the first application;
generating an application-specific service request that is functionally equivalent to the canonical service request, where the application-specific service request is configured, as a function of the first configuration data, in compliance with conventions of a first application-specific application programming interface associated with the first application;
transmitting the application-specific service request to the first application;
intercepting an application-specific response returned by the first application in response to receiving the application-specific service request, where the application-specific response is configured in compliance with conventions of the first application-specific application programming interface;
producing a canonical response that is functionally equivalent to the application-specific response, where the canonical response is configured, as a function of the first configuration data, in compliance with conventions of the canonical application programming interface;
and
transmitting the canonical response to the integration platform.

10 more elements

A method for integrating a set of endpoint applications into a computing platform, the method comprising:

receiving, from an integration-platform system by a generic connector module, a canonical service request generated by the integration-platform system,
where the canonical service request is configured in compliance with conventions of a canonical application programming interface,
where the canonical service request was generated in response to the integration-platform system intercepting a communication sent by the computing platform,
where the communication was originally directed to a first application of a set of endpoint applications, and
where the canonical service request is associated with first identifying information capable of identifying the first application;
selecting, as a function of the first identifying information, a first configuration file of a set of application-specific configuration files;
extracting first configuration data from the first configuration file, where the first configuration data is specific to the first application;
generating an application-specific service request that is functionally equivalent to the canonical service request, where the application-specific service request is configured, as a function of the first configuration data, in compliance with conventions of a first application-specific application programming interface associated with the first application;
transmitting the application-specific service request to the first application;
intercepting an application-specific response returned by the first application in response to receiving the application-specific service request, where the application-specific response is configured in compliance with conventions of the first application-specific application programming interface;
producing a canonical response that is functionally equivalent to the application-specific response, where the canonical response is configured, as a function of the first configuration data, in compliance with conventions of the canonical application programming interface;
and
transmitting the canonical response to the integration platform.

10 more elements

A computer program product, comprising a computer-readable hardware storage device having a computer-readable program code stored therein, the program code configured to be executed by an integration-platform system comprising a processor, a memory coupled to the processor, and a computer-readable hardware storage device coupled to the processor, the storage device containing program code configured to be run by the processor via the memory to implement a method for generic connector module of an integration-platform system comprising a processor, a memory coupled to the processor, and a computer-readable hardware storage device coupled to the processor, the storage device containing program code configured to be run by the processor via the memory to implement a method for integrating a set of endpoint applications into a computing platform, the method comprising:

receiving, from the integration-platform system, a canonical service request generated by the integration-platform system,
where the canonical service request is configured in compliance with conventions of a canonical application programming interface,
where the canonical service request was generated in response to the integration-platform system intercepting a communication sent by the computing platform,
where the communication was originally directed to a first application of the set of endpoint applications, and
where the canonical service request is associated with first identifying information capable of identifying the first application;
selecting, as a function of the first identifying information, a first configuration file of a set of application-specific configuration files;
extracting first configuration data from the first configuration file, where the first configuration data is specific to the first application;
generating an application-specific service request that is functionally equivalent to the canonical service request, where the application-specific service request is configured, as a function of the first configuration data, in compliance with conventions of a first application-specific application programming interface associated with the first application;
transmitting the application-specific service request to the first application;
intercepting an application-specific response returned by the first application in response to receiving the application-specific service request, where the application-specific response is configured in compliance with conventions of the first application-specific application programming interface;
producing a canonical response that is functionally equivalent to the application-specific response, where the canonical response is configured, as a function of the first configuration data, in compliance with conventions of the canonical application programming interface;
and
transmitting the canonical response to the integration platform.

10 more elements

Dependencies are inferred from the claim text.