The adapter toolkit provides numerous transporter modules that come standard with Event Stream Processor. You can re-use these modules to create a custom adapter instance.
Input transporters obtain data from external data sources and output this data into Event Stream Processor. The format of this output data is specified in the Output Datatype column of the table below.
AdapterRow is a container for one or more records or rows as they flow from one module (transporter, formatter, or ESP connector) to the next. You can add multiple records as objects within a List of a single AdapterRow object. The AdapterRow has a timestamp and block flags that control how its records are communicated to and from Event Stream Processor. See Envelopes and Transactions for additional details.
AepRecord is the class that represents stream records. This is the type that the ESP publisher expects as the data member in the AdapterRow instances that it receives from the previous module. This is also the type used in the AdapterRow instances that the ESP subscriber passes on to the next module.
Name | Mode (Streaming/Row) | Output Datatype | Description |
---|---|---|---|
File Input Transporter | Can be both (depends on configuration) | Java.lang.String or Java.nio.ByteBuffer |
In row mode, the transporter reads data from local files, wraps data with string, and sends it to the next module that is configured in the adapter configuration file. In streaming mode, the transporter reads data from local files, wraps it with ByteStream, and passes it to the next module that is configured in the adapter configuration file. |
FTP Input Transporter | Streaming | Java.nio.ByteBuffer |
Reads binary data from files on an FTP server, wraps it up with ByteStream, and passes it to the next module that is configured in the adapter configuration file. |
JDBC Input Transporter | Row | Java.util.List<Java.lang.Object> |
Reads database records from a database using JDBC, and sends data records to the next module that is configured in the adapter configuration file. |
JMS Input Transporter | Row | Java.lang.String or AepRecord or Java.util.List<Java.lang.Object> |
Receives JMS messages from a JMS server, and sends this data to the next module that is configured in the adapter configuration file. |
Socket Input Transporter | Streaming | Java.nio.ByteBuffer |
Reads binary data from a socket interface, wraps it with ByteStream, and passes it to the next module that is configured in the adapter configuration file. |
Output transporters obtain data from Event Stream Processor and output it to external data sources. The format of this input data is specified in the Input Datatype column of the table below.
Name | Mode (Streaming/Row) | Input Datatype | Description |
---|---|---|---|
File Output Transporter | Both (depends on configuration) | Java.lang.String or Java.nio.ByteBuffer |
In row mode, the transporter obtains string data from the previous module configured in the adapter configuration file, and writes this data to a local file. In streaming mode, the transporter obtains ByteStream data from the previous module configured in the adapter configuration file, and writes this data to a local file. |
FTP Output Transporter | Streaming | Java.nio.ByteBuffer |
Obtains ByteStream data from the previous module that is configured in the adapter configuration file, and saves it to a file on an FTP server. |
JDBC Output Transporter | Row | Java.util.List<Java.lang.Object> |
Obtains row-based data from the previous module that is configured in the adapter configuration file, and saves it into a database table using JDBC. |
JMS Output Transporter | Row | Java.lang.String or AepRecord or Java.util.List<Java.lang.Object> |
Obtains data from the previous module that is configured in the adapter configuration file and sends it to a JMS server. |
Socket Output Transporter | Streaming | Java.nio.ByteBuffer |
Obtains ByteStream data from the previous module that is configured in the adapter configuration file, and outputs it through a socket interface. |