Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 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 | |||
| |
2.1 | 12 | This microlearning centers around understanding the concept data modeling in design. |
| |
1.1 | 13 | |
| |
6.1 | 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 | ||
| |
1.1 | 22 | |
| 23 | |||
| |
6.1 | 24 | One person has access to many platform courses. It should look like the following: |
| |
1.1 | 25 | |
| |
6.1 | 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: | ||
| |
2.1 | 30 | |
| |
6.1 | 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 | ||
| |
5.1 | 38 | |
| 39 | |||
| |
6.1 | 40 | One user has access to many courses. It should look like the following: |
| |
1.1 | 41 | |
| |
6.1 | 42 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-attributes-entities-system-message.png]] |
| |
1.1 | 43 | |
| |
6.1 | 44 | Now, remove the attribute Name in Course by using the Toggle canvas edit mode. It should result in the following: |
| |
1.1 | 45 | |
| |
6.1 | 46 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--remove-attribute-system-message.png]] |
| 47 | |||
| |
7.1 | 48 | == 3.4 Complete message mapping == |
| |
1.1 | 49 | |
| |
6.1 | 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 | |||
| |
1.1 | 54 | |
| |
8.1 | 55 | == 4. Key takeaways == |
| |
1.1 | 56 | |
| |
8.1 | 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. | ||
| |
1.1 | 60 | |
| 61 | |||
| |
8.1 | 62 | == 5. Suggested Additional Readings == |
| |
1.1 | 63 | |
| |
8.1 | 64 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. |
| |
1.1 | 65 | |
| 66 | |||
| 67 | |||
| 68 | )))((({{toc/}}))){{/container}}{{/container}} |