Skip to main content

​
Overview

Central Management

Makes Connection definitions reusable in Integration Flow steps by collecting them centrally.

Multiple Database Support

Facilitates management by providing configuration from a single point for different database types (Oracle, MySQL, PostgreSQL, MongoDB, Trino, etc.).

Performance Optimization

Optimizes resource consumption in high traffic and provides consistent response time with Connection Pool parameters.

Secure Management

Supports secure deployment and audit processes with environment-based credential and JDBC URL management.

Connection Initialization

When Database connection is requested from within Integration Flow or Connector, the system reads configured connection parameters.

Connection Pool Management

Existing Connection is taken from the pool with C3P0 compatible pool strategy; if limit is exceeded, a new Connection is created.

Authentication

Authentication is performed with username/password or credential set connected to environment variable.

Data Communication

SQL/NoSQL commands are transmitted to the target Database driver via JDBC or Mongo URI and response is received.

Connection Management

After the operation is completed, Connection returns to the pool, unused connections for a long time are closed.

Error Management

In case of connection error, timeout, or authentication error, detailed error record and log routing are provided through the deployment result dialog box.

Integration Flow

Integration Flow steps that perform transactional CRUD operations via API Gateway.

Connector Scenarios

Connector scenarios that write to database after message consumption.

Scheduled Jobs

Data synchronization, reporting, and archiving tasks based on Scheduled Jobs.

DevOps Projects

DevOps teams testing environment-specific connection sets and migration projects.

​
Technical Features and Capabilities

Multiple Database Type Support

Oracle, MySQL, PostgreSQL, SQL Server, DB2, Sybase, Apache Hive/Impala, MongoDB, and Trino options are managed in a single form.

Smart JDBC URL Generation

Configuration time is shortened by automatically filling the recommended JDBC/URI template when database type changes.

Environment Variable Integration

JDBC URL, username, and password fields provide masking and autocomplete support with environment variables.

Environment-Based Configuration

Ability to define separate connection parameters for each environment (Development, Test, Production).

Enable/Disable Control

Making Connection active or passive (enable/disable toggle). In passive state, connection cannot be used but its configuration is saved.

Name Conflict Check

Unique Connection names are guaranteed with real-time name exist service.

Multiple Project Management

Connection sharing can be done thanks to the move to global project function.

Deployment Result Display

Detailed DeploymentResult dialog opens after save, enable, or test operations.

Connection Test Feature

Ability to verify connection parameters before saving with “Test Connection” button.

Export/Import Feature

Exporting Connection configuration as ZIP file. Importing to different environments (Development, Test, Production). Version control and backup capability.

Connection Monitoring

Monitoring connection health, pool status, and performance metrics.

​
Connection Parameters

Name

Description: Connection name (must be unique)
Example Value: Production_DBPool
Notes: Should not start with space, special characters should not be used

Database Type

Description: One of the supported EnumDatabaseType values
Example Value: POSTGRES
Notes: Type selection determines JDBC URL template

JDBC / Connection URL

Description: Connection string containing target Database address
Example Value: jdbc:postgresql://db-host:5432/core
Notes: Can be selected as environment variable

Use Credentials

Description: Indicates whether credentials are required
Example Value: true
Notes: Recommended for MongoDB and most JDBC drivers

Selected Environment

Description: Published environment where Connection will be applied
Example Value: Production
Notes: Must be selected for Test Connection

Description

Description: Text describing the purpose of Connection
Default Value: (Empty)
Recommended Value: Customer data ETL write

Username

Description: Database username or environment variable
Default Value: Environment variable
Recommended Value: Separate secret for each environment

Password

Description: Password or secret manager reference
Default Value: Environment variable
Recommended Value: Should be retrieved from secret manager / vault

Connection Timeout

Description: Maximum wait time for establishing connection
Default: 30000
Min: 1000 | Max: 60000
Unit: milliseconds

Request Timeout

Description: Maximum wait time for request response
Default: 30000
Min: 1000 | Max: 60000
Unit: milliseconds

Pool Size

Description: Maximum number of connections in Connection pool
Default: 5
Min: 1 | Max: 50
Unit: count

Idle Connection Test Period

Description: Health check period for connections in pool
Default: 30000
Min: 5000 | Max: 600000
Unit: milliseconds

Max Idle Time

Description: Time for closing unused connection
Default: 120000
Min: 10000 | Max: 900000
Unit: milliseconds

Max Connection Age

Description: Maximum time a connection can stay in pool
Default: 180000
Min: 60000 | Max: 3600000
Unit: milliseconds

