# US 2025/0147759 A1 · Automatic generation of a coexistence layer using robotic process automation for application modernization

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0147759 A1
- Document ID: US20250147759A1
- Status: Published application
- Kind: A1
- Application number: 18/503,159
- Filed: 2023-11-06
- Published: 2025-05-08
- Earliest claimed: 2023-11-06
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Corneliu Nicolae Barbulescu; Ciprian Constantinescu
- Web page: https://patentgrep.com/patent/US20250147759A1

## CPC

- G06F 8/76: Adapting program code to run in a different environment; Porting
- G06F 8/36: Software reuse
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Updating calls or operations in a database management system includes mapping, by a computer processor, application programming interface (API) types associated with a legacy server and a new server. The legacy server recognizes request signatures of a first API type and the new server recognizes request signatures of a second API type that is distinct from the first API type. A request is received from a system of engagement, addressed to a system of records resident on a legacy server. The request is intercepted by a coexistence layer module. A determination is made of whether the intercepted request uses a request signature recognized by the first API type. The coexistence layer module converts the intercepted request to a format using the request signature of the second API type. The converted intercepted request is sent to the new server. The converted intercepted request is performed by the new server.

## Claims

### Claim 1

A computer program product for updating calls or operations in a database management system, the computer program product comprising:
one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions comprising:
mapping, by a computer processor, application programming interface (API) types associated with a legacy server and a new server, wherein the legacy server recognizes request signatures of a first API type and the new server recognizes request signatures of a second API type that is distinct from the first API type;
receiving, by the computer processor, a request from a system of engagement resident on a client-side computing device, addressed to a system of records resident on a legacy server, wherein the request includes a call or operation;
intercepting the request by a coexistence layer module run by the computer processor;
determining, by the computer processor referencing the mapping, whether the intercepted request points to a system of records component that has been moved from the legacy server to a new server;
determining whether the intercepted request uses a request signature recognized by the first API type;
converting, by the coexistence layer module, the intercepted request to a format using the request signature of the second API type;
sending the converted intercepted request to the new server; and
performing the converted request by the new server.

### Claim 2 (depends on 1)

The computer program product of claim 1, wherein the program instructions further comprise operating an applications integrations module in the coexistence layer module, wherein the applications integrations module enables different applications running in the systems of engagement to operate with the system of records.

### Claim 3 (depends on 2)

The computer program product of claim 2, wherein the program instructions further comprise:
operating a robotic process automation in the coexistence layer module;
automatically generating an adapter software module by the robotic process automation upon determining that the intercepted request from the system of engagement is addressed to the system of records component moved to the new server; and
mapping, by the adapter software module, the intercepted request to an address on the new server.

### Claim 4 (depends on 3)

The computer program product of claim 3, wherein the program instructions further comprise, for new mappings, generating a new adapter software module deployed by the robotic process automation to the applications integrations module using either application programming interface calls or user interface actions.

### Claim 5 (depends on 4)

The computer program product of claim 4, wherein the program instructions further comprise deleting, by the robotic process automation, adapter software modules that are inactive.

### Claim 6 (depends on 1)

The computer program product of claim 1, wherein the program instructions further comprise:
monitoring new requests between the system of engagement and the system of records, by an interaction observer software module;
recording, by the observer software module, the new requests between the system of engagement and the system of records as interaction metadata; and
referencing, by the coexistence layer module, the recorded interaction metadata in the conversion of the intercepted request to the second software protocol.

### Claim 7 (depends on 1)

The computer program product of claim 1, wherein the program instructions further comprise:
determining, by the computer processor, whether the intercepted request points to a system of records component that remains resident on the legacy server; and
sending the intercepted request through to the legacy server.

### Claim 8

A computer implemented method for updating calls or operations in a database management system, comprising:
mapping, by a computer processor, application programming interface (API) types associated with a legacy server and a new server, wherein the legacy server recognizes request signatures of a first API type and the new server recognizes request signatures of a second API type that is distinct from the first API type;
receiving, by the computer processor, a request from a system of engagement resident on a client-side computing device, addressed to a system of records resident on a legacy server, wherein the request includes a call or operation;
intercepting the request by a coexistence layer module run by the computer processor;
determining, by the computer processor referencing the mapping, whether the intercepted request points to a system of records component that has been moved from the legacy server to a new server;
determining whether the intercepted request uses a request signature recognized by the first API type;
converting, by the coexistence layer module, the intercepted request to a format using the request signature of the second API type;
sending the converted intercepted request to the new server; and
performing the converted request by the new server.

