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 8.1
edited by Carlijn Kokkeler
on 2022/10/19 13:24
on 2022/10/19 13:24
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,44 @@ 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. 15 +* Message format 16 +** To start with, make sure that the system message format is JSON: 17 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--message-format.png]] 18 +* Creating a CDM 19 +** By importing the Order.xsd file, the CDM should result in the following: 20 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM.png]] 21 +* Creating a CDM message 22 +** The CDM message data model should look like the following: 23 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-data-model.png]] 24 + The CDM message definition should look like the following: 25 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-definition.png]] 26 +* Creating a system message 27 +** By importing the TransportOrder.xsd file, the system message data model should result in the following: 28 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-data-model.png]] 29 +** The system message definition should look like the following: 30 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-definition.png]] 31 +* Complete message mapping 32 +** The completed message mapping should look like the following: 33 +** Top of the model: 34 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-first-part.png]] 35 +** Bottom of the model: 36 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-second-part.png]] 37 + 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 to the Type attribute: 38 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-note.png]] 39 +* Update the CDM and CDM message and remove the housenumber attribute 40 +** The attribute 'StreetNumber' should be removed from the entities 'PickupAddress' and 'DeliveryAddress' in the CDM: 41 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--update-CDM-streetnumber.png]] 42 +* Update the System and CDM message to set the country attributes as enumerations 43 +** In your system and CDM message, change the data type of the attribute 'Country' to 'Enumeration'. For now, the enumeration cannot be edited yet. This can be done later on in the Create phase. 44 + [[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--update-country-enumeration.png]] 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.