Changes for page eMagiz Architecture

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -17,16 +17,25 @@
17	17	In this fundamental, we will zoom in on what data models are and how they are used within the various integration patterns we support in the platform. Then, we start our journey with a more theoretical look at the concept of data models. Following, we will zoom in on each of the three integration patterns. Finally, per integration pattern, we will explain the role of the data model within each of these three patterns.
18	18
19	19	=== 3.1 Solution Architecture ===
20		-In most phase, there is visualization present in the product that describes the integration landscape. In Capture, Design, Create and Deploy you will have this visual mostly, and each phase does display the integration landscape particular for that specific phase. So that the integration landscape is better understood in the context of the phase. We refer these views as solution views as it tries to describe how the data is flowing from system to system. Or what solution is used for the business process.
	20	+In most phase, there is visualization present in the product that describes the integration landscape. In Capture, Design, Create and Deploy you will have this visual mostly, and each phase does display the integration landscape particular for that specific phase. So that the integration landscape is better understood in the context of the phase. We refer these views as solution views as it tries to describe how the data is flowing from system to system. Or what solution is used for the business process.
	21	+
	22	+Below an example you can recognize as a screenshot of a Design phase. Such views are helpful in discussion with users and architectx involved in the integration work.
21	21
22	22	[[image:Main.Images.Fundamental.WebHome@fundamental_architecture-1.png]]
23	23
24	24	=== 3.2 Cloud Architecture ===
25		-For this we mean the specific way the eMagiz runtimes are distributed on infrastructure components such as the eMagiz Cloud, on-premises servers or other locations where runtime may exist. Please take a moment to check out the Fundamental on Cloud architecture via this [[link>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]]
26		-
27		-
	27	+For this we mean the specific way the eMagiz runtimes are distributed on infrastructure components such as the eMagiz Cloud, on-premises servers or other locations where runtime may exist. Please take a moment to check out the Fundamental on Cloud architecture via this [[link>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]].
	28	+The Cloud architecture can be design in the Design - Architecture section, and effectuated via the Deply - Architecture section. Please check out
28	28
29	29
	31	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
	32	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]]
	33	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
	34	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]]
	35	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
	36	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Advanced Level.eMagiz Cloud Management.WebHome||target="blank"]]
	37	+[[SPEL Expressions>>Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
	38	+
30	30	== 4. Key takeaways ==
31	31
32	32	* Data models define the structure of data related to a system or related to eMagiz itself