Wiki source code of Solutions
Version 2.1 by Carlijn Kokkeler on 2022/10/19 11:45
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 | * Completion of the [[exercises>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.WebHome||target="blank"]] from the Data modeling in Design use case. | ||
| 9 | |||
| 10 | == 2. Key concepts == | ||
| 11 | |||
| 12 | This microlearning contains the solutions to the [[exercises>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.WebHome||target="blank"]] from the Data modeling in Design use case. | ||
| 13 | |||
| 14 | == 3. CDM, CDM & system message, message mapping == | ||
| 15 | |||
| 16 | == 4. Key takeaways == | ||
| 17 | |||
| 18 | * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape. | ||
| 19 | * 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. | ||
| 20 | * A system message is specific to a system. | ||
| 21 | |||
| 22 | |||
| 23 | == 5. Suggested Additional Readings == | ||
| 24 | |||
| 25 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
| 26 | |||
| 27 | |||
| 28 | |||
| 29 | )))((({{toc/}}))){{/container}}{{/container}} |