Changes for page Exercises

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -9,71 +9,60 @@
9	9
10	10	== 2. Key concepts ==
11	11
12		-This microlearning centers around understanding the concept of the message definition.
	12	+This microlearning centers around understanding the concept data modeling in design.
13	13
14		-With message definition we mean: 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
	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	+
	17	+== 3.1 Creating a CDM ==
	18	+Please add the following entities and attributes to your CDM:
	19	+
	20	+* Person, with attributes ID, Name, and Email
	21	+* PlatformCourse, with attributes ID and Name
15	15
16		-In other words, the message definition defines the structure of the data that will be sent or received.
17	17
18		-== 3. What is a message definition ==
	24	+One person has access to many platform courses. It should look like the following:
19	19
20		-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.
21		-In all integration patterns (Messaging, API Gateway, and Event Streaming) we have message definitions.
	26	+[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-attributes-entities-CDM.png]]
22	22
23		-On one hand, we have message definitions that relate to a system.
24		-These definitions tell us something about how the system will send or wants to receive messages (data).
25		-On the other hand, we have message definitions that relate to eMagiz.
26		-These are generic and consistent across systems (i.e. CDM messages, Gateway messages, Topic messages).
	28	+== 3.2 Creating a CDM message ==
	29	+Now, go to your CDM message and add the Person and PlatformCourse to your message definition, including all attributes. It should look like the following:
	30	+
	31	+[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-message-definition-CDM-message.png]]
	32	+
	33	+== 3.3 Creating a system message ==
	34	+In System message, create the following entities and attributes:
	35	+
	36	+* User, with attributes ID and Name
	37	+* Course, with attributes ID and Name
27	27
28		-[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-definition--design-overview.png]]
29	29
30		-In this phase, you can open the context menu on the integration level (remember, that is a line between eMagiz and an external system).
31		-The context menu will look slightly different based on the integration pattern. These differ as the use cases for each pattern differ slightly.
	40	+One user has access to many courses. It should look like the following:
32	32
33		-[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-definition--context-menu-messaging-definition.png]]
	42	+[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--adding-attributes-entities-system-message.png]]
34	34
35		-[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-definition--context-menu-api-definition.png]]
	44	+Now, remove the attribute Name in Course by using the Toggle canvas edit mode. It should result in the following:
36	36
37		-[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-definition--context-menu-es-definition.png]]
	46	+[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--remove-attribute-system-message.png]]
	47	+
	48	+== 3.4 Complete message mapping ==
38	38
39		-Selecting one of the above options will lead you to an overview similar to the one that is shown below.
	50	+Now that you have completed these steps, go to Message mapping and complete the mapping.
40	40
41		-[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-definition--message-definition.png]]
	52	+[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping.png]]
	53	+
42	42
43		-In this overview, you can import a definition or create one yourself.
	55	+== 4. Key takeaways ==
44	44
45		-=== 3.1 eMagiz datamodels ===
	57	+* The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.
	58	+* 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.
	59	+* A system message is specific to a system.
46	46
47		-Above the focus was on the system messages (i.e. the definitions as defined by the external system). Within each of the patterns eMagiz supports (Messaging, API Management, and Event Streaming) we support an eMagiz data model. In these data models you can define how the messages should look like when they pass through the system of eMagiz. When creating a message transformation you always have atleast one eMagiz part that is based on an eMagiz data model. This is needed as you need to transform from the external system to the eMagiz data model for example.
48	48
49		-In messaging terms we call this eMagiz data model a CDM for example. Based on the pattern you are implementing the naming can change slightly but the conceptual idea is the same. For more information on the various data models we support for the patterns please check out the suggested additional readings section below.
	62	+== 5. Suggested Additional Readings ==
50	50
	64	+If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
51	51
52	52
53		-== 4. Assignment ==
54	54
55		-Navigate to Design and open the message definition option of at least one integration within your project.
56		-This assignment can be completed within the (Academy) project that you have created/used in the previous assignment.
57		-
58		-== 5. Key takeaways ==
59		-
60		-* 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
61		-* Some message definitions are specific to a system. Others are generic across systems
62		-
63		-
64		-
65		-== 6. Suggested Additional Readings ==
66		-
67		-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:
68		-
69		-* [API Gateway model](crashcourse-api-gateway-api-data-model.md)
70		-* [Understanding the eMagiz CDM](crashcourse-messaging-what-is-cdm.md)
71		-* [Event Streaming data model](intermediate-configuring-event-streaming-data-model.md)
72		-
73		-== 7. Silent demonstration video ==
74		-
75		-This video demonstrates a working solution and how you can validate whether you have successfully completed the assignment.
76		-
77		-{{video attachment="crashcourse-platform-design-what-is-a-message-definition.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
78		-
79	79	)))((({{toc/}}))){{/container}}{{/container}}