Wiki source code of Storing Metadata - Design Architecture
Last modified by Martijn Woudstra on 2022/08/08 15:52
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | In the previous microlearning, we learned a bit about Design Architecture. | ||
| 3 | In this microlearning, we will build on that by learning how you can store metadata on a machine level to get clarity on what is happening. | ||
| 4 | |||
| 5 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 6 | |||
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Basic knowledge of the eMagiz platform | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| 13 | This microlearning centers around learning how to store metadata on a machine level to give you and your colleagues' insights into what is happening. | ||
| 14 | |||
| 15 | With metadata we mean: Information that tells us something about the characteristics of a machine (i.e. host, name, contact, IP-whitelisting) | ||
| 16 | |||
| 17 | Storing metadata can help you: | ||
| 18 | |||
| 19 | * See where machines are running specifically | ||
| 20 | * See who you should contact in case of troubles | ||
| 21 | * See if there are any custom settings, special consideration when updating anything on that machine | ||
| 22 | |||
| 23 | == 3. Storing Metadata - Design Architecture == | ||
| 24 | |||
| 25 | Once again we find ourselves in Design -> Architecture. | ||
| 26 | When you double click on a machine or view it via the context menu you get a pop-up detailing information that could help you. | ||
| 27 | |||
| 28 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-storing-metadata--view-machine.png]] | ||
| 29 | |||
| 30 | As you can see it is still a pretty blank page at the moment. When you press Start Editing you can edit this information | ||
| 31 | |||
| 32 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-storing-metadata--edit-machine.png]] | ||
| 33 | |||
| 34 | Let us fill in some of the details to get a feeling of how the information can help you | ||
| 35 | |||
| 36 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-storing-metadata--edit-machine-filled-in.png]] | ||
| 37 | |||
| 38 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-storing-metadata--edit-machine-filled-in-example-two.png]] | ||
| 39 | |||
| 40 | As you can see from the examples given it is quite easy to register some information on machine level in a way that all can benefit | ||
| 41 | |||
| 42 | |||
| 43 | |||
| 44 | == 4. Assignment == | ||
| 45 | |||
| 46 | The assignment is easy this time. Add relevant information on at least one machine within your project that could clarify specific information on the machine level. | ||
| 47 | This assignment can be completed with the help of an associated Mendix project linked to the (Academy) project that you have created/used in the previous assignment. | ||
| 48 | |||
| 49 | == 5. Key takeaways == | ||
| 50 | |||
| 51 | Storing metadata can help you: | ||
| 52 | |||
| 53 | * See where machines are running specifically | ||
| 54 | * See who you should contact in case of troubles | ||
| 55 | * See if there are any custom settings, special consideration when updating anything on that machine | ||
| 56 | |||
| 57 | |||
| 58 | |||
| 59 | == 6. Suggested Additional Readings == | ||
| 60 | |||
| 61 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
| 62 | |||
| 63 | == 7. Silent demonstration video == | ||
| 64 | |||
| 65 | This video demonstrates a working solution and how you can validate whether you have successfully completed the assignment. | ||
| 66 | |||
| 67 | {{video attachment="crashcourse-platform-design-storing-metadata.mp4" reference="Main.Videos.Microlearning.WebHome"/}} | ||
| 68 | |||
| 69 | )))((({{toc/}}))){{/container}}{{/container}} |