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

From version 17.1
edited by eMagiz
on 2022/05/17 09:29
Change comment: There is no comment for this version
To version 26.1
edited by Danniar Firdausy
on 2024/09/18 13:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Cleanup Design Architecture
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.dfirdausy
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,20 +1,9 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
1 +{{container}}{{container layoutStyle="columns"}}(((
4 4  
5 -<div class="doc">
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.
6 6  
5 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 -
9 -= Cleanup Design Architecture =
10 -
11 -In this microlearning, we will focus on the verifying the Design Architecture when deleting a specific flow or system.
12 -
13 -Should you have any questions, please contact academy@emagiz.com.
14 -
15 -* Last update: August 26st, 2021
16 -* Required reading time: 5 minutes
17 -
18 18  == 1. Prerequisites ==
19 19  
20 20  * Basic knowledge of the eMagiz platform
... ... @@ -23,57 +23,43 @@
23 23  
24 24  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.
25 25  
26 -
27 -
28 28  == 3. Cleanup Design Architecture ==
29 29  
30 -**1. Removal of a machine**
17 +**Removal of a machine**
31 31  
32 -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
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.
33 33  
34 34  * Go to Design Architecture
35 35  * Find an empty machine in case there is one
36 36  * Remove the machine using the menu under right click
37 37  
38 -<p align="center">[[image:intermediate-lifecycle-management-cleanup-design-architecture-1.png||]]</p>
25 +[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-design-architecture-1.png]]
39 39  
40 -**2. Relocate system**
41 -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
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.
42 42  
43 -Steps
30 +Steps:
44 44  
45 45  * Go to Design Architecture
46 46  * Find an runtime in case there is one
47 47  * Using drag & drop you can move the runtime to the new machine as required
48 48  
49 -Considerations
36 +Considerations:
50 50  
51 -* 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.
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.
52 52  
53 -===== Practice =====
40 +== 4. Key takeaways ==
54 54  
55 -== 4. Assignment ==
56 -
57 -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.
58 -
59 -== 5. Key takeaways ==
60 -
61 61  * 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
62 -* 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)).
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"]].
63 63  
45 +== 5. Suggested Additional Readings ==
64 64  
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:
65 65  
66 -== 6. Suggested Additional Readings ==
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"]]
67 67  
68 -If you are interested in this topic and want more information on it please read the release notes provided by eMagiz
69 -
70 -== 7. Silent demonstration video ==
71 -
72 -As this is a more theoretical microlearning we have no video for this
73 -
74 -</div>
75 -
76 -</div>
77 -</div>
78 -
79 -{{/html}}
54 +)))((({{toc/}}))){{/container}}{{/container}}