Skip to Content

Changes for page eMagiz Messaging

Last modified by Erik Bakker on 2024/08/19 21:27
From version 15.1
edited by Erik Bakker
on 2022/06/13 12:37
Change comment: Imported from XAR
To version 17.1
edited by Erik Bakker
on 2022/06/13 13:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +eMagiz Messaging
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Content
... ... @@ -1,9 +1,4 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -
3 -
4 -
5 -= eMagiz Messaging =
6 -
7 7  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.
8 8  
9 9  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -16,8 +16,6 @@
16 16  
17 17  All concepts are discussed in the section below.
18 18  
19 -
20 -
21 21  == 3. Introducing Messaging ==
22 22  
23 23  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.
... ... @@ -57,7 +57,7 @@
57 57  [[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--transformation-example.png]]
58 58  
59 59  === 3.3 Queueing ===
60 -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).
53 +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>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Orchestration of data packets.intermediate-orchestration-of-data-packets-queues-how-do-they-work.WebHome||target="blank"]].
61 61  
62 62  === 3.4 Error Handling ===
63 63  
... ... @@ -65,7 +65,7 @@
65 65  
66 66  [[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--error-handling-manage-dashboard.png]]
67 67  
68 -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).
61 +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>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message.WebHome||target="blank"]].
69 69  
70 70  === 3.5 Architectural components ===
71 71  
... ... @@ -79,8 +79,6 @@
79 79  
80 80  [[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--cloud-architectural-setup.png]]
81 81  
82 -
83 -
84 84  == 4. Key takeaways ==
85 85  
86 86  * Messaging uses five layers to transport data between systems
... ... @@ -89,14 +89,12 @@
89 89  * Errors from the messaging flows show up in the manage dashboard
90 90  * Messaging runtimes should be deployed as close to the system as possible
91 91  
92 -
93 -
94 94  == 5. Suggested Additional Readings ==
95 95  
96 -* [Messaging Introduction](https://www.emagiz.com/en/messaging-en/)
97 -* [Crashcourse Messaging](../microlearning/crashcourse-messaging-index.md)
98 -* [Orchestration of Data Packets](../microlearning/intermediate-orchestration-of-data-packets-index.md)
99 -* [Additional Key Concepts Messaging](../microlearning/intermediate-key-concepts-emagiz-messaging-index.md)
85 +* [[Messaging Introduction>>https://www.emagiz.com/en/messaging-en/||target="blank"]]
86 +* [[Crashcourse Messaging>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
87 +* [[Orchestration of Data Packets>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Orchestration of data packets.WebHome||target="blank"]]
88 +* [[Additional Key Concepts Messaging>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Key concepts eMagiz Messaging.WebHome||target="blank"]]
100 100  
101 101  == 6. Silent demonstration video ==
102 102