Changes for page Cleanup Design Architecture

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Cleanup Design Architecture
	1	+ Cleanup Design Architecture

Content

...	...	@@ -1,6 +1,6 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2	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.
	3	+In this microlearning, we will focus on the verifying the Design Architecture when deleting a specific flow or system.
4	4
5	5	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
...	...	@@ -16,7 +16,7 @@
16	16
17	17	**Removal of a machine**
18	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.
	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	20
21	21	* Go to Design Architecture
22	22	* Find an empty machine in case there is one
...	...	@@ -25,15 +25,15 @@
25	25	[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-design-architecture-1.png]]
26	26
27	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.
	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	29
30		-Steps:
	30	+Steps
31	31
32	32	* Go to Design Architecture
33	33	* Find an runtime in case there is one
34	34	* Using drag & drop you can move the runtime to the new machine as required
35	35
36		-Considerations:
	36	+Considerations
37	37
38	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	39
...	...	@@ -40,7 +40,7 @@
40	40	== 4. Key takeaways ==
41	41
42	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"]].
	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: [[Intermediate Cloud Management>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]].
44	44
45	45	== 5. Suggested Additional Readings ==
46	46