< Back
Print

Stations

To start our first export, we need to create and configure a station.

Concept

A station represents a destination for our data. Just like a train station, our connector station can accept different kinds of payloads, which we will configure later. Each shop-system or custom system URL (e.g. for JSON or XML) will need it’s own station. The station configuration will contain information about where to send the data. It will also contain information such as authentication credentials.

Creating Your First Station

Go ahead and create a new station. Click this button to open the connector and station management.

Select your desired connector. In this instance, the GenericJSON Connector is selected. The configuration structure is the same for every connector.

You can create a new station from scratch or select a predefined template. Our team offers station templates with various sub-configurations for each connector. Keep in mind that these templates serve as a starting point and may differ significantly from your specific requirements. For this tutorial, we will continue with a blank station.

Selecting your newly created station will forward you to the first step in the station wizard.

Your station will also appear now in the navigator. You can also access the station wizard at any point in time later by using the right-click context.

The first step of the wizard has the following editor fields.

Field Name Field Description
Name Here you can name your new station. We recommend choosing descriptive names for all your configurations, so you can remember which configuration does what.
Application Instance You can use this option to specify what this station will be used for (Development/Testing/Production). This does not change any behavior, but can be used in the filter.
Station Image
Color You can use different colors to visually group stations.
Description

You now created a station. The main components of a station are the data maps and jobs.

A station determines where the data is exported to.
A data map determines how the data is transformed before the transmission or file creation.
A job determines what Contentserv objects are exported.

The configuration wizard will now lead you step-by-step through the configuration. Every step displays a hint text at the top to provide you the context of your configuration.

Follow the wizard until you reach the finish to build your export. Feel free to use the following tutorials on this page or search for configuration components in the search bar to learn more about each of them.

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents