Version 18.1 by Erik Bakker on 2022/06/10 08:37

Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 = Cleanup Design Architecture =
3
4 In this microlearning, we will focus on the verifying the Design Architecture when deleting a specific flow or system.
5
6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 * Last update: August 26st, 2021
9 * Required reading time: 5 minutes
10
11 == 1. Prerequisites ==
12
13 * Basic knowledge of the eMagiz platform
14
15 == 2. Key concepts ==
16
17 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.
18
19
20
21 == 3. Cleanup Design Architecture ==
22
23 **1. Removal of a machine**
24
25 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
26
27 * Go to Design Architecture
28 * Find an empty machine in case there is one
29 * Remove the machine using the menu under right click
30
31 [[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-design-architecture-1.png]]
32
33 **2. Relocate system**
34 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
35
36 Steps
37
38 * Go to Design Architecture
39 * Find an runtime in case there is one
40 * Using drag & drop you can move the runtime to the new machine as required
41
42 Considerations
43
44 * 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](crashcourse-platform-design-understanding-design-architecture-basic.md)) section 3.3 for more information on checking the size of a machine.
45
46
47
48 == 4. Assignment ==
49
50 Determine whether whether your Design Architecture requires cleaning. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
51
52 == 5. Key takeaways ==
53
54 * 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
55 * 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: ([Intermediate Cloud Management](intermediate-emagiz-cloud-management-index.md)).
56
57
58
59 == 6. Suggested Additional Readings ==
60
61 If you are interested in this topic and want more information on it please read the release notes provided by eMagiz
62
63 == 7. Silent demonstration video ==
64
65 As this is a more theoretical microlearning we have no video for this
66
67 )))((({{toc/}}))){{/container}}{{/container}}