(Re)start or stop the machine

{{container}}{{container layoutStyle="columns"}}(((

In this microlearning, we will focus on the action to (re)start or stop a machine. In some cases, it can be beneficial to (re)start or stop a machine.

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 (re)starting or stopping a machine

13

With a machine, we mean: This is the component in which the various runtimes are deployed into

14

15

* By restarting the machine, you restart the machine you have just selected

16

** The machine will stay on the same physical hardware.

17

** Flows return in original state

18

* By stopping the machine, you stop the machine (double lane) or you terminate the machine (single lane)

19

** Termination of the machine (single lane)

20

** Runtime states are temporarily stored in EFS (single lane)

21

** Dorment machine (double lane)

22

** In case you stop the core machine on which the JMS is running no data traffic can happen (single and double lane)

23

* By starting the machine, you start the machine (double lane) or you generate a new machine (single lane)

24

** Generation of the machine (single lane)

25

** Runtime states are retrieved from EFS (single lane)

26

** Start the virtual machine, the machine may have moved to different physical hardware (double lane)

27

28

== 3. Restart runtime ==

29

30

In this microlearning, we will focus on the action to (re)start or stop a machine. In some cases, it can be beneficial to (re)start or stop a machine. Before we delve into how to let us first consider the effect and implications of our actions.

31

32

* By restarting the machine, you restart the machine you have just selected

33

** The machine will stay on the same physical hardware.

34

** Flows return in original state

35

* By stopping the machine, you stop the machine (double lane) or you terminate the machine (single lane)

36

** Termination of the machine (single lane)

37

** Runtime states are temporarily stored in EFS (single lane)

38

** Dorment machine (double lane)

39

** In case you stop the core machine on which the JMS is running no data traffic can happen (single and double lane)

40

* By starting the machine, you start the machine (double lane) or you generate a new machine (single lane)

41

** Generation of the machine (single lane)

42

** Runtime states are retrieved from EFS (single lane)

43

** Start the virtual machine, the machine may have moved to different physical hardware (double lane)

44

45

As you can see these actions depending on your architectural setup could alter the physical hardware on which the machine is running. However, it does not alter the state of what is running on each of the runtimes within the machine (as that state is kept in EFS). Do note that when you stop a machine, particularly the one on which the JMS is running your data traffic will be impacted.

46

47

To execute these actions 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 machine (via a right mouse click) and select one of the options (Restart, Start or Stop).

48

49

[[image:Main.Images.Microlearning.WebHome@novice-emagiz-cloud-management-restart-or-stop-machine--context-menu-machine.png]]

50

51

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.

== 4. Assignment ==

There is no assignment for this microlearning.

56

57

== 5. Key takeaways ==

58

59

* By restarting the machine, you restart the machine you have just selected