Skip to Content
Version 1.1 by eMagiz on 2022/05/10 11:24
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = Runtime Dashboard =
10
11 In this microlearning, you will learn the way you can see and validate which flows are active or running on a specific runtime in eMagiz.
12
13 Should you have any questions, please contact academy@emagiz.com.
14
15 * Last update: February 10th, 2021
16 * Required reading time: 3 minutes
17
18 == 1. Prerequisites ==
19
20 * Basic knowledge of the eMagiz platform
21 * Understanding Releases and be able to run a Deployment plan effectively
22
23 == 2. Key concepts ==
24
25 eMagiz uses the concept of flows and runtimes. A flow can run inside a runtime, and that runtime acts as a container to make that flow operate properly. Flows can be stopped inside that container, started, installed, and uninstalled. The runtime dashboard helps to understand the status of the flow inside the runtime, and where needed change the status of that flow.
26
27 eMagiz holds some terminology around these runtimes
28 1 * There is the use of a JMS flow which is run as a single flow inside a runtime. For that specific runtime, there is 1 flow called the JMS and therefore usually referred to as the JMS runtime or just JMS
29 2 * In the Create phase you have seen the onramps and offramps, as well as the routing and error flows. These are running inside the container runtime, often referred to as the container. In the Cloud formation, the JMS and Container are located on a single Cloud machine
30 3 * There are also exit and entry flows that run inside runtimes, and these runtimes are referred to as the connector runtimes or just connectors. These connectors can run on Cloud Connector machines or Local Connector machines.
31
32
33
34 == 3. Exploring the Runtime dashboard ==
35
36 1. Navigation * use the selection on the left-hand panel to select the runtime you wish to inspect
37 2. Options
38 * Start - start the flow selected. The light bulb will turn yellow if the flow is started correctly
39 * Stop - stop the flow selected. The status of the flow will become Resolved.
40 * Refresh - refresh the status of all flows on the selected runtime
41 * Other options are discussed in the next microlearnings
42 3. Versions
43 * Using the dashboard you can see what version of a flow is running in terms of major, minor, or patch. The pattern is <major>.<minor>.<patch>.
44 * The last two digits always denote the build number that is used for that flow.
45 4. Do's and don'ts
46 * Don't stop the container.infra flow. This means that the connectivity to the runtime is gone, and your control over the runtime itself. Especially in Cloud deployments, this is not recommended
47 * Stopping the error.process flow means that error messages are no longer send to the eMagiz platform.
48
49 <p align="center">[[image:crashcourse-platform-deploy-runtime-dashboard-pic1.png||]]</p>
50
51 ===== Practice =====
52
53 == 4. Assignment ==
54
55 Once you have installed the runtimes as described in the previous microlearnings, inspect the runtime dashboard. Stop, start flows.
56
57 == 5. Key takeaways ==
58
59 * The runtime dashboard helps to understand what flows are running and what the associated status is
60 * You need edit rights to perform actions in the Runtime dashboard
61
62
63
64 == 6. Suggested Additional Readings ==
65
66 If you are interested in this topic and want more information on it please read the help text provided by eMagiz when executing these actions.
67
68 == 7. Silent demonstration video ==
69
70 This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
71
72 <iframe width="1280" height="720" src="../../vid/microlearning/crashcourse-platform-deploy-runtime-dashboard.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
73
74 </div>
75
76 </div>
77 </div>
78
79 {{/html}}