Wiki source code of Exercises
Version 13.1 by Carlijn Kokkeler on 2022/10/19 11:42
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 | * Creating a CDM | ||
| 18 | Please import the file Order.xsd in your CDM. | ||
| 19 | * Creating a CDM message | ||
| 20 | Now, go to your CDM message and select Order as root entity. | ||
| 21 | Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition. | ||
| 22 | * Creating a system message | ||
| 23 | In one of your System messages, import the file TransportOrder.xsd. | ||
| 24 | Select CreateOrder as root entity and add all other entities and attributes to your system definition. | ||
| 25 | * Complete message mapping | ||
| 26 | Now that you have completed these steps, go to Message mapping and complete the mapping. | ||
| 27 | |||
| 28 | The solutions to these exercises can be found [[here>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.Solutions.WebHome||target="blank"]]. | ||
| 29 | |||
| 30 | == 4. Key takeaways == | ||
| 31 | |||
| 32 | * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape. | ||
| 33 | * 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. | ||
| 34 | * A system message is specific to a system. | ||
| 35 | |||
| 36 | |||
| 37 | == 5. Suggested Additional Readings == | ||
| 38 | |||
| 39 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
| 40 | |||
| 41 | |||
| 42 | |||
| 43 | )))((({{toc/}}))){{/container}}{{/container}} |