Solutions - eMagiz

1

{{container}}{{container layoutStyle="columns"}}(((

2

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

3

4

Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].

5

6

== 1. Prerequisites ==

7

8

* Completion of the [[exercises>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.WebHome||target="blank"]] from the Data modeling in Design use case.

9

10

== 2. Key concepts ==

11

12

This microlearning contains the solutions to the [[exercises>>doc:Main.eMagiz Academy.Use Cases.Data modeling in Design.Exercises.WebHome||target="blank"]] from the Data modeling in Design use case.

13

14

== 3. CDM, CDM & system message, message mapping ==

15

* Message format

16

** To start with, make sure that the system message format is JSON:

17

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--message-format.png]]

18

* Creating a CDM

19

** By importing the Order.xsd file, the CDM should result in the following:

20

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM.png]]

21

* Creating a CDM message

22

** The CDM message data model should look like the following:

23

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-data-model.png]]

24

The CDM message definition should look like the following:

25

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-CDM-message-definition.png]]

26

* Creating a system message

27

** By importing the TransportOrder.xsd file, the system message data model should result in the following:

28

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-data-model.png]]

29

** The system message definition should look like the following:

30

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--creating-a-system-message-definition.png]]

31

* Complete message mapping

32

** The completed message mapping should look like the following:

33

** Top of the model:

34

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-first-part.png]]

35

** Bottom of the model:

36

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-second-part.png]]

37

As can be seen, the PickupAddress and the DeliveryAddress should both be mapped to Address. The attribute 'Type' of Address can be set as mapped. The value can be either 'pickupaddress' or 'deliveryaddress', depending on the type of address that is applicable. This information can be added as a note to the Type attribute:

38

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--complete-message-mapping-note.png]]

39

* Update the CDM and CDM message and remove the housenumber attribute

40

** The attribute 'StreetNumber' should be removed from the entities 'PickupAddress' and 'DeliveryAddress' in the CDM:

41

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--update-CDM-streetnumber.png]]

42

* Update the System and CDM message to set the country attributes as enumerations

43

** In your system and CDM message, change the data type of the attribute 'Country' to 'Enumeration'. For now, the enumeration cannot be edited yet. This can be done later on in the Create phase.

44

[[image:Main.Images.Usecase.WebHome@data-modeling-in-design-exercises--update-country-enumeration.png]]

45

46

== 4. Key takeaways ==

47

48

* The CDM holds all entities and attributes that are relevant within the context of your complete integration landscape.

49

* 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.

50

* A system message is specific to a system.