Solutions
Version 3.1 by Carlijn Kokkeler on 2022/10/19 12:14
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
- Completion of the exercises from the Data modeling in Design use case.
2. Key concepts
This microlearning contains the solutions to the exercises from the Data modeling in Design use case.
3. CDM, CDM & system message, message mapping
- Creating a CDM
By importing the Order.xsd file, the CDM should result in the following:
- Creating a CDM message
The CDM message data model should look like the following:
The CDM message definition should look like the following:
- Creating a system message
By importing the TransportOrder.xsd file, the system message data model should result in the following:
The system message definition should look like the following:
- Complete message mapping
The completed message mapping should look like the following:
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.