​
Usage Scenarios

API Proxy CRUD

Situation: Writing to customer table from Gateway
Solution: POSTGRES, Pool Size=10, Test Checkout active
Expected Behavior: Sequential INSERT operations with low latency

Reporting ETL

Situation: Scheduled Job pulling night report
Solution: ORACLE, Idle Test=60000, Max Age=900000
Expected Behavior: Pool remains stable in long queries

Mongo Audit Log

Situation: Writing REST calls to MongoDB
Solution: MONGODB, Credentials off, user info in URI
Expected Behavior: Single connection is reused for each document write

Trino Data Blending

Situation: Self-service analytics flow
Solution: TRINO, Pool Size=3, Timeout=45000
Expected Behavior: Excessive load is not placed on Trino coordinator

DB2 Legacy Integration

Situation: Old core banking system
Solution: DB2, Use Credentials=true, SSL/TLS on
Expected Behavior: Transactional operations proceed securely

Large Scale Queue Drain

Situation: Bulk insert to SQL Server after Kafka consumption
Solution: SQL_SERVER, Pool Size=20, Increment=5
Expected Behavior: Multiple consumer threads are not blocked

​
Connection Configuration

​
Creating New Database Connection Pool

Image 2024 9 9 15 35 35 Pn

​
Configuration Steps

1

Going to Creation Page

  • Go to Connection → Database Connection Pool section from the left menu.
  • Click the [+ Create] button in the top right.
2

Entering Basic Information

Enable Status (Active Status):Set active/passive status with toggle. New connections are active by default.Name (Name) Required:Example: Production_DBPool
  • Enter unique name, should not start with space.
  • System automatically checks. Green checkmark: available. Red X: existing name.
Description (Description):Example: “Reporting queries of Order service”
  • Max. 1000 characters.
  • Describe the purpose of Connection.
3

Environment Selection

  • Select environment from dropdown menu: Development, Test, or Production.
  • Different connection parameters can be defined for each environment.
4

Database Type and JDBC URL

  • Select target driver from Database Type list; recommended JDBC template comes automatically.
  • Edit JDBC / Connection URL field or bind environment variable with Select Variable button.
  • Add driver-specific parameters in URL for MongoDB and Trino.
You can use the same connection for different environments using environment variable.
5

Credentials and Credentials

  • If Use Credentials is selected, username/password fields become visible.
  • Enter value for each field or select variable with environment variable autocomplete.
  • Use Credentials can be turned off for unique URI that does not require credentials (e.g., Mongo SRV).
6

Timeout and Connection Pool Settings

  • Adjust pool parameters such as Initial/Min/Max Pool Size, Increment Count, Max Statements according to traffic volume.
  • Enter Connection Timeout, Idle Connection Test Period, Max Idle Time, Max Connection Age values in milliseconds.
  • Configure Test Connection On Checkout/Checkin checkboxes for drivers other than MongoDB/Trino.
7

Security and Authentication Settings

  • Add ssl=true or similar parameter to JDBC URL for databases requiring SSL/TLS.
  • Hide secrets using environment variable for LDAP or vault-based credentials.
  • Do not use plain text password in Production environment.
Always use SSL/TLS in Production environment and manage passwords through secret manager.
8

Test Connection

  • Click [Test Connection] button.
  • Test whether connection parameters are correct.
  • Successful: Green confirmation message, Failed: Error details are shown.
9

Saving

  • Click [Save and Deploy] button in the top right.
Checklist:
  • Unique name
  • Required fields filled
  • Test connection successful (recommended)
Result:
  • Connection is added to list.
  • Becomes available for use in Integration Flow and Connector steps.
  • Becomes active according to environment.
Connection created successfully! You can now use it in Integration Flow and Connector steps.

​
Deleting Connection

Deletion Operation

Method 1: Select Delete from ⋮ menu at end of row.
Method 2: Click [Delete] button on Connection detail page.

Deletion Tips

Check Before Deleting:
  • May be used in Integration Flow or Connector steps.
  • Assign an alternative connection if necessary.
  • Backup with Export before deleting.
Alternative: Deactivate
  • Use Disable option instead of deleting.
  • Connection becomes passive but is not deleted.
  • Can be reactivated when needed.

​
Exporting/Importing Connection

In this step, users can export (export) existing connections for backup, moving to different environments, or sharing purposes, or import (import) a previously exported connection again. This operation is used to maintain data integrity in version control, transitions between test and production environments, or inter-team sharing processes.

