Exercises

In this microlearning, we will educate you on what we mean when we talk about message definitions.

Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

• Basic knowledge of the eMagiz platform

2. Key concepts

This microlearning centers around understanding the concept data modeling in design.

3. CDM, CDM & system message, message mapping

By following the steps below, you should gain a better understanding of the differences between CDM, CDM messages, and system messages.
  

3.1 Creating a CDM

Please add the following entities and attributes to your CDM:
  

• Person, with attributes ID, Name, and Email
• PlatformCourse, with attributes ID and Name

One person has access to many platform courses. It should look like the following:

3.2 Creating a CDM message

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:
 

  

3.3 Creating a system message

In System message, create the following entities and attributes:
  

• User, with attributes ID and Name
• Course, with attributes ID and Name

One user has access to many courses. It should look like the following:

Now, remove the attribute Name in Course by using the Toggle canvas edit mode. It should result in the following:

3.4 Complete message mapping

Now that you have completed these steps, go to Message mapping and complete the mapping.

4. Key takeaways

• The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.
• 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.
• A system message is specific to a system.

5. Suggested Additional Readings

If you are interested in this topic and want more information on it please read the help text provided by eMagiz.