Skip to Content

Wiki source code of Reset Runtime

Last modified by Martijn Woudstra on 2022/10/28 14:06
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 In a previous microlearning, we learned about restarting runtimes. In that microlearning, we learned that restarting the runtime does not affect flows, data, psychical hardware, or otherwise. It is simply jump-starting the runtime or machine once more. In this microlearning, however, we will focus on the action to reset a runtime. A reset on the other hand is the more aggressive approach and does have a significant effect. In other words, the main difference is that with a reset you begin with a clean slate compared to the simple restart.
5
6 Having said that there are some cases where it can become beneficial to reset a runtime. For instance when running into memory issues or when doing large bulk build number upgrades.
7
8 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
9
10 == 1. Prerequisites ==
11
12 * Basic knowledge of the eMagiz platform
13 * Basic knowledge of cloud management
14
15 == 2. Key concepts ==
16
17 This microlearning centers around resetting a runtime
18 With resetting, we mean: Ensure that we begin with a clean slate and forget about what happened before
19
20 * A reset is the more aggressive approach compared to a restart.
21 * The reset does the following on cloud level:
22 ** Stops the runtime service (if running)
23 ** Removes data (except Artemis folder + revision info)
24 ** Removes local repository folder
25 ** Starts the runtime service (if stopped at step 1)
26 * With a reset, you start with a clean slate
27 ** Flow version could be different based on changes in the release
28 ** Custom H2 database is emptied
29
30 == 3. Reset runtime ==
31
32 In a previous microlearning, we learned about restarting runtimes. In that microlearning, we learned that restarting the runtime does not affect flows, data, psychical hardware, or otherwise. It is simply jump-starting the runtime or machine once more. In this microlearning, however, we will focus on the action to reset a runtime. A reset on the other hand is the more aggressive approach and does have a significant effect. In other words, the main difference is that with a reset you begin with a clean slate compared to the simple restart.
33
34 Having said that there are some cases where it can become beneficial to reset a runtime. For instance when running into memory issues or when doing large bulk build number upgrades.
35
36 In short, the reset action can be described by the following:
37
38 * A reset is the more aggressive approach compared to a restart.
39 * The reset does the following on runtime level:
40 ** Stops the runtime service (if running)
41 ** Removes data (except Artemis folder + revision info)
42 ** Removes local repository folder
43 ** Starts the runtime service (if stopped at step 1)
44 * With a reset, you start with a clean slate
45 ** Flow version could be different based on changes in the release
46 ** Custom H2 database is emptied
47
48 To execute this action please navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called Details.
49
50 [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--context-menu-runtime-gen3.png]]
51
52 In the pop-up that you will see you can navigate to the "Status" tab. This tab shows the details of the runtime such as the release version, the uptime and the current status.
53
54 [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--details-menu-runtime-gen3.png]]
55
56 On this pop-up you also have several options available that can "Reset" your runtime. Differently from how it used to work you now need to execute various steps in order to achieve the same effect. The first step of the process is to press the "Stop" button. This way the runtime is stopped. Subsequently you need to press the "Remove" button. Once this is done you can close the pop-up for now and deploy your currently active release. As a result the runtime will be deployed again with a clean slate.
57
58 To verify that everything went correctly and your runtime is running correctly you can once again view the details pop-up on Architecture level. Subsequently you can double check this by looking at the logs under Manage -> Log Entries.
59
60 {{warning}}Note that when you have a custom H2 database on runtime level (i.e. for storing metadata) the H2 database will be deleted as well when you remove the runtime. To safeguard against this you could store your H2 database on EFS. Please take a look at the help text for the URL field on the JDBC H2 connection pool component for more information.
61
62 [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--help-text-h2-efs.png]]{{/warning}}
63
64 == 4. Assignment ==
65
66 There is no assignment for this microlearning.
67
68 == 5. Key takeaways ==
69
70 * A reset is the more aggressive approach compared to a restart.
71 * The reset does the following on cloud level:
72 ** Stops the runtime service (if running)
73 ** Removes data (except Artemis folder + revision info)
74 ** Removes local repository folder
75 ** Starts the runtime service (if stopped at step 1)
76 * With a reset, you start with a clean slate
77 ** Flow version could be different based on changes in the release
78 ** Custom H2 database is emptied
79
80 == 6. Suggested Additional Readings ==
81
82 There are no suggested additional readings on this topic
83
84 == 7. Silent demonstration video ==
85
86 There is no demonstration video of this functionality.)))
87
88 ((({{toc/}}))){{/container}}
89 {{/container}}