Table of contents
- Creating and maintaining outgoing configurations
- Monitoring outgoing configurations
- Video guide
Outgoing configurations define how data should be sent to an (external) system. Examples of such systems are (s)FTP directories, REST APIs, and databases. Outgoing configurations can be reused for multiple integrations. To do so, you can select the same outgoing configuration within multiple route configurations.
Outgoing configurations can be created and maintained by navigating to Connections -> Outgoing.
Creating and maintaining outgoing configurations
Possible configuration fields:
- Name - A name describing the connectivity this configuration enables, i.e. Create SAP Order
- Identifier - A unique identifier for this outgoing configuration (this field is automatically generated based on the name).
- Description - Detailed description for the outgoing configuration.
- Disabled - A flag that indicates whether the outgoing configuration is disabled. Disabled outgoing configurations do not process data.
- Publisher - The publisher is the technical component performing the communication with the (external) system.
- Entity transformers - The transformers which should be executed on the data flowing through this integration.
Monitoring outgoing configurations
All logging related to outgoing configurations is stored under the corresponding route configurations. You can find these logs by following the steps described here.