Wiki source code of Restart Runtime
Last modified by Danniar Firdausy on 2024/09/19 09:56
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{container}}{{container layoutStyle="columns"}}((( | ||
2 | In this microlearning, we will explore the reasons for restarting a runtime, the process involved, and the effects on your integration flows. Restarting a runtime can be a useful action in various situations, and understanding when and how to do it effectively is crucial. Let's get started! | ||
3 | |||
4 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
5 | |||
6 | == 1. Prerequisites == | ||
7 | |||
8 | * Basic knowledge of the eMagiz platform | ||
9 | |||
10 | == 2. Key concepts == | ||
11 | |||
12 | This microlearning centers around restarting a runtime. | ||
13 | * With runtime, we mean: This is the component in which the individual integration flows are deployed into. | ||
14 | |||
15 | == 3. Restart runtime == | ||
16 | |||
17 | In this microlearning, we will focus on the action to restart a runtime. In some cases, it can be beneficial to restart a runtime. Before we delve into how to let us first consider the effect and implications of our actions. | ||
18 | |||
19 | * By restarting the runtime, you restart all flows (including infra) of the runtime you have selected | ||
20 | ** Flows return in original state | ||
21 | |||
22 | As you can see this action does not alter the state of your runtime by being executed. 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 restart runtime. | ||
23 | |||
24 | [[image:Main.Images.Microlearning.WebHome@novice-emagiz-cloud-management-restart-runtime--context-menu-runtime.png]] | ||
25 | |||
26 | After a grace period please execute the standard checks, i.e checking the logs under Manage -> Log Entries and verify if you can access the runtimes via runtime dashboard. | ||
27 | |||
28 | == 4. Key takeaways == | ||
29 | |||
30 | * Restarting a runtime reboots all flows and infrastructure within that runtime, returning them to their original state. | ||
31 | * This action does not alter the overall state of your runtime. | ||
32 | * Ensure to perform standard checks, such as reviewing logs and verifying runtime accessibility, after a restart to confirm everything is functioning as expected. | ||
33 | |||
34 | == 5. Suggested Additional Readings == | ||
35 | |||
36 | If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: | ||
37 | |||
38 | * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] | ||
39 | ** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] | ||
40 | *** [[Reset Runtime (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-reset-runtime.WebHome||target="blank"]] | ||
41 | * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] | ||
42 | ** [[Recovery Guide (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.WebHome||target="blank"]] | ||
43 | *** [[Signal received - Recovery Needed (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.expert-recovery-guide-signals-reproducable-steps||target="blank"]] | ||
44 | * [[Restart Runtime (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22restart+runtime%22||target="blank"]] | ||
45 | |||
46 | )))((({{toc/}}))){{/container}}{{/container}} |