Changes for page Cleanup Design Architecture

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

Content

...	...	@@ -4,9 +4,6 @@
4	4
5	5	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
7		-* Last update: August 26st, 2021
8		-* Required reading time: 5 minutes
9		-
10	10	== 1. Prerequisites ==
11	11
12	12	* Basic knowledge of the eMagiz platform
...	...	@@ -15,11 +15,9 @@
15	15
16	16	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.
17	17
18		-
19		-
20	20	== 3. Cleanup Design Architecture ==
21	21
22		-**1. Removal of a machine**
	17	+**Removal of a machine**
23	23
24	24	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
25	25
...	...	@@ -29,7 +29,7 @@
29	29
30	30	[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-design-architecture-1.png]]
31	31
32		-**2. Relocate system**
	27	+**Relocate system**
33	33	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
34	34
35	35	Steps
...	...	@@ -40,10 +40,8 @@
40	40
41	41	Considerations
42	42
43		-* 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.WebHome||target="blank"]] section 3.3 for more information on checking the size of a machine.
44	44
45		-
46		-
47	47	== 4. Assignment ==
48	48
49	49	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,10 +51,8 @@
51	51	== 5. Key takeaways ==
52	52
53	53	* 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
54		-* 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)).
	47	+* 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>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]].
55	55
56		-
57		-
58	58	== 6. Suggested Additional Readings ==
59	59
60	60	If you are interested in this topic and want more information on it please read the release notes provided by eMagiz