Last modified by Erik Bakker on 2024/08/26 12:11

From version 11.1
edited by Erik Bakker
on 2022/08/22 11:46
Change comment: There is no comment for this version
To version 14.1
edited by Eva Torken
on 2023/06/16 11:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -52,17 +52,12 @@
52 52  
53 53  Once again, you will receive a confirmation pop-up. Confirming, in this case, means deleting all captured information on the system level and removing all designed information on the system level.
54 54  
55 -One last consideration to consider when removing the system is to determine whether your captured system was already part of the Create and Deploy phase of eMagiz. If that was the case, additional measures are needed to properly clean up the system and all related information in the Deploy phase of eMagiz. In that case, you need to Delete your runtime in Deploy on all three environments. More on how to do so can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.advanced-lifecycle-management-cleanup-a-deployed-runtime.WebHome||target="blank"]]. Make note that is an advanced action that only a bus owner can perform within your project. If you did not yet transfer the integration and the system to the Create phase, this action is unnecessary as the runtime does not exist in the Deploy phase.
55 +One last consideration to consider when removing the system is to determine whether your captured system was already part of the Create and Deploy phase of eMagiz. If that was the case, additional measures are needed to properly clean up the system and all related information in the Deploy phase of eMagiz. In that case, you need to Delete your runtime in Deploy on all three environments. More on how to do so can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.advanced-lifecycle-management-cleanup-a-deployed-runtime||target="blank"]]. Make note that is an advanced action that only a model owner can perform within your project. If you did not yet transfer the integration and the system to the Create phase, this action is unnecessary as the runtime does not exist in the Deploy phase.
56 56  
57 57  Armed with this knowledge, you can make the correct decision in cases where you consider cleaning up the captured integration.
58 58  
59 -== 4. Assignment ==
59 +== 4. Key takeaways ==
60 60  
61 -Determine whether you can clean up a captured integration within your project. If so, execute the cleanup.
62 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
63 -
64 -== 5. Key takeaways ==
65 -
66 66  * There are four essential considerations before cleaning up a captured integration:
67 67   * Is the integration/flow not mentioned anymore in any alerting in Manage?
68 68   * Is the integration removed from all releases?
... ... @@ -71,15 +71,9 @@
71 71  * Before deletion, eMagiz will ask for confirmation
72 72  * Deletion means that you cannot get it back anymore
73 73  
74 -== 6. Suggested Additional Readings ==
69 +== 5. Suggested Additional Readings ==
75 75  
76 76  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
77 77  
78 -== 7. Silent demonstration video ==
79 -
80 -This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned
81 -
82 -{{video attachment="novice-lifecycle-management-cleanup-a-captured-integration.mp4" reference="Main.Videos.Microlearning.WebHome"/}})))
83 -
84 84  ((({{toc/}}))){{/container}}
85 85  {{/container}}