Wiki source code of Cleanup Design Architecture

Last modified by Danniar Firdausy on 2024/09/18 13:54

Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2
3 This microlearning focuses on verifying and cleaning up your Design Architecture when deleting specific flows or systems. We will guide you through the steps to ensure that your system remains optimized and well-organized after cleaning up your integration model.
4
5 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6
7 == 1. Prerequisites ==
8
9 * Basic knowledge of the eMagiz platform
10
11 == 2. Key concepts ==
12
13 This microlearning centers around cleaning up Design Architecture. The Design Architecture as you have seen in previous microlearnings is the place to place the designed system at the right connector machine (Cloud or on-premises). When cleaning your model it can happen that a specific system needs to be removed or relocated. The cleaned flow might be the last in the system, and therefore the system needs to be removed. Next to that, the removed flow may cause a different design decision towards the location of the system.
14
15 == 3. Cleanup Design Architecture ==
16
17 **Removal of a machine**
18
19 We are assuming that the flow in question is already removed untill the Capture phase. The system would already be removed in case it was the last flow of the system.
20
21 * Go to Design Architecture
22 * Find an empty machine in case there is one
23 * Remove the machine using the menu under right click
24
25 [[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-design-architecture-1.png]]
26
27 **Relocate system**
28 We are assuming that the flow in question is already removed untill the Capture phase. The system would still be present as more flows exist.
29
30 Steps:
31
32 * Go to Design Architecture
33 * Find an runtime in case there is one
34 * Using drag & drop you can move the runtime to the new machine as required
35
36 Considerations:
37
38 * Move the runtime to a new machine in case an existing machine has sufficient memory for the updated runtime (which has a new memory advice). See the microlearning [[Understanding Design Architecture - Basic>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]] section 3.3 for more information on checking the size of a machine.
39
40 == 4. Key takeaways ==
41
42 * Review of the Design Architecture is very important to do at a regular basis. Cleaning a flow should be always be followed by the review if the Design Architecture needs a cleanup
43 * Cleaning up the Design phase may also result in an update of the memory settings of the connector runtime. Please take a moment to review the appropriate microlearning for this: [[Understanding Design Architecture - Basic>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]].
44
45 == 5. Suggested Additional Readings ==
46
47 If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
48
49 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
50 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
51 *** [[Understanding Design Architecture - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]]
52 * [[Lifecycle Management (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22lifecycle+management%22||target="blank"]]
53
54 )))((({{toc/}}))){{/container}}{{/container}}