Method 1

Select ⋮ → Export from action menu. ZIP file is automatically downloaded.

Method 2

Click [Export] button on Connection detail page. ZIP file is downloaded.

File Format

Format: {Date}-connection-{ConnectionName}-export.zip
Example: 13 Nov 2025-connection-Production_DBPool-export.zip

ZIP Contents

  • Connection JSON file
  • Metadata information
  • Dependency information (e.g., certificates, key store)

Usage Areas

  • Backup
  • Moving between environments (Test → Prod)
  • Versioning
  • Team or project-based sharing

Import Steps

  • Click [Import Database Connection Pool] button on main list.
  • Select downloaded ZIP file.
  • System checks: Is format valid? Is there name conflict? Are dependencies present?
  • Then click [Import] button.

Import Scenarios

Scenario 1: Name Conflict → Overwrite old connection or create with new name.Scenario 2: Missing Dependencies → Create missing certificates or key stores first or exclude during import.

​
Usage Areas of Connection

Creating and Activating Connection

Steps:
  1. Create Connection.
  2. Verify connection with Test Connection.
  3. Save and activate with Save and Deploy.
  4. Ensure Connection is in Enabled status.

Usage in Integration / Connector Steps

Database Connection Pool is selected from Connection field in steps requiring SQL or NoSQL data. Examples: steps like “Database Query”, “Bulk Insert”, “Metadata Lookup”.

Scheduled Job Usage

Connection is selected in scheduled ETL, reporting, or cleanup tasks to access external systems. When job is redeployed, current connection parameters are used.

Test Purpose Usage

Connection accuracy can be checked independently of Integration Flow with Connection Test feature. This test provides quick verification in pooling and credential changes.

​
Best Practices

Pool Capacity Planning

Bad: Leaving Pool Size=1 for all databases.
Good: Measuring traffic and manually adjusting min/max values.
Best: Applying peak concurrent request ×1.5 rule and providing elastic scaling with Increment Count.

JDBC URL Management

Bad: Manually writing host and port and forgetting to change in environments.
Good: Entering separate URL for each environment.
Best: Moving single form to all environments with reference using environment variable autocomplete.

Credential Storage

Bad: Entering password as plain text and sharing.
Good: Using secret manager only in production.
Best: Using secret references in all environments and planning rotation.

Consistency Between Versions

Bad: Managing different connection objects on test and prod.
Good: Copying with Export/Import.
Best: Using environment selector in single connection and putting JSON export under version control.

Environment Management

Bad: Using same connection parameters in all environments.
Good: Creating separate connection for each environment.
Best: Managing all environments in single connection using environment option, only changing environment during inter-environment transitions.

Connection Test

Bad: Saving and deploying Connection without testing.
Good: Verifying with Test Connection before saving.
Best: Testing after each parameter change, performing full integration test in test environment before moving to production.

Credential Rotation

Update passwords periodically, verify consistency by performing Test Connection in all environments after change.

Network Segmentation

Route Connection definitions to database endpoints accessible only from relevant VPC/VNet, do not use unnecessary public IP.

Permission Matrix

Assign minimum permissions to database users; only allow necessary schemas and operations, do not use DBA privileged accounts.

Credential Management

Store sensitive information such as username and password using environment variable or secret manager. Do not hardcode credentials in code or configuration files. Update passwords periodically.

SSL/TLS Usage

Always enable SSL/TLS in Production environment. Use self-signed certificates only in development environment. Track certificate expiration dates and renew on time.

Access Control

Allow only authorized users to change Connection configuration. Store Connection change logs. Apply change approval process for critical connections.

Wrong Environment Selection

Why to avoid: Risk of accessing production data from test environment.
Alternative: Verify environment dropdown before saving, use Prod_, Test_ prefixes in naming.

Excessive Pool Size

Why to avoid: Unnecessary sessions open on target Database, resources are exhausted.
Alternative: Determine Max Pool Size according to traffic metrics, update with monitoring.

Skipping Certificate Verification

Why to avoid: If SSL/TLS is off, data is transmitted as plain text.
Alternative: Add ssl=true to JDBC URL and use trusted CA certificate.

Using Production Connection in Test Environment

Why to avoid: Test data may be written to production system, real users may be affected, security risk occurs.
Alternative: Create separate connection for each environment, use environment parameter, separate connection names by adding prefix according to environment (Test_, Prod_).

Very Low Timeout Values

Why to avoid: Connection constantly times out in network delays, Integration steps fail.
Alternative: Adjust timeout values according to real usage scenarios, measure network latency and determine timeouts accordingly.

