Everything You Need to Know

Database Server

Connection

Estimated reading: 9 minutes 57 views

Overview

The Connection Add page is used to create a new database connection profile.

Administrators must provide the database type, database name or SID, server address, port, and authentication credentials. Additional connection parameters can also be provided when required by the database driver or environment.

Connection Add Fields

Field Description
Connection Name A friendly name used to identify the connection in OneDB.
Database Type The database platform, such as MySQL, PostgreSQL, Oracle, or MSSQL.
Database Name The database name. For Oracle, this may refer to the SID or service-related value depending on the configured connection format.
IP Address The IP address or hostname of the database server.
Port The database listener port.
Username The database username used by OneDB to connect to the target database.
Password The password for the database user.
Additional Connection String Optional key-value parameters appended to the JDBC URL.
Test Connection Tests whether OneDB can connect using the provided configuration.
Submit Saves the connection profile.

Connection Name

The Connection Name field defines a friendly name for the database connection.

Use a clear name that helps administrators identify the database environment, database type, or deployment location.

Example:

mysql-local
pg-local
postgresql-local
Oracle-On-Cloud
MsSQL-On-Cloud
PostgreSQL-On-Cloud

Recommended naming convention:

<DatabaseType>-<Environment>-<Purpose>

Example:

PostgreSQL-Prod-CustomerDB
MySQL-UAT-CRM
Oracle-Dev-CoreBanking
MSSQL-Prod-HR

Database Type

The Database Type field defines the database platform used by the connection.

Supported database types include:

Database Type Description
MySQL Connects to a MySQL database.
PostgreSQL Connects to a PostgreSQL database.
Oracle Connects to an Oracle database.
MSSQL Connects to a Microsoft SQL Server database.

The selected database type determines the connection behavior and expected connection parameters.

Database Name

The Database Name field defines the target database name.

For Oracle connections, this value may be used as the SID or service-related identifier depending on the connection format supported in the environment.

Examples:

Database Type Example Value
MySQL customer_db
PostgreSQL customer_db
MSSQL customer_db
Oracle FREE / ORCL / service name or SID

Use the database name, or enter the SID if the database type is Oracle.

IP Address

The IP Address field defines the target database server address.

This can be an IP address or hostname.

Example:

127.0.0.1
192.168.10.25
db-prod.company.local

For production environments, use the database address approved by the infrastructure or database administration team.

Port

The Port field defines the database listener port.

Common default ports include:

Database Type Common Default Port
MySQL 3306
PostgreSQL 5432
Oracle 1521
MSSQL 1433

The actual port may be different depending on the database server configuration.

Username and Password

The Username and Password fields define the database credentials used by OneDB to connect to the target database.

The database user should have only the required permissions needed for the intended OneDB use case.

Recommended practice:

Recommendation Description
Use a dedicated account Create a specific database user for OneDB integration.
Apply least privilege Grant only the required permissions.
Avoid shared admin accounts Do not use highly privileged or shared database administrator accounts unless specifically required and approved.
Rotate credentials Follow the organization’s credential rotation policy.

Additional Connection String

The Additional Connection String field allows administrators to define optional key-value parameters that are appended to the JDBC URL.

This is useful when the database connection requires additional driver options, timeout values, secure connection parameters, SSL/TLS settings, or other connection-level parameters.

Example:

connectTimeout=10&socketTimeout=30

Common use cases may include:

Use Case Example Parameter
Configure connection timeout connectTimeout=10
Configure socket timeout socketTimeout=30
Configure secure connection behavior Depends on database type and JDBC driver support
Add driver-specific options Depends on database type and JDBC driver support

Parameters must follow the supported key-value format for the selected database driver. Incorrect parameters may cause the connection test or database access to fail.

Secure Connection

The Secure Connection option allows OneDB to connect to the target database using an encrypted database connection when supported and required by the database server.

This setting is used for communication between the OneDB appliance and the target database server. It is different from secure listener connections, which are used between a client application and the OneDB Listener.

When Secure Connection is enabled, OneDB will attempt to establish a secured database connection using the supported database driver configuration.

Secure Connection may be required in environments where database traffic must be encrypted across the network, especially for production, cloud, hybrid, or regulated environments.

When to Enable Secure Connection

Enable Secure Connection when the target database server requires or supports encrypted client connections.

Common use cases include:

Use Case Description
Cloud database The database provider requires or recommends encrypted connections.
Production database Database traffic must be protected between OneDB and the database server.
Cross-network connection OneDB connects to a database through a different network segment, VPN, or private link.
Compliance requirement Internal security policy requires encrypted database connections.
Untrusted network path The database connection passes through network areas where encryption is required.

