You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Open Integration Hub enables data synchronization across a variety of applications. To create a connection and enable interaction a link is needed between the software application and the Open Integration Hub - namely an Open Integration Hub connector.
@@ -25,33 +22,43 @@ The Open Integration Hub enables data synchronization across a variety of applic
25
22
- [Folders](#folders)
26
23
- [Documents](#documents)
27
24
-[Workgroup](#workgroup)
28
-
- [Information](#information)
29
25
- [Member](#member)
30
26
-[Wording](#wording)
31
27
32
28
<!-- /TOC -->
33
29
30
+
The Open Integration Hub enables data synchronization across a variety of applications. To enable interaction with any software an technical component is needed to the Open Integration Hub - the connector. It consists of two distinct parts: the adapter and the transformer.
31
+
32
+
An **adapter** is a module for the syntactic connection of an external application and its data to the Open Integration Hub. This includes protocol translation, data format transformation, etc.
33
+
Furthermore it provides functionalities to perform e.g. CRUD operations within the source system.
34
34
35
-
A connector connects a software solution to the Open Integration Hub. It consists of two distinct parts, namely adapter and transformer. It contains different functionalities e.g. to fetch and transform data. These functionalities are further explained in the sections [adapter](#adapter) and [transformer](#transformer). In order to achieve our goal to establish a successful open source community we need to steadily increase the number of connectors. So join us and help us grow as an open source community!
35
+
For further information please read through the information within the [adapter folder](/Adapters).
36
36
37
+
A **transformer** is responsible to semantically transform an incoming JSON object into another JSON object. Thus the mapping between two data models is done within the transformer.
38
+
39
+
For further information please read through the information within the [transformer folder](/Transformer).
37
40
38
41
The following illustration provides a holistic overview of a connector:
39
42

40
43
41
-
### Adapter
42
44
43
-
An adapter is a module for the syntactic connection of an external application and its data to the Open Integration Hub. This includes protocol translation, data format transformation, etc.
44
-
Furthermore it provides functionalities to perform e.g. CRUD operations within the source system.
45
+
## Open Source Connectors
45
46
46
-
For further information please read through the information within the [adapter folder](/Adapters).
47
+
Like the Open Integration Hub services, connectors are also standardized components that can be reused in any implementation of the framework. There are several contributors that provide a wide range of open source connectors already. So before you start your own, check out what's already there:
If you want to build your own connector, we suggest you start with a our node.js example, to understand the structure and what you need to get going. Most components are build in node.js, although you can choose any language you want.
50
54
51
-
A transformer is responsible to semantically transform an incoming JSON object into another JSON object. Thus the mapping between two data models is done within the transformer.
@@ -68,25 +75,14 @@ When looking for further information or support, please contact: philipp.hoegner
68
75
### Folders
69
76
70
77
-[Adapters](Adapters): Describes the adapters, their goals, standardized behavior and checklists for building an adapter
71
-
-[Protocols](Protocols): Collection of all taken protocols by the workgroup
78
+
-[Protocols](Protocols): Archive for all protocols by the workgroup
72
79
-[Transformer](Transformer): Includes the transformer concept, a basic introduction into the JSONata transformation language, transformer evolution and suggestions for possible implementations
73
80
74
81
### Documents
75
82
-[CONTRIBUTING](CONTRIBUTING.md): Contains the contribution guideline for the Open Integration Hub project
76
83
-[CODE_OF_CONDUCT](CODE_OF_CONDUCT.md): Contains an explanation of the expected behavior of the community members, following the code of conduct defined by the Contributor Covenant
77
84
78
85
## Workgroup
79
-
### Information
80
-
You have the opportunity to get your questions answered in a `weekly Q&A session`.
81
-
Feel free to attend and invite other people to this session.
82
-
83
-
If possible please send your question in advance to **philipp.hoegner@cloudecosystem.org**.
84
-
85
-
The session will take place every `Monday from 11:00 - 12:00`. The first session will be next monday.
@@ -99,4 +95,4 @@ The session will take place every `Monday from 11:00 - 12:00`. The first sessio
99
95
| Philipp Hoegner|[philecs](https://github.com/philecs)|[Cloud Ecosystem](http://www.cloudecosystem.org/)| Committer |
100
96
101
97
## Wording
102
-
Within the project different terms and abbreviations are frequently used. All terms and abbrevations are explained within the [glossary](https://github.com/openintegrationhub/Connectors/wiki/Glossary) and our [list of abbrevations](https://github.com/openintegrationhub/Connectors/wiki/Abbreviations).
98
+
Within the project different terms and abbreviations are frequently used. All terms and abbreviations are explained within the [glossary](https://github.com/openintegrationhub/Connectors/wiki/Glossary) and our [list of abbrevations](https://github.com/openintegrationhub/Connectors/wiki/Abbreviations).
0 commit comments