Match your installation
Find the application and database you run. Use the connection details to locate the settings for your deployment.
Application compatibility
No application code changes required. Connect your application to EngineGrids Accelerator using its existing database connection settings.
Find your application, choose your deployment and database, and follow the connection steps for your environment.
Try another name, choose a different database, or clear the filters. If your application is not listed, tell us what you use.
Craft 5 accepts CRAFT_DB_DRIVER, CRAFT_DB_SERVER and CRAFT_DB_PORT in the environment, or equivalent values in config/db.php.
The self-hosted data platform uses DB_CLIENT to select its database and DB_HOST, DB_PORT, DB_DATABASE and account variables for the connection.
The site settings.php file defines the primary connection in $databases, including driver, host, port, database and credentials.
Ghost reads its MySQL client, host, port and credentials from the database section of config.production.json or corresponding environment variables.
The deployment datasource configuration sets database type, server name, port and database; Oracle uses a JDBC URL.
The Joomla installer selects the database type, host and account; those site-wide settings are stored in configuration.php and managed through Global Configuration.
LocalSettings.php sets the wiki database endpoint with $wgDBserver; MySQL accepts host:port, while PostgreSQL has a separate $wgDBport setting.
Strapi 5 config/database.js or config/database.ts reads DATABASE_CLIENT, DATABASE_HOST, DATABASE_PORT and account settings from the application environment.
Set the Default database connection under DB/Connections in config/system/settings.php or the additional environment configuration, including driver, host and port.
WordPress stores its database name, account and network endpoint in wp-config.php; DB_HOST accepts a host and alternate port.
Adobe Commerce’s customer-managed deployment configures the store database with --db-host, --db-name and account settings; --db-host accepts a network hostname and port.
The Commerce installer accepts --db-host with an optional port plus the database name and account. The storefront’s MySQL connection serves its catalog, customer and order data.
Enter the store’s database connection details in the installation Configuration step. OpenCart maintains configuration files for the storefront and administration application.
PrestaShop keeps its store database connection details in parameters.php; the installer initially records the database chosen for the shop.
Shopware connects through DATABASE_URL, which includes the database account, host, port and name; separate environment variables configure database TLS certificates.
The Sylius application’s DATABASE_URL chooses a MySQL or PostgreSQL connection and supplies its server, account and database through environment configuration.
WooCommerce uses the WordPress database connection. Set its server and port through DB_HOST in the site’s wp-config.php, alongside the existing database name and account.
Review CIVICRM_DSN in civicrm.settings.php, which identifies the database server, database, and credentials used by CiviCRM.
Set the database platform, host, and port through ESPOCRM_DATABASE_PLATFORM, ESPOCRM_DATABASE_HOST, and ESPOCRM_DATABASE_PORT in the Docker deployment.
Dynamics Server Setup and Deployment Manager use a configured SQL Server computer and instance.
Siebel Management Console database settings select the RDBMS and accept an Oracle connect string, SQL Server host/port/database, or Db2 database alias.
Review the installation wizard’s Database Configuration host, database name, and application database credentials.
Supply the MySQL database hostname and database account in the Vtiger installation database configuration.
Run the ADempiere server setup utility and set Database Server, Database Type, Database Port, Database Name, and the application account.
Configure the selected datasource and its inline JDBC URI in framework/entity/config/entityengine.xml, then map the application delegator to that datasource.
Use the database connection selected in the Dolibarr installer and maintained in conf/conf.php for the ERP/CRM database.
Use the server setup utility’s database type, server hostname, port, database name, and account fields; the saved environment properties drive server startup.
Set DatabaseServer, DatabaseInstance and DatabaseName for the application database. For a multitenant deployment, also configure the database connections for mounted tenants.
The GP client's SQL Server ODBC system DSN identifies the server and authentication details.
Configure the PostgreSQL endpoint with db_host and db_port in the Odoo server configuration, keeping the existing database name and account.
Use EBS context settings and AutoConfig to configure the application tier’s Oracle database connections, including JDBC/DBC and native Oracle Net endpoints.
EPM System Configurator configures product repository connections and permits an explicit JDBC URL override.
EnterpriseOne data sources specify Oracle connect strings, SQL Server ODBC databases, or Db2 client data sources and aliases.
Deployment Package configuration specifies the database platform, SQL Server name or Oracle service name, and database host and port.
Register the database server with its host or IP address, instance and optional non-default port in System Landscape Directory.
Use the installed SAP database interface to set the runtime endpoint for SQL Server or Oracle. Configure CLI for ABAP, JDBC for Java and db2cli.ini for Db2 LUW deployments.
Set the database URI in the Tryton server configuration or TRYTOND_DATABASE_URI, using the PostgreSQL host and port in the URI.
Confluence Setup establishes an external JDBC connection; an administrator can configure a supported JDBC URL or JNDI datasource.
Configure the production section of config/database.yml for the Canvas PostgreSQL server; the application and database can run on separate hosts.
Discourse’s production configuration accepts DISCOURSE_DB_HOST and DISCOURSE_DB_PORT, with the database name and account set through the same environment-variable scheme.
LimeSurvey’s application/config/config.php holds its database connectionString, account and password; the DSN identifies the database server, port and database.
Set the application database connection through SqlSettings.DataSource in config.json or MM_SQLSETTINGS_DATASOURCE, using a PostgreSQL connection URI.
Moodle’s installer records the selected database server, hostname, database name and account in config.php for the learning site.
The installation wizard writes the database endpoint and account to config/config.php; dbhost supports hostname:port. Oracle connections use Nextcloud’s enterprise database integration.
Tutor supports an external MySQL service through RUN_MYSQL, MYSQL_HOST and MYSQL_PORT, alongside the Open edX database account and name.
ownCloud Server configures database host and account in config/config.php or occ maintenance:install. Its Oracle enterprise deployment also accepts an Oracle connection string.
The Docker deployment exposes SEAFILE_MYSQL_DB_HOST and SEAFILE_MYSQL_DB_PORT plus account and database-name variables for its Seafile, Seahub and ccnet databases.
Install the database driver and SQLAlchemy dialect, then configure the SQLAlchemy connection URI with the business database host, port, and database.
Choose Data Sources → Add Data Source, select the engine, and enter the host, port, database name, and reporting account.
Use Connections → Data sources to add the MySQL, PostgreSQL, or Microsoft SQL Server connection, then select it for panels and queries.
Administrators create data-server connections and configure vendor JDBC URLs or native database connections.
Choose Create → Data Source → JDBC Data Source, select the database driver, and enter the hostname/database or JDBC URL; use Test Connection before saving.
Open Admin → Databases → Add a database and configure the business database connection used by questions and dashboards.
Configuration repository: set MB_DB_TYPE, MB_DB_HOST, MB_DB_PORT, MB_DB_DBNAME, MB_DB_USER, and MB_DB_PASS, or MB_DB_CONNECTION_URI, when starting the self-managed Metabase service.
Report definitions and server data-source settings select relational endpoints and credentials for queries or scheduled refresh.
Report data sources contain an editable connection string and credentials for the selected database provider.
The connectivity wizard and database connection objects configure a database DSN and stored credentials.
A configured Db2 LUW DSN can also serve MicroStrategy metadata operations.
Administrators create JDBC report data sources with the chosen driver, connection string, and database credentials.
Create a database connection, choose the database type and Native (JDBC), then set Host Name, Database Name, Port Number, and the database account.
The Data Load Editor uses a configured database connector or ODBC DSN pointing to the database endpoint.
Open Settings → Data Sources and define the query connection. Set the host, port, database name, and credentials for a TCP/IP connection to Db2.
Published data sources use database connectors with configurable server, database, port and credentials.
Configure sql_alchemy_conn in the database section or AIRFLOW__DATABASE__SQL_ALCHEMY_CONN with the chosen database URI.
Jira's setup/configuration tool or dbconfig.xml defines the external database connection.
Installation accepts the database host and database-specific port/service connection parameters for customer-supplied databases.
Deployment configuration selects DB_TYPE and supplies a JDBC URL or database hostname, port and service name.
Set DB_TYPE and HOST in the database section of Forgejo’s configuration, then retain the matching database name and account settings.
Set DB_TYPE, HOST, NAME, USER, and PASSWD in the database section of app.ini; HOST contains the database address and port.
Use php bin/console db:configure with --db-host, --db-port, --db-name, and the database account to maintain the GLPI database connection.
BPMConfig properties control database data sources; the documented update process exports and edits database host, port, database name or Oracle URL.
The MDM installation records the operational database endpoint and credentials; virtual MDM database connectivity is configured in its ODBC settings.
The Manage deployment's Database connection settings accept a JDBC connection string, username, password, and driver options.
PowerCenter Repository Service uses configurable native database connect strings for its repository database.
Workflow Manager connection objects configure relational databases queried as data-integration sources and written as targets.
Set DatabaseType, DatabaseHost, DatabasePort, DatabaseName, and the database account in Request Tracker’s site configuration.
Configure sonar.jdbc.url or SONAR_JDBC_URL with the database endpoint, using the matching JDBC username/password settings.
Set DBHost, DBPort, DBName and DBUser in zabbix_server.conf, and configure the same database endpoint in the web frontend setup.
Configure DatabaseHost, Database, DatabaseUser, DatabasePw, and the engine-specific DatabaseDSN in Kernel/Config.pm.
Find the application and database you run. Use the connection details to locate the settings for your deployment.
Use the Accelerator address in your existing database connection settings. Keep your application, driver, and database. Your database remains the system of record.
Evaluate EngineGrids in your own environment to compare application performance and database demand.
EngineGrids supports MySQL, MariaDB, PostgreSQL, Microsoft SQL Server, Oracle Database and IBM Db2. Configure read scope and write behavior for the selected engine.
Tell us the application, its database, and how you run it. We can help you plan a connection and evaluation.