Not Using Connection Pool

Why to avoid: New connection opens on each request, performance decreases, resource consumption increases, target system load increases.
Alternative: Enable Connection pool, adjust pool size according to traffic volume, set up pool monitoring.

​
Performance Tips

Query Density Management

Recommendation: Create separate connection definitions for intensive SELECT/INSERT flows.
Effect: Reduces pool starvation risk, response times are balanced.

Read/Write Separation

Recommendation: Use different Connection for read replica and primary DB.
Effect: Replica performance is maintained, write operations are not affected.

Ready JDBC Templates

Recommendation: Edit automatically filled JDBC URLs according to project standard and save as template.
Effect: Time to open new connection shortens, error rate decreases.

Connection Pool Optimization

Recommendation: Adjust pool size according to peak traffic (recommended: concurrent request count × 1.5), set idle connection timeouts, perform pool health check.
Effect: Connection opening cost decreases by 80%, response times decrease, resource usage is optimized.

Timeout Values Optimization

Recommendation: Measure real network latency, adjust timeout values accordingly, avoid very low or very high timeouts.
Effect: Unnecessary waits are prevented, fast fail-over is provided, user experience improves.

Connection Monitoring

Recommendation: Monitor Connection pool usage, track timeout rates, perform connection health check, set up alerting.
Effect: Problems are detected proactively, performance bottlenecks are identified early, downtime decreases.

​
Troubleshooting

Host/port may be incorrect, SSL parameters may be missing, or DNS may not be resolvable.
1

URL Validation

Validate URL with ping/tnsping in test environment.
2

SSL Parameters

Add SSL parameters to JDBC string.
3

DNS Check

Update DNS record or hosts entry.
Variable expression may be incomplete, Environment service may not have returned result, or Use Credentials toggle may be wrong.
1

Syntax Check

Complete syntax in username/password field.
2

Environment Variable

Retrigger environment variable search.
3

Toggle Reset

Reset fields by closing and reopening toggle.
Network delay, target system responding slowly, or timeout value may be too low.
1

Network Check

Check network connectivity.
2

System Health

Check target system health.
3

Timeout Settings

Increase timeout values.
4

Log Review

Review Connection logs.
Wrong username/password, expired credentials, or permission problem may exist.
1

Credentials

Verify credentials.
2

User Status

Check that user is active in target system.
3

Permission Check

Check that necessary permissions are granted.
4

Certificate Check

Check SSL/TLS certificates.
Pool size may be too low, connection leak may exist, or traffic may be too high.
1

Pool Size

Increase pool size.
2

Connection Check

Check that connections are properly closed.
3

Idle Timeout

Set idle connection timeouts.
4

Metric Monitoring

Monitor Connection usage metrics.
Different connection may be selected in Integration/Connector step, step may be incorrectly configured, or Flow/Job may not have been redeployed.
1

Enable Toggle

Check that Connection’s enable toggle is active.
2

Connection Selection

Verify that correct connection is selected in Integration Flow.
3

Connection Deploy

Redeploy Connection.
4

Flow/Job Deploy

Redeploy Integration Flow or Job.
5

Log Check

Check Gateway logs.

​
Frequently Asked Questions (FAQ)

Oracle, MySQL, PostgreSQL, SQL Server, DB2, Sybase, Apache Hive/Impala, MongoDB, and Trino connections can be defined through the same form.
Yes, you can provide separate username/password references for each environment with environment dropdown and environment variable autocomplete.
No, URI field works in mongodb:// format for MongoDB and Increment Count, Max Statements fields are automatically hidden.
Test Connection On Checkout/Checkin checkboxes are active in JDBC types using c3p0 driver; they are disabled in MongoDB and Trino.
Error messages, log links, and return actions are listed in the DeploymentResult window that opens after Save/Test operation.
Yes, the same connection can be used in multiple Integration Flow or Connector steps. This provides central management and guarantees configuration consistency. However, care should be taken as changes made to connection will affect all usage locations.
Connection pool usage is not mandatory but strongly recommended in high-traffic systems. Reusing existing connections instead of opening new connection on each request significantly increases performance.
Yes, it is recommended that you create separate connection for each environment. Alternatively, you can manage all environments within a single connection using environment parameter. This approach provides easier management and less error risk.
Several reasons may exist:
  1. Connection enable toggle may be passive
  2. Different connection may be selected in Integration step
  3. Connection may not have been deployed
  4. Integration Flow may not have been redeployed yet