Reset runtime - eMagiz

(((

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.

6

7

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.

8

9

Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].

10

11

== 1. Prerequisites ==

12

13

* Basic knowledge of the eMagiz platform

14

* Basic knowledge of cloud management

15

16

== 2. Key concepts ==

17

18

This microlearning centers around resetting a runtime

19

With resetting, we mean: Ensure that we begin with a clean slate and forget about what happened before

20

21

* A reset is the more aggressive approach compared to a restart.

22

* The reset does the following on cloud level:

23

** Stops the runtime service (if running)

24

** Removes data (except Artemis folder + revision info)

25

** Removes local repository folder

26

** Starts the runtime service (if stopped at step 1)

27

* With a reset, you start with a clean slate

28

** Flow version could be different based on changes in the release

29

** Custom H2 database is emptied

30

31

== 3. Reset runtime ==

32

33

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.

34

35

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.

36

37

In short, the reset action can be described by the following:

38

39

* A reset is the more aggressive approach compared to a restart.

40

* The reset does the following on cloud level:

41

** Stops the runtime service (if running)

42

** Removes data (except Artemis folder + revision info)

43

** Removes local repository folder

44

** Starts the runtime service (if stopped at step 1)

45

* With a reset, you start with a clean slate

46

** Flow version could be different based on changes in the release

47

** Custom H2 database is emptied

48

49

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 reset runtime.

50

51

[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--context-menu-runtime.png]]

52

53

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.

54

55

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 execute the Reset action. 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.

56

57

[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--help-text-h2-efs.png]]

58

59

== 4. Key takeaways ==

60

61

* A reset is the more aggressive approach compared to a restart.

62

* The reset does the following on cloud level:

63

** Stops the runtime service (if running)

64

** Removes data (except Artemis folder + revision info)

65

** Removes local repository folder

66

** Starts the runtime service (if stopped at step 1)

67

* With a reset, you start with a clean slate

68

** Flow version could be different based on changes in the release

69

** Custom H2 database is emptied

70

71

== 5. Suggested Additional Readings ==

72

73

There are no suggested additional readings on this topic)))

74

75

((({{toc/}}))){{/container}}

76

Wiki source code of Reset runtime

Navigation

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}
		3	(((
		4
		5	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.
		6
		7	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.
		8
		9	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
		10
		11	== 1. Prerequisites ==
		12
		13	* Basic knowledge of the eMagiz platform
		14	* Basic knowledge of cloud management
		15
		16	== 2. Key concepts ==
		17
		18	This microlearning centers around resetting a runtime
		19	With resetting, we mean: Ensure that we begin with a clean slate and forget about what happened before
		20
		21	* A reset is the more aggressive approach compared to a restart.
		22	* The reset does the following on cloud level:
		23	** Stops the runtime service (if running)
		24	** Removes data (except Artemis folder + revision info)
		25	** Removes local repository folder
		26	** Starts the runtime service (if stopped at step 1)
		27	* With a reset, you start with a clean slate
		28	** Flow version could be different based on changes in the release
		29	** Custom H2 database is emptied
		30
		31	== 3. Reset runtime ==
		32
		33	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.
		34
		35	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.
		36
		37	In short, the reset action can be described by the following:
		38
		39	* A reset is the more aggressive approach compared to a restart.
		40	* The reset does the following on cloud level:
		41	** Stops the runtime service (if running)
		42	** Removes data (except Artemis folder + revision info)
		43	** Removes local repository folder
		44	** Starts the runtime service (if stopped at step 1)
		45	* With a reset, you start with a clean slate
		46	** Flow version could be different based on changes in the release
		47	** Custom H2 database is emptied
		48
		49	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 reset runtime.
		50
		51	[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--context-menu-runtime.png]]
		52
		53	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.
		54
		55	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 execute the Reset action. 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.
		56
		57	[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-cloud-management-reset-runtime--help-text-h2-efs.png]]
		58
		59	== 4. Key takeaways ==
		60
		61	* A reset is the more aggressive approach compared to a restart.
		62	* The reset does the following on cloud level:
		63	** Stops the runtime service (if running)
		64	** Removes data (except Artemis folder + revision info)
		65	** Removes local repository folder
		66	** Starts the runtime service (if stopped at step 1)
		67	* With a reset, you start with a clean slate
		68	** Flow version could be different based on changes in the release
		69	** Custom H2 database is emptied
		70
		71	== 5. Suggested Additional Readings ==
		72
		73	There are no suggested additional readings on this topic)))
		74
		75	((({{toc/}}))){{/container}}
		76	{{/container}}