Wiki source code of What is a message mapping
Last modified by Erik Bakker on 2023/01/24 15:05
Hide last authors
author | version | line-number | content |
---|---|---|---|
24.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( | |
1.1 | 2 | ||
3 | In this microlearning, we will educate you on what we mean when we talk about message mapping | ||
4 | |||
24.1 | 5 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | |
1.1 | 6 | ||
7 | == 1. Prerequisites == | ||
8 | |||
9 | * Basic knowledge of the eMagiz platform | ||
10 | |||
11 | == 2. Key concepts == | ||
12 | |||
13 | This microlearning centers around understanding the concept of message mapping | ||
14 | |||
15 | With message mapping we mean: Drawing lines, making notes, and defining static inputs between two message definitions to identify how data elements will be transformed from the source to the target definition | ||
16 | |||
17 | In other words, the art of good message mapping lies within your ability to correctly translate between two definitions. eMagiz will help you to make that art a reality. | ||
18 | |||
19 | == 3. What is a message mapping == | ||
20 | |||
21 | A message mapping is a visual representation of how data is translated from the source definition to the target definition. | ||
22 | In all integration patterns (Messaging, API Gateway, and Event Streaming) you can translate data elements between definitions. | ||
23 | |||
24 | You can access a message mapping when you navigate to the Design phase of eMagiz. | ||
25 | |||
24.1 | 26 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-mapping--design-overview.png]] | |
1.1 | 27 | ||
28 | In this phase, you can open the context menu on the integration level (remember, that is a line between eMagiz and an external system). | ||
29 | The context menu will look slightly different for each integration pattern. These differ as the use case for each pattern differs slightly. | ||
30 | |||
24.1 | 31 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-mapping--context-menu-messaging-mapping.png]] | |
1.1 | 32 | ||
24.1 | 33 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-mapping--context-menu-api-mapping.png]] | |
1.1 | 34 | ||
24.1 | 35 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-mapping--context-menu-es-mapping.png]] | |
1.1 | 36 | ||
37 | Selecting one of the above options will lead you to an overview similar to the one shown below. | ||
38 | |||
24.1 | 39 | [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-design-what-is-a-message-mapping--message-mapping-overview.png]] | |
1.1 | 40 | ||
41 | In this overview, you can actualize the message mapping between the system (identifiable by the blue bar above the definition) and eMagiz (identifiable by the green bar above the definition). | ||
42 | In the next microlearning, we will continue to actualize the message mapping so we can transform the data between the external system and eMagiz. | ||
43 | |||
44 | This assignment can be completed within the (Academy) project that you have created/used in the previous assignment. | ||
45 | |||
28.1 | 46 | == 4. Key takeaways == | |
1.1 | 47 | ||
48 | With message mapping we mean: Drawing lines, making notes, and defining static inputs between two message definitions to identify how data elements will be transformed from the source to the target definition | ||
49 | In other words, the art of good message mapping lies within your ability to correctly translate between two definitions. eMagiz will help you to make that art a reality. | ||
50 | |||
28.1 | 51 | == 5. Suggested Additional Readings == | |
1.1 | 52 | ||
53 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
24.1 | 54 | )))((({{toc/}}))){{/container}}{{/container}} |