Changes for page eMagiz Messaging

Last modified by Erik Bakker on 2023/01/23 13:27
From version 14.1
edited by eMagiz
on 2022/06/13 09:34
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/06/13 12:37
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,7 +1,4 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -<div class="doc">
1 +{{container}}{{container layoutStyle="columns"}}(((
5 5  
6 6  
7 7  
... ... @@ -11,9 +11,6 @@
11 11  
12 12  Should you have any questions, please get in touch with academy@emagiz.com.
13 13  
14 -* Last update: March 4th, 2022
15 -* Required reading time: 10 minutes
16 -
17 17  == 1. Prerequisites ==
18 18  
19 19  * Some context on messaging will be helpful.
... ... @@ -28,11 +28,11 @@
28 28  
29 29  The eMagiz Messaging is the pattern in which you can connect various parties via various connectivity mechanisms to the messaging engine of eMagiz. These external applications can connect in the most appropriate way (i.e., REST, SOAP, SFTP, and many more) to eMagiz. eMagiz will subsequently place the input messages on a specific queue. For example, you can distribute the message to various other external applications and deliver the messages via the connectivity method most desirable for each external application.
30 30  
31 -<p align="center">[[image:fundamental-messaging-introduction--logical-view-landscape.png||]]</p>
25 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--logical-view-landscape.png]]
32 32  
33 33  Any messaging integration in eMagiz consists of five layers. The message starts in the entry and moves via the onramp, routing, offramp, and exit to the other application.
34 34  
35 -<p align="center">[[image:fundamental-messaging-introduction--five-layers.png||]]</p>
29 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--five-layers.png]]
36 36  
37 37  === 3.1 The five layers of eMagiz Messaging ===
38 38  
... ... @@ -48,7 +48,7 @@
48 48  
49 49  The Canonical Data Model is a crucial part of the messaging pattern, which we call the CDM in layman terms. The CDM is the data model at the heart of all your messaging integration and defines how a specific message should look from your point of view. For example, when you have an Order and Invoice integration, the CDM will explain what an Order looks like, how an Invoice looks, and how the two are related (or not). Based on this model, you can select portions of the CDM to act as the CDM message for a specific message type (i.e., Order).
50 50  
51 -<p align="center">[[image:fundamental-messaging-introduction--cdm-example.png||]]</p>
45 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--cdm-example.png]]
52 52  
53 53  Critical considerations in setting up a CDM are:
54 54  
... ... @@ -60,7 +60,7 @@
60 60  
61 61  As the external parties will most likely not adhere to this standard you defined in the CDM, a crucial part of messaging integration is transforming the structure as supplied (or requested) by the external party to and from the CDM. You can quickly transform this data with the help of the eMagiz tooling in the Design phase of eMagiz. See below for an illustration.
62 62  
63 -<p align="center">[[image:fundamental-messaging-introduction--transformation-example.png||]]</p>
57 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--transformation-example.png]]
64 64  
65 65  === 3.3 Queueing ===
66 66  Within eMagiz, we use the queueing mechanism to transport messages from one queue to the other. The JMS orchestrates this mechanism of queues. The JMS registers and deregisters queues dynamically when there is a need for the queue to be created or destroyed. For example, a customer needs to be registered on any queue to pick up messages. Once the message is delivered to the next queue and the transaction is finished, the message leaves the previous queue. For a more in-depth analysis of how queues work within the platform, please check out this [microlearning](../microlearning/intermediate-orchestration-of-data-packets-queues-how-do-they-work.md).
... ... @@ -69,7 +69,7 @@
69 69  
70 70  Each messaging flow related to a messaging queue (i.e., onramp, routing, offramp, exit) contains a subprocess that will send the error to the error flow if the operational process fails. As a result, the error will show up in the Dashboard in the Manage phase of eMagiz so the user can analyze it. An example of what this Dashboard looks like can be found below.
71 71  
72 -<p align="center">[[image:fundamental-messaging-introduction--error-handling-manage-dashboard.png||]]</p>
66 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--error-handling-manage-dashboard.png]]
73 73  
74 74  With the help of this information, you can easily determine the origin of an error message. For more information on that please check out this [microlearning](../microlearning/crashcourse-platform-manage-determining-origin-of-error-message.md).
75 75  
... ... @@ -79,14 +79,14 @@
79 79  
80 80  An example of such a hybrid setup is depicted below.
81 81  
82 -<p align="center">[[image:fundamental-messaging-introduction--hybrid-architectural-setup.png||]]</p>
76 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--hybrid-architectural-setup.png]]
83 83  
84 84  Logically if all your systems are cloud systems, the most logical choice would be to deploy the complete eMagiz model within the eMagiz Cloud. An example of such a cloud setup is depicted below.
85 85  
86 -<p align="center">[[image:fundamental-messaging-introduction--cloud-architectural-setup.png||]]</p>
80 +[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--cloud-architectural-setup.png]]
87 87  
88 -===== Practice =====
89 89  
83 +
90 90  == 4. Key takeaways ==
91 91  
92 92  * Messaging uses five layers to transport data between systems
... ... @@ -106,10 +106,5 @@
106 106  
107 107  == 6. Silent demonstration video ==
108 108  
109 -<iframe width="1280" height="720" src="../../vid/fundamental/fundamental-messaging-introduction.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
110 -
111 -</div>
112 -</div>
113 -</div>
114 -
115 -{{/html}}
103 +{{video attachment="fundamental-messaging-introduction.mp4" reference="Main.Videos.Fundamental.WebHome"/}}
104 +)))((({{toc/}}))){{/container}}{{/container}}