Wiki source code of Solutions
Version 3.1 by Carlijn Kokkeler on 2022/10/19 12:14
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 | * Creating a CDM | ||
| 16 | By importing the Order.xsd file, the CDM should result in the following: | ||
| 17 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM.png]] | ||
| 18 | * Creating a CDM message | ||
| 19 | The CDM message data model should look like the following: | ||
| 20 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-data-model.png]] | ||
| 21 | The CDM message definition should look like the following: | ||
| 22 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-definition.png]] | ||
| 23 | * Creating a system message | ||
| 24 | By importing the TransportOrder.xsd file, the system message data model should result in the following: | ||
| 25 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-data-model.png]] | ||
| 26 | The system message definition should look like the following: | ||
| 27 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-definition.png]] | ||
| 28 | * Complete message mapping | ||
| 29 | The completed message mapping should look like the following: | ||
| 30 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-first-part.png]] | ||
| 31 | [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-second-part.png]] | ||
| 32 | |||
| 33 | == 4. Key takeaways == | ||
| 34 | |||
| 35 | * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape. | ||
| 36 | * 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. | ||
| 37 | * A system message is specific to a system. | ||
| 38 | |||
| 39 | |||
| 40 | == 5. Suggested Additional Readings == | ||
| 41 | |||
| 42 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
| 43 | |||
| 44 | |||
| 45 | |||
| 46 | )))((({{toc/}}))){{/container}}{{/container}} |