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.

• Creating a CDM
    Please import the file Order.xsd in your CDM.
• Creating a CDM message
    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.
• Creating a system message
    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.
• Complete message mapping
    Now that you have completed these steps, go to Message mapping and complete the mapping.

The solutions to these exercises can be found here.

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.