Skip to Content

Changes for page Exercises

Last modified by Carlijn Kokkeler on 2022/10/19 13:32
From version 5.1
edited by Carlijn Kokkeler
on 2022/09/30 09:32
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2022/10/19 11:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,46 +11,33 @@
11 11  
12 12  This microlearning centers around understanding the concept data modeling in design.
13 13  
14 -== 3. Please complete the following steps ==
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 15  
17 +* Creating a CDM
18 + Please import the file Order.xsd in your CDM.
19 +* Creating a CDM message
20 + Now, go to your CDM message and select Order as root entity.
21 + Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition.
22 +* Creating a system message
23 + In one of your System messages, import the file TransportOrder.xsd.
24 + Select CreateOrder as root entity and add all other entities and attributes to your system definition.
25 +* Complete message mapping
26 + Now that you have completed these steps, go to Message mapping and complete the mapping.
16 16  
17 -=== 3.1 Creating entities and attributes in your CDM ===
28 +The solutions to these exercises can be found [[here>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.Solutions.WebHome||target="blank"]].
18 18  
19 -Please add the following entities and attributes to your CDM:
20 -
21 -* Person, with attributes ID, Name, and Email.
22 -* PlatformCourse, with attributes ID and Name.
30 +== 4. Key takeaways ==
23 23  
32 +* The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.
33 +* 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.
34 +* A system message is specific to a system.
24 24  
25 -One person has access to many platform courses. It should look like the following:
26 26  
37 +== 5. Suggested Additional Readings ==
27 27  
39 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
28 28  
29 29  
30 -== 4. Assignment ==
31 31  
32 -Navigate to Design and open the message definition option of at least one integration within your project.
33 -This assignment can be completed within the (Academy) project that you have created/used in the previous assignment.
34 -
35 -== 5. Key takeaways ==
36 -
37 -* A message definition is a visual representation of how the elements are related to each other, whether they are mandatory and the data types they have that can be used in the message mapping
38 -* Some message definitions are specific to a system. Others are generic across systems
39 -
40 -
41 -
42 -== 6. Suggested Additional Readings ==
43 -
44 -If you are interested in this topic and want more information on it please read the help text provided by eMagiz. Furthermore check out these links if you want a more in-depth knowledge of the eMagiz data models:
45 -
46 -* [API Gateway model](crashcourse-api-gateway-api-data-model.md)
47 -* [Understanding the eMagiz CDM](crashcourse-messaging-what-is-cdm.md)
48 -* [Event Streaming data model](intermediate-configuring-event-streaming-data-model.md)
49 -
50 -== 7. Silent demonstration video ==
51 -
52 -This video demonstrates a working solution and how you can validate whether you have successfully completed the assignment.
53 -
54 -{{video attachment="crashcourse-platform-design-what-is-a-message-definition.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
55 -
56 56  )))((({{toc/}}))){{/container}}{{/container}}