Changes for page Exercises

Summary

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

Details

Page properties

Content

...	...	@@ -11,45 +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. Add all other entities and attributes from Order.xsd, which were imported into the CDM, to your CDM message definition.
	21	+* Creating a system message
	22	+ 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.
16	16
17		-=== 3.1 Creating entities and attributes in your CDM ===
	24	+== 3.4 Complete message mapping ==
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.
23		-
24		-One person has access to many platform courses. It should look like the following:
	26	+Now that you have completed these steps, go to Message mapping and complete the mapping.
25	25
	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"]].
26	26
	30	+== 4. Key takeaways ==
27	27
	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.
28	28
29		-== 4. Assignment ==
30	30
31		-Navigate to Design and open the message definition option of at least one integration within your project.
32		-This assignment can be completed within the (Academy) project that you have created/used in the previous assignment.
	37	+== 5. Suggested Additional Readings ==
33	33
34		-== 5. Key takeaways ==
	39	+If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
35	35
36		-* 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
37		-* Some message definitions are specific to a system. Others are generic across systems
38	38
39	39
40		-
41		-== 6. Suggested Additional Readings ==
42		-
43		-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:
44		-
45		-* [API Gateway model](crashcourse-api-gateway-api-data-model.md)
46		-* [Understanding the eMagiz CDM](crashcourse-messaging-what-is-cdm.md)
47		-* [Event Streaming data model](intermediate-configuring-event-streaming-data-model.md)
48		-
49		-== 7. Silent demonstration video ==
50		-
51		-This video demonstrates a working solution and how you can validate whether you have successfully completed the assignment.
52		-
53		-{{video attachment="crashcourse-platform-design-what-is-a-message-definition.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
54		-
55	55	)))((({{toc/}}))){{/container}}{{/container}}