IP Library › Granted Patent US 12683944

Granted Patent B2

US 12683944 · App. 18/772,498 · Granted Jul 14, 2026

Connector deployment within a connectivity framework

Inventors: Christian Schmitz (Porto Alegre, BR); Peter Schoenau (Stuttgart, DE); Silvio Normey Gomez (Santana do Livramento, BR); Mitchell Gudmundson (Colorado Springs, CO)

Assignee: SAP SE

H04L63/08 H04L41/12 H04L63/029

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 12683944
App. No.: 18/772,498
Granted: Jul 14, 2026
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Systems and methods include execution of a first instance of a connector registry service to receive a first registration request from a first instance of a first connector to a first data system, the first registration request comprising a first connector identifier, a first connection type and a first endpoint type, store the first connector identifier, the first connection type and the first endpoint type in a data store, read a plurality of associated connector identifiers, connection types and endpoint types from the data store, the plurality of associated connector identifiers, connection types and endpoint types including the first connector identifier, the first connection type and the first endpoint type, and transmit the plurality of associated connector identifiers, connection types and endpoint types to a first instance of a gateway service.

Claims (101)

1 . A system comprising:

a memory storing program code;

one or more processing units to execute the program code to:

execute a first instance of a connector registry service to:

receive a first registration request from a first instance of a first connector to a first data system, the first registration request comprising a first connector identifier, a first connection type and a first endpoint type;

store the first connector identifier, the first connection type and the first endpoint type in a data store;

read a plurality of associated connector identifiers, connection types and endpoint types from the data store, the plurality of associated connector identifiers, connection types and endpoint types including the first connector identifier, the first connection type and the first endpoint type; and

transmit the plurality of associated connector identifiers, connection types and endpoint types to a first instance of a gateway service.

2 . A system according to claim 1 , the one or more processing units to execute the program code to cause the system to:

convert the plurality of associated connector identifiers, connection types and endpoint types from a data model of the first connector to a data model of the gateway service,

wherein transmission of the plurality of associated connector identifiers and connection types comprises transmission of the converted plurality of associated connector identifiers and connection types.

3 . A system according to claim 1 , the one or more processing units to execute the program code to cause the system to:

execute a second instance of the connector registry service to:

read the plurality of associated connector identifiers, connection types and endpoint types from the data store; and

transmit the plurality of associated connector identifiers, connection types and endpoint types to a second instance of the gateway service and to a third instance of the gateway service.

4 . A system according to claim 3 , the one or more processing units to execute the program code to cause the system to:

receive a second request from a second instance of the first connector for connection details associated with the first connector identifier;

in response to the second request, determine a hostname, port and user credentials associated with the first connector identifier; and

return the hostname, port and user credentials to the second instance of the first connector.

5 . A system according to claim 4 , wherein determination of the hostname, port and user credentials associated with the first connector identifier comprises:

determination of whether the hostname, port and user credentials associated with the first connector identifier are not stored in a cache of the system; and

in response to the determination, requesting of the hostname, port and user credentials associated with the first connector identifier from a second system.

6 . A system according to claim 1 , the one or more processing units to execute the program code to cause the system to:

receive a second request from a second instance of the first connector for connection details associated with the first connector identifier;

in response to the second request, determine a hostname, port and user credentials associated with the first connector identifier; and

return the hostname, port and user credentials to the second instance of the first connector.

7 . A system according to claim 6 , wherein determination of the hostname, port and user credentials associated with the first connector identifier comprises:

determination that the hostname, port and user credentials associated with the first connector identifier are not stored in a cache of the system; and

in response to the determination that the hostname, port and user credentials associated with the first connector identifier are not stored in the cache of the system, requesting of the hostname, port and user credentials associated with the first connector identifier from a second system.

8 . A system according to claim 1 , the one or more processing units to execute the program code to:

execute a second instance of the connector registry service to:

read the plurality of associated connector identifiers, connection types and endpoint types from the data store; and

transmit the plurality of associated connector identifiers, connection types and endpoint types to a second instance of the gateway service; and

execute a third instance of the connector registry service to:

receive a second registration request from a first instance of a second connector to a second data system, the second registration request comprising a second connector identifier, a second connection type and a second endpoint type;

store the second connector identifier, the second connection type and the second endpoint type in the data store;

read a second plurality of associated connector identifiers, connection types and endpoint types from the data store, the second plurality of associated connector identifiers, connection types and endpoint types including the second connector identifier, the second connection type and the second endpoint type; and

transmit the second plurality of associated connector identifiers, connection types and endpoint types to a third instance of the gateway service.

9 . A system according to claim 8 , the one or more processing units to execute the program code to:

execute the second instance of the connector registry service to:

read the second plurality of associated connector identifiers, connection types and endpoint types from the data store; and

transmit the second plurality of associated connector identifiers, connection types and endpoint types to the second instance of the gateway service; and

execute the first instance of the connector registry service to:

read the second plurality of associated connector identifiers, connection types and endpoint types from the data store; and

transmit the second plurality of associated connector identifiers, connection types and endpoint types to the first instance of the gateway service.