### Claim 9 (depends on 8)

The method of claim 8, further comprising operating an applications integrations module in the coexistence layer module, wherein the applications integrations module enables different applications running in the systems of engagement to operate with the system of records.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
operating a robotic process automation in the coexistence layer module;
automatically generating an adapter software module by the robotic process automation upon determining that the intercepted request from the system of engagement is addressed to the system of records component moved to the new server; and
mapping, by the adapter software module, the intercepted request to an address on the new server.

### Claim 11 (depends on 10)

The method of claim 10, further comprising, for new mappings, generating a new adapter software module deployed by the robotic process automation to the applications integrations module using either application programming interface calls or user interface actions.

### Claim 12 (depends on 11)

The method of claim 11, further comprising deleting, by the robotic process automation, adapter software modules that are inactive.

### Claim 13 (depends on 8)

The method of claim 8, further comprising:
monitoring new requests between the system of engagement and the system of records, by an interaction observer software module;
recording, by the observer software module, the new requests between the system of engagement and the system of records as interaction metadata; and
referencing, by the coexistence layer module, the recorded interaction metadata in the conversion of the intercepted request to the second software protocol.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
determining, by the computer processor, whether the intercepted request points to a system of records component that remains resident on the legacy server; and
sending the intercepted request through to the legacy server.

### Claim 15

A computing device configured to update calls or operations in a database management system, comprising:
a processor operating a software transformation engine; and
a memory coupled to the processor, the memory storing instructions to cause the processor to perform acts comprising:
mapping, by the processor, application programming interface (API) types associated with a legacy server and a new server, wherein the legacy server recognizes request signatures of a first API type and the new server recognizes request signatures of a second API type that is distinct from the first API type;
receiving, by the processor, a request from a system of engagement resident on a client-side computing device, addressed to a system of records resident on a legacy server, wherein the request includes a call or operation;
intercepting the request by a coexistence layer module run by the computer processor;
determining, by the processor referencing the mapping, whether the intercepted request points to a system of records component that has been moved from the legacy server to a new server;
determining whether the intercepted request uses a request signature recognized by the first API type;
converting, by the coexistence layer module, the intercepted request to a format using the request signature of the second API type;
sending the converted intercepted request to the new server; and
performing the converted request by the new server.

### Claim 16 (depends on 15)

The computing device of claim 15, wherein the instructions cause the processor to perform further acts comprising operating an applications integrations module in the coexistence layer module, wherein the applications integrations module enables different applications running in the systems of engagement to operate with the system of records.

### Claim 17 (depends on 16)

The computing device of claim 16, wherein the instructions cause the processor to perform further acts comprising:
operating a robotic process automation in the coexistence layer module;
automatically generating an adapter software module by the robotic process automation upon determining that the intercepted request from the system of engagement is addressed to the system of records component moved to the new server; and
mapping, by the adapter software module, the intercepted request to an address on the new server.

### Claim 18 (depends on 17)

The computing device of claim 17, wherein the instructions cause the processor to perform further acts comprising, for new mappings, generating a new adapter software module deployed by the robotic process automation to the applications integrations module using either application programming interface calls or user interface actions.

### Claim 19 (depends on 15)

The computing device of claim 15, wherein the instructions cause the processor to perform further acts comprising:
monitoring new requests between the system of engagement and the system of records, by an interaction observer software module;
recording, by the observer software module, the new requests between the system of engagement and the system of records as interaction metadata; and
referencing, by the coexistence layer module, the recorded interaction metadata in the conversion of the intercepted request to the second software protocol.

### Claim 20 (depends on 17)

The computing device of claim 17, wherein the instructions cause the processor to perform further acts comprising:
determining, by the computer processor, whether the intercepted request points to a system of records component that remains resident on the legacy server; and
sending the intercepted request through to the legacy server.
