Skip to Content
Version 1.1 by eMagiz on 2022/05/22 21:16
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = Explaining Platform components =
10
11 In this microlearning, we will focus on the eMagiz platform and the various components that are part of the eMagiz platform. Knowing which components make up the eMagiz solution will help you better understand the product and in turn, will also make it easier to manage your eMagiz solution. Per component, we will introduce what it is and what it is good for.
12
13 Should you have any questions, please contact academy@emagiz.com.
14
15 * Last update: April 22th, 2021
16 * Required reading time: 9 minutes
17
18 == 1. Prerequisites ==
19
20 * Basic knowledge of the eMagiz platform
21
22 == 2. Key concepts ==
23
24 This microlearning centers around explaining the components that make up the platform.
25
26 By components we mean: A part that is needed to successfully run the eMagiz solution. Some of these parts are generic. Others are only relevant for specific cases
27
28 There are six key components within the eMagiz platform:
29
30 * eMagiz iPaaS Portal
31 * Runtime
32 * Cloud Templates
33 * Build numbers
34 * eMagiz Connector for Mendix (Messaging)
35 * eMagiz Connector for Mendix (Event Streaming)
36
37
38
39 == 3. Explaining Platform components ==
40
41 In this microlearning, we will focus on the eMagiz platform and the various components that are part of the eMagiz platform. Knowing which components make up the eMagiz solution will help you better understand the product and in turn, will also make it easier to manage your eMagiz solution. Per component, we will introduce what it is and what it is good for.
42
43 There are six key components within the eMagiz platform:
44
45 * eMagiz iPaaS Portal
46 * Runtime
47 * Cloud Templates
48 * Buildnumbers
49 * eMagiz Connector for Mendix (Messaging)
50 * eMagiz Connector for Mendix (Event Streaming)
51
52 === 3.1 eMagiz iPaaS Portal ===
53
54 The eMagiz iPaaS Portal provides web-based access to the eMagiz project where users can create, update and delete integrations across the Test, Acceptance, and Productions environments. Holds access to all configuration options of the eMagiz platform instance required to run these integrations optimally. The portal is divided into five phases (Capture, Design, Create, Deploy and Manage). Each of these phases has a unique purpose.
55
56 Note that the eMagiz iPaaS Portal (https://my.emagiz.com) is updated every 2 weeks to allow for user interface improvements and improvements to the integration model. According to the EULA, clients can expect a downtime of max. 2 hours of the eMagiz Portal. All other services inside the client platform such as messaging and monitoring services, are not affected and will continue to run as normal.
57
58 === 3.2 Runtime ===
59
60 The runtime is the component into which the individual integration flows are deployed into. It's a Java-based application container that can run in the Cloud or Local. A runtime is visually displayed and described in the eMagiz iPaaS Portal as a container (holding the onramps, offramps, routing, error) or a connector (holding the exits and entries).
61
62 Note that eMagiz plans a major release once per year that involves migration activities of the current client installation. A separate eMagiz Release should be created and tested to isolate a potential impact on the current configuration. eMagiz makes the best efforts to make these migrations as smooth as possible with as little effort as possible for client installations.
63
64 ==== 3.2.1 Supported Version(s) ====
65
66 * Version 5.0.2 - released October 19th, 2018
67 * Version 5.0.3 - released May 17th, 2019
68
69 See also release notes under the Community section of the eMagiz iPaaS Portal or this link: https://emagiz.github.io/docs/release-notes/index_runtime.html
70
71 === 3.3 Cloud Templates ===
72
73 Cloud templates are the blueprints for the cloud slot. They translate your architectural design to virtual or physical resources in the cloud. In other words, the cloud template is responsible to provides the components such as OS, Java versions, etc. in which the runtime components can operate in. On top of that these templates also provide various auto-healing and managing tools to enhance the performance and stability of the platform instance. These are Cloud platform-specific.
74
75 Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you. This functionally is currently supported for Test and Acceptance. We are working on making it supported for Production.
76
77 These Cloud templates are released per Cloud environment such as AWS and are updated on average 4-6 times a year. Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you. This functionally is currently supported for Test and Acceptance. We are working on supporting it for Production. Messaging traffic is only impacted with a delay * no messages are lost.
78
79 ==== 3.3.1 Supported Versions ====
80
81 * R17 Single Lane
82 * R16 Single Lane
83 * R10 Double lane
84 * R11 Double lane
85
86 See also release notes under the Community section of the eMagiz iPaaS Portal or this link: https://emagiz.github.io/docs/release-notes/index_cloud.html
87
88 === 3.4 Build numbers ===
89
90 Every deployment package of a flow has a specific build number. This deployment package (build) contains the (eMagiz) software components that work in conjunction with the functional components as configured in the Create phase of the eMagiz Portal.
91
92 As eMagiz makes use of various open source technologies such as Spring, Apache, ActiveMQ Artemis, Saxon, Netty, and others we need to ensure that we keep our dependency on those pieces of software up to date. Apart from that we also make updates to various functional components that are available to you in the Create phase. Those updates (adding a new component, removing a component, changing a component) result in different code that needs to be stored in the deployment package. So every time we change something in that area (repository or runtime level) a new build number is released.
93
94 We strive to ensure that all build numbers that are released are backward compatible with previous build numbers. We are dedicated to ensuring client platforms are unaffected by these build numbers improvements.
95
96 Note that you can find all open source technology (including versions) that eMagiz uses under Administration -> About eMagiz -> Credits
97
98 <p align="center">[[image:intermediate-solution-architecture-explaining-platform-components--open-source-credits-emagiz.png||]]</p>
99
100 ==== 3.4.1 Supported Versions ====
101
102 * All build numbers higher than or equal to build 46
103
104 See also release notes under the Community section of the eMagiz iPaaS Portal or this link: https://emagiz.github.io/docs/release-notes/index_build.html
105
106 === 3.5 eMagiz Connector for Mendix (Messaging) ===
107
108 Contains the Mendix module that allows the Mendix project to interact with the eMagiz iPaaS instance through the Messaging pattern. Holds the configuration details to connect to the eMagiz instance as well as the Java actions that can be referred to inside Mendix Microflows. With the help of this module, you can considerably speed up the development of messaging integrations between Mendix and eMagiz
109
110 Note that you can download the available version under Deploy -> On-premises -> Runtime Downloads
111
112 <p align="center">[[image:intermediate-solution-architecture-explaining-platform-components--runtime-downloads-emc.png||]]</p>
113
114 ==== 3.5.1 Supported Versions ====
115
116 * All EMC versions higher or equal than version 3.0.2
117
118 See also release notes under the Community section of the eMagiz iPaaS Portal or this link: https://emagiz.github.io/docs/release-notes/index_runtime.html
119
120 === 3.6 eMagiz Connector for Mendix (Event Streaming) ===
121
122 Contains the Mendix module that allows the Mendix project to interact with the eMagiz Cluster through the Event Streaming pattern. Holds the configuration details to connect to the eMagiz instance as well as example microflows on how to produce and consume on the topics within the eMagiz Cluster. With the help of this module, you can considerably speed up the development of event streaming integrations between Mendix and eMagiz
123
124 Note that you can download the available version under Deploy -> On-premises -> Runtime Downloads
125
126 <p align="center">[[image:intermediate-solution-architecture-explaining-platform-components--runtime-downloads-emk.png||]]</p>
127
128 ==== 3.6.1 Supported Versions ====
129
130 * All versions higher or equal than version 1.0.0
131
132 See also release notes under the Community section of the eMagiz iPaaS Portal or this link: https://emagiz.github.io/docs/release-notes/index_runtime.html
133
134 ===== Practice =====
135
136 == 4. Assignment ==
137
138 Read up on the release notes of the various platform components and determine for the projects in which you operate what the status is of your eMagiz solution on the eMagiz platform.
139
140 == 5. Key takeaways ==
141
142 * The eMagiz platform consists of a lot of components.
143 * The following six components are most relevant for our user community:
144 * eMagiz iPaaS Portal
145 * Runtime
146 * Cloud Templates
147 * Buildnumbers
148 * eMagiz Connector for Mendix (Messaging)
149 * eMagiz Connector for Mendix (Event Streaming)
150
151
152
153 == 6. Suggested Additional Readings ==
154
155 If you are interested in this topic and want more information on it please read the release notes provided by eMagiz
156
157 == 7. Silent demonstration video ==
158
159 As this is a more theoretical microlearning we have no video for this
160
161 </div>
162
163 </div>
164 </div>
165
166 {{/html}}