IP Library Granted Patent US 10,936,378
Granted Patent B1
US 10,936,378 · App. 16/672,936 · Granted Mar 2, 2021

System and method for automating integration process building between multiple applications using integration assistance robots

Inventor: Thameem U. Khan (Germantown, MD)
Assignee: BOOMI, INC.
G06F9/54
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,936,378
App. No.
16/672,936
Granted
Mar 2, 2021
Kind
B1
Abstract

An information handling system operating an integration assistance robotic automation system may comprise a memory storing a log of machine-executable code instructions generated by a plurality of application programming interfaces (APIs) for a plurality of applications, based on user instructions previously received at the APIs to define an integration process between a first application executing code instructions in a first coding language and a second application executing code instructions in a second coding language, and a processor parsing the log to identify a first connector code set in the first language defining an action to be taken on a dataset managed by the first application, and a second connector code set in the second language defining an action to be taken on a dataset managed by the second application, and transmitting an executable run-time engine, the first and second connector code sets for execution at an execution location.

Claims (37)

1. An information handling system operating an integration assistance robotic automation system comprising:

a memory storing a log of machine-executable code instructions generated by a plurality of application programming interfaces (APIs) for a first application and a second application, based on user instructions previously received at the plurality of APIs to define a user-designed integration process between the first application and the second application;

wherein the first application executes code instructions in a first coding language and the second application executes code instructions in a second coding language;

a processor parsing the log to identify a first connector code set written in the first coding language to define an action to be taken on a dataset managed at a specific location by the first application, and a second connector code set written in the second coding language to define an action to be taken on a dataset managed at a specific location by the second application;

the processor transmitting an executable run-time engine, the first connector code set, and the second connector code set for execution at an execution location.

2. The information handling system of claim 1 further comprising:

the processor intercepting a first API code instruction transmitted from a first API to the first application, defining the action to be taken on the dataset managed by the first application, and a second API code instruction transmitted from a second API to the second application, defining the action to be taken on the dataset managed at the specific location by the second application; and

the memory storing the intercepted first API code instruction and the intercepted second API code instruction as the log of machine-executable code instructions.

3. The information handling system of claim 2 , wherein the processor executes a robotic process automation logging code instruction to intercept the first API code instruction and the second API code instruction.

4. The information handling system of claim 1 , wherein the first coding language is XML.

5. The information handling system of claim 1 , wherein the second coding language is JSON.

6. The information handling system of claim 1 , wherein one of the plurality of applications is executed at a different location than a location at which the runtime engine is executed.

7. The information handling system of claim 1 , wherein the first application is executed at a same location as a location at which the runtime engine is executed.

8. A method of automatically creating an executable process of integrating a dataset between two incompatible applications comprising:

storing, in a memory, a log of machine-executable code instructions generated by a plurality of application programming interfaces (APIs) for a first application and a second application, based on user instructions previously received at the plurality of APIs to define a user-designed integration process between the first application and the second application;

wherein the first application executes code instructions in a first coding language and the second application executes code instructions in a second coding language;

parsing the log, via a processor, to identify a first connector code set written in the first coding language to define an action to be taken on a dataset managed at a specific location by the first application, and a second connector code set written in the second coding language to define an action to be taken on a dataset managed at a specific location by the second application;

transmitting, via the processor, an executable run-time engine, the first connector code set, and the second connector code set for execution at an execution location.

9. The method of claim 8 further comprising:

intercepting, via a processor, a first API code instruction transmitted from a first API to the first application, defining the action to be taken on the dataset managed by the first application, and a second API code instruction transmitted from a second API to the second application, defining the action to be taken on the dataset managed at the specific location by the second application; and

storing the intercepted first API code instruction and the intercepted second API code instruction in the memory as the log of machine-executable code instructions.

10. The method of claim 9 , wherein the processor executes a robotic process automation logging code instruction to intercept the first API code instruction and the second API code instruction.

11. The method of claim 8 , wherein the first coding language is XML.

12. The method of claim 8 , wherein the second coding language is JSON.

13. The method of claim 8 , wherein the second application is executed at a different location than a location at which the runtime engine is executed.

14. The method of claim 8 , wherein the second application is executed at a same location as a location at which the runtime engine is executed.

15. An information handling system operating an integration assistance robotic automation system comprising:

the processor intercepting a first API code instruction written in a first coding language, transmitted from a first of a plurality of APis to a first application, defining an action to be taken on a dataset managed at a specific location by the first application in an integration process for a plurality of applications, based on user instructions received at the first of the plurality of APis;

a processor intercepting a second API code instruction, written in a second coding language, transmitted from a second of the plurality of APis to a second application in the integration process, defining an action to be taken on a dataset managed at a specific location by the second application, based on user instructions received at the second of the plurality of APis;

a memory for storing the intercepted first API code instruction and the intercepted second API code instruction as a log of machine-executable code instructions;

the processor parsing the log to identify a first connector code set written in the first coding language, defining the action to be taken on the dataset managed at the specific location by the first application, and a second connector code set written in the second coding language, defining the action to be taken on the dataset managed at the specific location by the second application;

the processor transmitting an executable run-time engine, the first connector code set, and the second connector code set for execution at an execution location.

16. The information handling system of claim 15 , wherein the processor executes a robotic process automation logging code instruction to intercept the first API code instruction and the second API code instruction.

17. The information handling system of claim 1 , wherein the first coding language is JSON.

18. The information handling system of claim 1 , wherein the second coding language is XML.

19. The information handling system of claim 1 , wherein the first application is executed at a cloud service provider, in a different location than the location at which the runtime engine is executed.

20. The information handling system of claim 1 , wherein the second application is executed at a cloud service provider, at a same location as the location at which the runtime engine is executed.

Assignments (12)
SECURITY INTEREST Recorded Nov 12, 2024
From: SIXTH STREET SPECIALTY LENDING, INC.
To: BLUE OWL CAPITAL CORPORATION
Reel/Frame 069342/0406 →
SECURITY INTEREST Recorded Oct 1, 2021
From: BOOMI, LLC
To: SIXTH STREET SPECIALTY LENDING, INC., AS COLLATERAL AGENT
Reel/Frame 057679/0908 →
PARTIAL RELEASE OF SECURITY INTEREST Recorded May 28, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.
Reel/Frame 056422/0485 →
PARTIAL RELEASE OF SECURITY INTEREST IN SPECIFIED PATENTS Recorded May 28, 2021
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: DELL PRODUCTS L.P.
Reel/Frame 056423/0422 →
PARTIAL RELEASE OF SECURITY INTEREST IN SPECIFIED PATENTS Recorded May 28, 2021
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: DELL PRODUCTS L.P.
Reel/Frame 056423/0435 →
PARTIAL RELEASE OF SECURITY INTEREST IN SPECIFIED PATENTS Recorded May 28, 2021
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: DELL PRODUCTS L.P.
Reel/Frame 056423/0454 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 20, 2020
From: DELL PRODUCTS L.P.
To: BOOMI, INC.
Reel/Frame 054430/0589 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 053311/0169 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 26, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 052243/0773 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Mar 24, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052216/0758 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 4, 2019
From: KHAN, THAMEEM U.
To: DELL PRODUCTS, LP
Reel/Frame 050906/0096 →