Changes for page eMagiz Messaging

Last modified by Erik Bakker on 2023/01/23 13:27
From version 1.1
edited by eMagiz
on 2022/06/13 09:29
Change comment: There is no comment for this version
To version 2.1
edited by eMagiz
on 2022/06/13 09:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,20 +1,12 @@
1 1  {{html wiki="true"}}
2 2  <div class="ez-academy">
3 3   <div class="ez-academy_body">
4 -
5 -
6 - <li class="doc-nav__item"><a href="../../docs/fundamental/index_academy_fundamental_all" class="doc-nav__link">Home</a></li>
7 -
8 -
9 -
10 -
11 -
12 12  <div class="doc">
13 13  
14 14  
15 15  
16 16  = eMagiz Messaging =
17 -
9 +
18 18  In this fundamental, we will introduce the essential concepts of eMagiz Messaging. The focus will be to address the fundamental concepts of this pattern. Please refer to other Fundamentals to learn more about related items and look at the relevant microlearnings available to learn how to configure messaging flows in eMagiz.
19 19  
20 20  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -23,21 +23,22 @@
23 23  * Required reading time: 10 minutes
24 24  
25 25  == 1. Prerequisites ==
18 +
26 26  * Some context on messaging will be helpful.
27 27  
28 -
29 29  == 2. Key concepts ==
22 +
30 30  All concepts are discussed in the section below.
31 31  
32 32  
33 -
26 +
34 34  == 3. Introducing Messaging ==
35 35  
36 -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.
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.
37 37  
38 38  <p align="center">[[image:fundamental-messaging-introduction--logical-view-landscape.png||]]</p>
39 39  
40 -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.
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.
41 41  
42 42  <p align="center">[[image:fundamental-messaging-introduction--five-layers.png||]]</p>
43 43  
... ... @@ -52,6 +52,7 @@
52 52  5. Exit * the exit will read the message from the queue and then connect to the target system
53 53  
54 54  === 3.2 Canonical Data Model (CDM) ===
48 +
55 55  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).
56 56  
57 57  <p align="center">[[image:fundamental-messaging-introduction--cdm-example.png||]]</p>
... ... @@ -63,6 +63,7 @@
63 63  * Logical
64 64  
65 65  === 3.3 Transformation ===
60 +
66 66  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.
67 67  
68 68  <p align="center">[[image:fundamental-messaging-introduction--transformation-example.png||]]</p>
... ... @@ -71,6 +71,7 @@
71 71  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).
72 72  
73 73  === 3.4 Error Handling ===
69 +
74 74  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.
75 75  
76 76  <p align="center">[[image:fundamental-messaging-introduction--error-handling-manage-dashboard.png||]]</p>
... ... @@ -108,14 +108,12 @@
108 108  * [Orchestration of Data Packets](../microlearning/intermediate-orchestration-of-data-packets-index.md)
109 109  * [Additional Key Concepts Messaging](../microlearning/intermediate-key-concepts-emagiz-messaging-index.md)
110 110  
111 -
112 112  == 6. Silent demonstration video ==
113 113  
114 114  <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>
115 115  
116 -
117 117  </div>
118 -</main>
119 119  </div>
120 120  </div>
114 +
121 121  {{/html}}