10 . A method comprising:

receiving, at a first instance of a connector registry service, a first registration request from a first instance of a first connector to a first data system, the first registration request comprising a first connector identifier and a first connection type;

storing, by the first instance of the connector registry service, the first connector identifier and the first connection type in a data store;

reading, by the first instance of the connector registry service, a plurality of associated connector identifier and connection types from the data store, the plurality of associated connector identifiers and connection types including the first connector identifier and the first connection type; and

transmitting, by the first instance of the connector registry service, the plurality of associated connector identifiers and connection types to a first instance of a gateway service and to a second instance of the gateway service.

11 . A method according to claim 10 , further comprising:

converting, by the first instance of the connector registry service, the plurality of associated connector identifiers and connection types from a data model of the first connector to a data model of the gateway service,

wherein transmitting the plurality of associated connector identifiers and connection types comprises transmitting, by the first instance of the connector registry service, the converted plurality of associated connector identifiers and connection types.

12 . A method according to claim 10 , further comprising:

executing a second instance of the connector registry service to:

read the plurality of associated connector identifiers and connection types from the data store; and

transmit the plurality of associated connector identifiers and connection types to a third instance of the gateway service.

13 . A method according to claim 12 , further comprising:

receiving, at the second instance of the connector registry service, a second request from a second instance of the first connector for connection details associated with the first connector identifier;

in response to the second request, determining, by the second instance of the connector registry service, a hostname, port and user credentials associated with the first connector identifier; and

returning, by the second instance of the connector registry service, the hostname, port and user credentials to the second instance of the first connector.

14 . A method according to claim 13 , wherein determining the hostname, port and user credentials associated with the first connector identifier comprises:

determining, by the second instance of the connector registry service, whether the hostname, port and user credentials associated with the first connector identifier are not stored in a cache; and

in response to the determination that the hostname, port and user credentials associated with the first connector identifier are not stored in the cache, requesting, by the second instance of the connector registry service, the hostname, port and user credentials associated with the first connector identifier from a system.

15 . A method according to claim 10 , further comprising:

receiving, at the first instance of the connector registry service, a second request from a second instance of the first connector for connection details associated with the first connector identifier;

in response to the second request, determining, by the first instance of the connector registry service, a hostname, port and user credentials associated with the first connector identifier; and

returning, by the first instance of the connector registry service, the hostname, port and user credentials to the second instance of the first connector.

16 . A method according to claim 15 , wherein determining the hostname, port and user credentials associated with the first connector identifier comprises:

determining that the hostname, port and user credentials associated with the first connector identifier are not stored in a cache; and

in response to the determination that the hostname, port and user credentials associated with the first connector identifier are not stored in the cache, requesting the hostname, port and user credentials associated with the first connector identifier from a system.

17 . A method according to claim 10 , further comprising:

executing a second instance of the connector registry service to:

read the plurality of associated connector identifiers, connection types and endpoint types from the data store; and

transmit the plurality of associated connector identifiers and connection types to a third instance of the gateway service; and

execute a third instance of the connector registry service to:

store the second connector identifier and the second connection type in the data store;

read a second plurality of associated connector identifiers and connection types from the data store, the second plurality of associated connector identifiers and connection types including the second connector identifier and the second connection type; and

transmit the second plurality of associated connector identifiers and connection types to a fourth instance of the gateway service.

18 . A method according to claim 17 , further comprising:

executing the second instance of the connector registry service to:

read the second plurality of associated connector identifiers and connection types from the data store; and

transmit the second plurality of associated connector identifiers and connection types to the third instance of the gateway service; and

execute the first instance of the connector registry service to:

read the second plurality of associated connector identifiers and connection types from the data store; and

transmit the second plurality of associated connector identifiers and connection types to the first instance of the gateway service and to the second instance of the gateway service.

19 . One or more non-transitory computer-readable media storing program code that, when executed by a computing system, cause the computing system to perform operations comprising:

storing, by the first instance of the connector registry service, the first connector identifier and the first connection type in a data store;

receiving, at a second instance of the connector registry service, a second registration request from a first instance of a second connector to a second data system, the second registration request comprising a second connector identifier and a second connection type;

storing, by the second instance of the connector registry service, the second connector identifier and the second connection type in the data store;

reading, by the second instance of the connector registry service, a second plurality of associated connector identifiers and connection types from the data store, the second plurality of associated connector identifiers and connection types including the second connector identifier and the second connection type; and

transmitting, by the second instance of the connector registry service, the second plurality of associated connector identifiers and connection types to a third instance of the gateway service,

wherein the first instance of the connector registry service reads the second plurality of associated connector identifiers and connection types from the data store and transmits the second plurality of associated connector identifiers and connection types to the first instance and the second instance of the gateway service.

20 . One or more non-transitory computer-readable media according to claim 19 , where the program code, when executed by a computing system, causes the computing system to perform operations comprising:

in response to the second request, determining, by the first instance of the connector registry service, a hostname, port and user credentials associated with the first connector identifier; and

returning, by the first instance of the connector registry service, the hostname, port and user credentials to the second instance of the first connector.