Changes for page Entry, not a queue

Summary

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

Details

Page properties

Content

...	...	@@ -21,6 +21,14 @@
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	+
24	24	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.
25	25
26	26	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:
...	...	@@ -43,11 +43,11 @@
43	43
44	44	== 4. Key takeaways ==
45	45
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.
	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)
51	51
52	52	== 5. Suggested Additional Readings ==
53	53