Wiki source code of Exercises
Version 8.1 by Carlijn Kokkeler on 2022/09/30 10:03
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{container}}{{container layoutStyle="columns"}}((( | ||
2 | In this microlearning, we will educate you on what we mean when we talk about message definitions. | ||
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 understanding the concept data modeling in design. | ||
13 | |||
14 | == 3. CDM, CDM & system message, message mapping == | ||
15 | By following the steps below, you should gain a better understanding of the differences between CDM, CDM messages, and system messages. | ||
16 | |||
17 | == 3.1 Creating a CDM == | ||
18 | Please add the following entities and attributes to your CDM: | ||
19 | |||
20 | * Person, with attributes ID, Name, and Email | ||
21 | * PlatformCourse, with attributes ID and Name | ||
22 | |||
23 | |||
24 | One person has access to many platform courses. It should look like the following: | ||
25 | |||
26 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-attributes-entities-CDM.png]] | ||
27 | |||
28 | == 3.2 Creating a CDM message == | ||
29 | Now, go to your CDM message and add the Person and PlatformCourse to your message definition, including all attributes. It should look like the following: | ||
30 | |||
31 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-message-definition-CDM-message.png]] | ||
32 | |||
33 | == 3.3 Creating a system message == | ||
34 | In System message, create the following entities and attributes: | ||
35 | |||
36 | * User, with attributes ID and Name | ||
37 | * Course, with attributes ID and Name | ||
38 | |||
39 | |||
40 | One user has access to many courses. It should look like the following: | ||
41 | |||
42 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-attributes-entities-system-message.png]] | ||
43 | |||
44 | Now, remove the attribute Name in Course by using the Toggle canvas edit mode. It should result in the following: | ||
45 | |||
46 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--remove-attribute-system-message.png]] | ||
47 | |||
48 | == 3.4 Complete message mapping == | ||
49 | |||
50 | Now that you have completed these steps, go to Message mapping and complete the mapping. | ||
51 | |||
52 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping.png]] | ||
53 | |||
54 | |||
55 | == 4. Key takeaways == | ||
56 | |||
57 | * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape. | ||
58 | * The CDM message is tailor-made for a specific piece of data and only holds the entities and attributes relevant for that piece of data. | ||
59 | * A system message is specific to a system. | ||
60 | |||
61 | |||
62 | == 5. Suggested Additional Readings == | ||
63 | |||
64 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
65 | |||
66 | |||
67 | |||
68 | )))((({{toc/}}))){{/container}}{{/container}} |