Test Connection

The Test Connection button is used to verify whether OneDB can connect to the target database using the provided configuration.

Administrators should test the connection before saving or using it in production configuration.

Test Connection Result

The Test Connection function is used to verify whether OneDB can successfully connect to the target database using the configured connection settings.

To test a connection:

  1. Open the Connection Management page.
  2. Locate the connection to be tested.
  3. Click the Test Connection icon on the selected row.

OneDB will attempt to connect to the target database using the configured parameters.

Successful Connection Test

If the test is successful, a notification message will be displayed indicating that the database connection has been established successfully.

Example:

Notification
Connection database <database_type> succeed!

This indicates that OneDB was able to establish a connection to the target database successfully.

Click OK to close the notification.

Failed Connection Test

If the test fails, a notification message will be displayed indicating that the connection attempt was unsuccessful.

Example:

Oops...
Connection database <database_type> failed!

This indicates that OneDB was unable to connect to the target database using the current configuration.

Click OK to close the notification.

Possible Causes of Connection Failure

If the connection test fails, check the following items:

Area What to Check
IP Address / Hostname Confirm the database server address is reachable from the OneDB appliance.
Port Confirm the database listener port is correct and open.
Database Name / SID Confirm the database name, service name, or SID is correct.
Database Type Confirm the correct database platform is selected.
Username / Password Confirm the credentials are valid.
Additional Connection String Confirm additional parameters are valid for the selected database type.
Firewall / Network Confirm network rules allow connectivity from OneDB to the database server.
Database Service Confirm the database service is running and accepting connections.

Database Detail

The Database Detail function displays additional information about the connected database instance.

To view database details:

  1. Open the Connection Management page.
  2. Locate the required connection.
  3. Click the Database Detail icon on the selected row.

Database Detail window will be displayed.

Database Detail Information

The Database Detail window may display information such as:

Field Description
Connection ID The unique identifier of the configured database connection.
Database Product The detected database product name.
Major Version The major version of the database server.
Minor Version The minor version of the database server.
Driver Version The version of the database driver used by OneDB.
Product Version The full version information returned by the database server.

This information helps administrators verify the connected database platform and version.

How to Add a Connection

  1. Open Connection from the Database Server menu.
  2. Click Add connection.
  3. Enter the Connection Name.
  4. Select the Database Type.
  5. Enter the Database Name.
  6. Enter the database server IP Address or hostname.
  7. Enter the database Port.
  8. Enter the database Username.
  9. Enter the database Password.
  10. Add optional parameters in Additional Connection String, if required.
  11. Click Test Connection to verify connectivity.
  12. Click Submit to save the connection.

How to Edit a Connection

  1. Open Connection from the Database Server menu.
  2. Find the connection that needs to be updated.
  3. Click the Edit icon.
  4. Update the required fields.
  5. Click Test Connection if connection parameters were changed.
  6. Save the changes.

How to Delete a Connection

  1. Open Connection from the Database Server menu.
  2. Find the connection that should be removed.
  3. Click the Delete icon.
  4. Confirm the deletion if prompted.

Before deleting a connection, ensure that it is no longer used by Field Settings, Database Browser, templates, applications, or other OneDB operations.

Important Notes

  • A connection profile defines how OneDB reaches a target database server.
  • A successful connection test confirms that the OneDB appliance can reach and authenticate to the target database using the provided parameters at the time of testing.
  • A successful connection test does not guarantee that all database objects, schemas, tables, or records are accessible. Access depends on the database user permissions and database configuration.
  • Since OneDB is delivered as an OVA-based appliance, connectivity depends on the appliance network configuration, routing, firewall rules, DNS resolution, and database server availability.
  • Additional connection string parameters are appended to the JDBC URL and should only be configured by administrators who understand the selected database driver requirements.
  • Incorrect database type, database name, SID, port, credentials, or connection string parameters may cause connection failure.
  • Database credentials should be protected and managed according to the organization’s security policy.
  • Avoid using highly privileged database administrator accounts unless explicitly required and approved.

Recommended Practice

Recommendation Description
Use clear naming Name connections based on database type, environment, and purpose.
Test before saving Always test the connection before using it in configuration.
Use dedicated credentials Use a dedicated database account for OneDB.
Apply least privilege Grant only the required permissions for OneDB operations.
Validate network access Confirm that the OneDB appliance can reach the database server.
Be careful with JDBC parameters Use only supported additional connection string parameters.
Review dependencies Check whether the connection is used by Field Settings or Database Browser before deleting it.
Share this Doc

Connection

Or copy link

Table of Contents