Event controlled input agents receive data passively. An external data source supplies the data at any time. The agent responds to incoming messages, files, or connections.
Choose the input agent below that fits your scenario.
Overview
Receives messages from message-broker queues through AMQP or JMS connections. | Connects to AMQP brokers such as RabbitMQ or Apache ActiveMQ. |
Connects to JMS-compliant message brokers such as Apache ActiveMQ. | Secure B2B message exchange over HTTPS with signing and encryption. |
B2B data exchange via ebMS 3.0 with web services and WS-Security. | Receives data from the communication log for downstream processing. |
Receives data from DataCockpit forms or portals. | Reads messages from data queues on IBM AS/400 systems. |
Receives fax messages for further processing. | Receives messages from Google Cloud Pub/Sub topics. |
Fetches files from a remote server via FTP or FTPS. | Accepts data through an HTTP endpoint, for example, a web service. |
Receives telemetry data from IoT devices and sensors. | Consumes messages from Apache Kafka topics. |
Accepts files that users upload manually. | Processes internal platform messages between profiles. |
Receives messages from MQTT brokers, often used in IoT scenarios. | Classic OFTP and OFTP2 data exchange, common in the automotive industry. |
Receives IDocs from SAP systems via ALE and RFC. | Accepts messages and attachments via SMTP. |
Transfers files securely over SSH using SCP or SFTP. | Receives data through a direct TCP connection. |