Changes for page Entry, not a queue

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,7 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
4		-In this microlearning, we will explore what the function of the entry is within the message engine. Furthermore, we will explain why there is no entry queue.
	4	+In this microlearning, we will explore the role of the "entry" in the eMagiz message engine. You will learn why there is no entry queue and how eMagiz facilitates connectivity between external systems and internal queues. By the end, you will gain a deeper understanding of how entries initiate the integration process and ensure smooth data flow.
5	5
6	6	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7	7
...	...	@@ -21,14 +21,6 @@
21	21
22	22	== 3. Entry, not a queue ==
23	23
24		-In this microlearning, we will explore what the function of the entry is within the message engine. Furthermore, we will explain why there is no entry queue.
25		-
26		-* The key aspects are:
27		- ** Entry is the starting point of the integration process in messaging
28		- ** Queues are an internal resource of eMagiz
29		- ** Outside parties are not allowed to write on eMagiz queues directly
30		- ** eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
31		-
32	32	As you learned from the introductory course on messaging, we use a five-layer approach to handle data within the messaging engine. The first layer the data encounters is the entry. The goal of the entry is twofold. One is to establish a connection with an external system. The other is to place data on a queue. There are two ways to establish connectivity. The first method is via a pull mechanism. This pull mechanism means that eMagiz will initiate the communication to retrieve data. The second method is a push mechanism. This push mechanism means that eMagiz will patiently wait till the external system offers data to eMagiz. The push mechanism will typically be realized with the help of a hosted web service (REST or SOAP) within your eMagiz solution.
33	33
34	34	Since the goal of the entry is connectivity between the external system and eMagiz, you could argue that it would be easy to let them place the data on the queue. However, things are not that easy. There are several reasons why this is not a best practice:
...	...	@@ -38,7 +38,7 @@
38	38	* This would mean that the external system can directly place data on a queue
39	39	* This would create a tightly coupled dependency between the external system and eMagiz
40	40
41		-The above arguments concluded that the connectivity between eMagiz and the external system and the internal queue mechanism of eMagiz should be considered two separate things. This conclusion did raise a question on how eMagiz can guarantee message delivery. The messaging engine uses queues to ensure message delivery. But what if the first queue (the onramp queue) cannot be reached? What happens then.
	33	+The above arguments concluded that the connectivity between eMagiz and the external system and the internal queue mechanism of eMagiz should be considered two separate things. This conclusion did raise a question on how eMagiz can guarantee message delivery. The messaging engine uses [[queues>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Orchestration of data packets.intermediate-orchestration-of-data-packets-queues-how-do-they-work||target="blank"]] to ensure message delivery. But what if the first queue (the onramp queue) cannot be reached? What happens then.
42	42
43	43	The H2 database is introduced to safeguard against any problems within the entry. This component is generated in every entry in eMagiz. This H2 database will temporarily store data and act as a bridge between the entry and the onramp queue. This way, eMagiz can guarantee message delivery. If you want to learn more about the function of the H2 database, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-function-of-h2-database||target="blank"]].
44	44
...	...	@@ -51,11 +51,11 @@
51	51
52	52	== 4. Key takeaways ==
53	53
54		-* The key aspects are:
55		- ** Entry is the starting point of the integration process in messaging
56		- ** Queues are an internal resource of eMagiz
57		- ** Outside parties are not allowed to write on eMagiz queues directly
58		- ** eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
	46	+* Entry is the initial step of the integration process in eMagiz messaging, establishing a connection between external systems and the platform.
	47	+* Queues are an internal resource within eMagiz and are used to manage the flow and delivery of messages reliably.
	48	+* External systems are not allowed direct access to eMagiz queues, ensuring separation between external connectivity and internal processing for security and flexibility.
	49	+* eMagiz offers multiple connectivity options (e.g., REST, SOAP, Database, File) to interact with external systems, while maintaining control over data flow within the platform.
	50	+* The H2 database acts as a safeguard within the entry, temporarily storing data to guarantee message delivery if the onramp queue is unavailable.
59	59
60	60	== 5. Suggested Additional Readings ==
61	61