# US 12,216,627 B2 · Systems and methods for providing a database driver management architecture

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

- Number: US 12,216,627 B2
- Document ID: US12216627B2
- Status: Granted
- Kind: B2
- Application number: 18/446,144
- Filed: 2023-08-08
- Published: 2024-12-26
- Granted: 2025-02-04
- Earliest claimed: 2023-06-23
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: Jpmorgan Chase Bank, N.A.
- Inventors: Karthik Anagurti; Kamal Pande; Kiran Kumar Macherla; Kajal Gorai; Scott R Stevens
- Web page: https://patentgrep.com/patent/US12216627B2

## CPC

- G06F 16/217: {Database tuning (G06F16/2282 takes precedence; database performance monitoring G06F11/3409)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In some aspects, the techniques described herein relate to a method including: receiving, at a client computer, a driver script file; creating, by the driver script file, a use-case specific directory; creating, by the driver script file, an application parameters file; retrieving, by the driver script file, a core configuration script file; determining, by the core configuration script file, a required database driver; retrieving, by the core configuration script file, the required database driver; retrieving, by the core configuration script file, a database driver configuration file for the required database driver; populating, by the core configuration script file, the database driver configuration file with a plurality of entries, wherein the plurality of entries in the database driver configuration file comprise entries based on a user input; and validating, by the core configuration script file, a connection defined by the database driver configuration file.

## Claims

### Claim 1

A method comprising:
executing, on a client computer, a core configuration script file, wherein the core configuration script file scans the client computer for a required database driver based on a connectivity requirement;
determining, by the core configuration script file, that the required database driver is not present on the client computer;
retrieving, by the core configuration script file, the required database driver;
retrieving, by the core configuration script file, a database driver configuration file for the required database driver;
populating, by the core configuration script file, the database driver configuration file with a plurality of entries, wherein the plurality of entries in the database driver configuration file comprise entries based on a user input; and
validating, by the core configuration script file, a connection defined by the database driver configuration file, wherein validating the connection includes connecting to a selected database using the required database driver and a database-specific standard query.

### Claim 2 (depends on 1)

The method of claim 1, wherein the user input includes the selected database, and a selected client application to connect to the selected database.

### Claim 3 (depends on 1)

The method of claim 1, comprising:
creating, by the core configuration script file, a database-specific file.

### Claim 4 (depends on 1)

The method of claim 1, wherein validating the connection includes creating a connection string based on the plurality of entries in the database driver configuration file.

### Claim 5 (depends on 1)

The method of claim 1, comprising:
determining, by the core configuration script file, that the connection to the selected database is not operative in response to an unsuccessful validation; and
raising, by the core configuration script file, a support with a technical support platform.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
receiving, at the client computer, a driver script file; and
executing the driver script file.

### Claim 7 (depends on 6)

The method of claim 6, comprising:
creating, by the driver script file, a use-case specific directory.

### Claim 8 (depends on 7)

The method of claim 7, comprising:
creating, by the driver script file, an application parameters file.

### Claim 9 (depends on 8)

The method of claim 8, comprising:
retrieving, by the driver script file, the core configuration script file from an artifact repository.

### Claim 10 (depends on 6)

The method of claim 6, comprising:
creating, by the driver script file, a base project directory.

### Claim 11

A method comprising:
executing, on a client computer, a core configuration script file, wherein the core configuration script file receives an identification of a required database driver from a first user input and scans the client computer for a required database driver based on a connectivity requirement;
determining, by the core configuration script file, that the required database driver is not present on the client computer;
retrieving, by the core configuration script file, the required database driver;
retrieving, by the core configuration script file, a database driver configuration file for the required database driver;
populating, by the core configuration script file, the database driver configuration file with a plurality of entries, wherein the plurality of entries in the database driver configuration file comprise entries based on a second user input; and
validating, by the core configuration script file, a connection defined by the database driver configuration file, wherein validating the connection includes connecting to a selected database using the required database driver and a database-specific standard query.

### Claim 12 (depends on 11)

The method of claim 11, wherein the second user input includes the selected database, and a selected client application to connect to the selected database.

### Claim 13 (depends on 11)

The method of claim 11, comprising:
creating, by the core configuration script file, a database-specific file.

### Claim 14 (depends on 11)

The method of claim 11, wherein validating the connection includes creating a connection string based on the plurality of entries in the database driver configuration file.

### Claim 15 (depends on 11)

The method of claim 11, comprising:
determining, by the core configuration script file, that the connection to the selected database is not operative in response to an unsuccessful validation; and
raising, by the core configuration script file, a support with a technical support platform.

### Claim 16 (depends on 11)

The method of claim 11, comprising:
receiving, at the client computer, a driver script file; and
executing the driver script file.

### Claim 17 (depends on 16)

The method of claim 16, comprising:
creating, by the driver script file, a use-case specific directory.

### Claim 18 (depends on 17)

The method of claim 17, comprising:
creating, by the driver script file, an application parameters file.

### Claim 19 (depends on 18)

The method of claim 18, comprising:
retrieving, by the driver script file, the core configuration script file from an artifact repository.

### Claim 20 (depends on 16)

The method of claim 16, comprising:
creating, by the driver script file, a base project directory.