Changes for page eMagiz Architecture
Last modified by Carlijn Kokkeler on 2024/08/08 15:21
From version 17.1
edited by Erik Bakker
on 2022/07/07 09:54
on 2022/07/07 09:54
Change comment:
There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2022/07/07 09:56
on 2022/07/07 09:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -13,7 +13,7 @@ 13 13 14 14 == 3. Architecture in eMagiz == 15 15 16 -In this fundamental, we will zoom in on whatdatamodels are andhowtheyareusedwithinthevariousintegrationpatternswe supportThen,westartour journeywith a more theoretical look at theconcept of data models. Following, we will zoom inon eachofthehreeintegrationpatterns.Finally,per integrationpattern, we willexplain the roleofthe datamodel withineachofthesethree patterns.16 +In this fundamental, we will zoom in on explaining the concepts and terms related to Architecture incorporated within the eMagiz platform. At first, we will look at the "Solution Architecture" within the platform, and subsequently, we will look at the "Cloud Architecture." 17 17 18 18 === 3.1 Solution Architecture === 19 19 In most phases, there is visualization present in the product that describes the integration landscape. In Capture, Design, Create and Deploy, you will have this primarily visual, and each phase displays the integration landscape for that specific phase. So that the integration landscape is better understood in the context of the phase. We refer to these views as solution views as it tries to describe how the data is flowing from system to system. In other words, what solution is used for the business process.