Table Of Contents
- Introduction
- Creating and maintaining outgoing configurations
- Monitoring outgoing configurations
- Video guide
Introduction
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.
Note: When using an HTTP Publisher, for example, you will face its own settings for adding an Outgoing configuration such as request URI, or form encoder where the only “Form URI encoder” is available for now. Once selected, you are able to choose which encoding type you need:
- RFC 1738 “Spaces to +” - encoding space to “+” option.
- RFC 3986 “Spaces to %20” - sending JSON inside the URL of the particular perimeter.
However, please pay attention that the URL encoding is only applied when it receives an array. This is the case when a payload of the type object is given. The arguments also only get added with the HTTP method - GET. This only applies to cases when RFC 3986 “Spaces to %20” is selected.
- Entity transformers - The transformers 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.
Video guide
