Ana içeriğe geç

Supported Databases and Third-Party Integrations

Supported Databases

Apinizer supports multiple database types via JDBC and Mongo URI. All database connections provide optimized performance with pool management.

Relational Databases

MySQL

Driver: mysql-connector-j v8.0.33

Connection support to MySQL databases via JDBC.

PostgreSQL

Driver: postgresql v42.7.10

Connection support to PostgreSQL databases via JDBC.

Oracle

Driver: ojdbc11 v21.5.0.0

Connection support to Oracle databases via JDBC.

Microsoft SQL Server

Driver: mssql-jdbc v13.2.1

Connection support to Microsoft SQL Server databases via JDBC.

IBM DB2

Driver: jcc v12.1.3.0

Connection support to IBM DB2 databases via JDBC.

Sybase

Driver: jconn4 v15.7.0.4

Connection support to Sybase databases via JDBC.

NoSQL and Big Data Databases

MongoDB

Driver: Spring Data MongoDB

Connection support to MongoDB clusters via Mongo URI.

Apache Hive

Driver: HiveJDBC42 v2.6.30

Connection support to Apache Hive databases via JDBC.

Apache Impala

Driver: ImpalaJDBC42 v2.6.38

Connection support to Apache Impala databases via JDBC.

Trino

Driver: trino-jdbc v479

Connection support to Trino databases via JDBC.

Supported Third-Party Integrations

Message Queue Systems

Apache Kafka

Version: v3.4.0

Apache Kafka message queue integration

  • Topic-based message sending and consumption
  • SSL/TLS security support
  • Message queue management for event-driven architectures
RabbitMQ

Version: v5.16.0

RabbitMQ message broker integration

  • AMQP protocol support
  • Queue and exchange management
  • Asynchronous messaging operations
Apache ActiveMQ

Version: v5.12.3

Apache ActiveMQ message broker integration

  • JMS protocol support
  • Queue and topic management
  • Message queue operations

Search and Data Systems

Elasticsearch

Elasticsearch cluster integration

  • REST-based log, metric, and search data
  • Index and lifecycle management
  • Central cluster connections
LDAP/Active Directory

Version: v2.0.2

LDAP and Active Directory integration

  • SSL/TLS protected connection
  • Access with pool management
  • Integration with enterprise directory services

Logging and Monitoring Systems

Graylog

Version: v1.5.1

Graylog GELF integration

  • Central log collection in GELF format
  • Transmission with TCP/UDP
  • Log aggregation and analysis
Syslog

Syslog protocol integration

  • Sending syslog messages
  • Central logging support
  • RFC 5424 standard support
Logback

Logback logging integration

  • Log records with Logback framework
  • Log management and routing
  • Appender configuration
SNMP

Version: v2.8.18

SNMP protocol integration

  • Sending SNMP traps
  • Network monitoring operations
  • SNMP v1/v2/v3 support

Communication and File Systems

SMTP/Email

Email server integration

  • Notification via TLS-enabled SMTP
  • Alarm and bulk email sending
  • Email templates and management
FTP/SFTP

FTP/SFTP file transfer

  • FTP/SFTP/FTPS protocols
  • Secure file transfer
  • Directory management and automatic retry
Webhook

HTTP webhook integration

  • HTTP webhook connections
  • Event-driven operations
  • REST API calls
Linux Script

Linux script execution

  • Running commands on remote Linux servers via SSH
  • Script execution support
  • DevOps automation

Connection Pool Management

All database connections are optimized with pool management:

Performance Optimization
  • Connection performance is optimized
  • Resource usage is kept under control
  • Connection count can be limited
Configuration
  • Minimum and maximum connection counts
  • Connection timeout settings
  • Connection test and validation
ipucu

Database connections are optimized and resource usage is kept under control thanks to connection pool management. This provides high performance and scalability.

Connection Configuration

The following information is defined when creating a connection:

Basic Information
  • Connection Name: Unique name identifying the connection
  • Connection Type: Database, message queue, etc.
  • Description: Descriptive information about the connection (optional)
Connection Information
  • Host/URL: Server address or connection URL
  • Port: Connection port (varies by connection type)
  • Database Name: Database name (for database connections)
  • JDBC URL: JDBC URL for database connections
  • Mongo URI: Mongo URI for MongoDB connections
Authentication
  • Username: Username for connection
  • Password: Password for connection (stored encrypted)
  • Credential Usage: Whether credentials will be used
Advanced Settings
  • Pool Settings: Minimum and maximum connection counts
  • Timeout Settings: Connection and query timeout values
  • SSL/TLS Settings: Secure connection configuration
  • Environment-Based Management: Dynamic configuration with environment variables

Usage Areas

Connections are used in various areas in the Apinizer platform:

DB-2-API

Creating APIs from database

APIs can be instantly created with DB-2-API using database connections.

Policies

Policies running database queries

Queries can be run using database connections within policies.

API Integrator

Task flows containing database operations

Integration scenarios can be created using database connections in Task Flows.

Connectors

Connectors requiring database and system connection

Connectors provide integration with different systems using connections.

API Traffic Logging

Sending API traffic logs to log systems

Connections are used to send logs to systems like Elasticsearch, Graylog, Syslog.

Alarm and Monitoring

Sending alarms to monitoring systems

Connections are used to send alarms and monitoring data to systems like SNMP, Syslog.

Security

Connection information is securely stored in Apinizer's Secret Manager:

Encryption
  • Connection passwords are stored encrypted
  • Secure credential management
  • Environment-based security settings
Access Control
  • Role-based access control
  • Connection test and validation
  • Audit logging support
uyarı

Connection information is sensitive data. Connection passwords and credentials are stored securely and encrypted. Appropriate permissions are required to access connection information.

Next Steps