Connector is a component in the Apinizer platform that enables connecting to different systems, sending data to these systems, or retrieving data from them. Connectors are used in four main areas: creating integration scenarios in API Integrator Task Flows, providing protocol conversion by creating Connector API Proxies (e.g., HTTP to MQTT), executing actions in Alarm and Monitoring situations, and sending API traffic logs to different systems. Each connector is specialized to communicate with a specific system or protocol. They can be easily used through form-based configuration without writing code.
Connection to SQL databases (MySQL, PostgreSQL, Oracle, MSSQL, DB2)SQL queries can be executed and database operations can be performed using database connections.
Linux command executionCommand and script execution on remote Linux servers via SSH.
Elasticsearch Connector is particularly important. Querying and visualizing API Traffic analytically in the Apinizer Management Console is only possible by adding the Elasticsearch Connector to the relevant environment.
Connectors are used in four main areas in the Apinizer platform:
In API Integrator Task Flows
Connections to different systems are established in Task Flows and data exchange is provided. Connectors are visually connected to create integration scenarios.
API Proxy Creation
API Proxies can be created with connectors. This enables protocol conversion such as HTTP to MQTT. For example, data can be placed in a message queue via HTTP protocol.
Alarm, Monitoring and Anomaly Detection
Used when executing actions when alarms, monitoring, and anomaly detection situations occur. Operations such as sending notifications and logging in error situations are performed.
API Traffic Logs
Used to send API traffic logs to other systems. Logs are sent to logging systems such as Elasticsearch, Graylog, Syslog.