Skip to Content

Changes for page Solutions

Last modified by Carlijn Kokkeler on 2022/10/19 13:24
From version 5.1
edited by Carlijn Kokkeler
on 2022/10/19 12:23
Change comment: There is no comment for this version
To version 1.1
edited by Carlijn Kokkeler
on 2022/10/19 11:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,35 +5,30 @@
5 5  
6 6  == 1. Prerequisites ==
7 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.
8 +* Basic knowledge of the eMagiz platform
9 9  
10 10  == 2. Key concepts ==
11 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.
12 +This microlearning centers around understanding the concept data modeling in design.
13 13  
14 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 - Top of the model:
31 - [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-first-part.png]]
32 - Bottom of the model:
33 - [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-second-part.png]]
34 - As can be seen, the PickupAddress and the DeliveryAddress should both be mapped to Address. The attribute Type of Address can be set as mapped. The value can be either 'pickupaddress' or 'deliveryaddress', depending on the type of address that is applicable. This information can be added as a note:
35 - [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-note.png]]
15 +By following the steps below, you should gain a better understanding of the differences between CDM, CDM messages, and system messages.
36 36  
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 +
37 37  == 4. Key takeaways ==
38 38  
39 39  * The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.