Connectivity Studio

This chapter explains the basic concept behind Connectivity Studio.

Note: To-Increase is in the process of redesigning the Connectivity studio documentation. For the redesigned parts of the Connectivity studio documentation, refer to Connectivity studioYou can find the not-yet-redesigned parts of the documentation here.

Concept

The required components to make an integration with Connectivity Studio are: two connectors, two documents, and one message. The message is the vehicle transporting data from source to target and takes care of the field mapping. Both the source and the target are composed of a connector and a document. The connector defines how to connect to a data source where the document describes how the data looks like.

Let's explain this with an example. Imagine that you want to import customers from a webshop to Microsoft Dynamics AX. How does this looks like in Connectivity Studio? In this case, the Webshop is the source and Microsoft Dynamics AX is the target.


The source and the target are composed out of a connector and a document. The following image shows all the required components for this integration.


The main advantages of this concept is that all the integrations are defined in the same (structured) way and you can also re-use components. For example: If you want to export the customers to the webshop you can re-use the connectors and documents. You only need to create a new message.