Changes for page Solutions
Last modified by Carlijn Kokkeler on 2022/10/19 13:24
From version 1.1
edited by Carlijn Kokkeler
on 2022/10/19 11:36
on 2022/10/19 11:36
Change comment:
There is no comment for this version
To version 2.1
edited by Carlijn Kokkeler
on 2022/10/19 11:45
on 2022/10/19 11:45
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,30 +5,14 @@ 5 5 6 6 == 1. Prerequisites == 7 7 8 -* Basic knowledgeof the eMagizplatform8 +* 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 9 10 10 == 2. Key concepts == 11 11 12 -This microlearning c entersaroundunderstandingtheconceptdata modeling indesign.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 13 14 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 16 17 -== 3.1 Creating a CDM == 18 -Please import the file Order.xsd in your CDM. 19 - 20 -== 3.2 Creating a CDM message == 21 -Now, go to your CDM message and select Order as root entity. Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition. 22 - 23 -== 3.3 Creating a system message == 24 -In one of your System messages, import the file TransportOrder.xsd. Select CreateOrder as root entity and add all other entities and attributes to your system definition. 25 - 26 -== 3.4 Complete message mapping == 27 - 28 -Now that you have completed these steps, go to Message mapping and complete the mapping. 29 - 30 -The solutions to these exercises can be found here. 31 - 32 32 == 4. Key takeaways == 33 33 34 34 * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.