Changes for page Calling an Asynchronous Queue in Mendix

Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In this microlearning, we will integrate Mendix with eMagiz using the eMagiz Mendix module. Here, we will guide you through calling a synchronous queue in Mendix, essential for efficient data exchange between your systems.
	2	+In this microlearning, we will integrate Mendix with eMagiz using the eMagiz Mendix module. Here, we will guide you through calling an asynchronous queue in Mendix, essential for efficient data exchange between your systems.
3	3
4	4	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
...	...	@@ -15,10 +15,10 @@
15	15
16	16	== 2. Key concepts ==
17	17
18		-This microlearning centers around calling a synchronous queue in Mendix.
19		-* With eMagiz Connector, we mean A Mendix module developed and maintained by eMagiz that simplifies connecting a Mendix application to an eMagiz project for data traffic between both systems.
	18	+This microlearning centers around calling an asynchronous queue in Mendix.
	19	+* With eMagiz Connector, we mean a Mendix module developed and maintained by eMagiz that simplifies connecting a Mendix application to an eMagiz project for data traffic between both systems.
20	20
21		-To call a synchronous queue in Mendix, you need the following:
	21	+To call an asynchronous queue in Mendix, you need the following:
22	22
23	23	* The destination (i.e., the queue from which you want to retrieve the information)
24	24	* Execute microflow (the microflow that will process the incoming data)
...	...	@@ -26,40 +26,40 @@
26	26
27	27	{{warning}}All changes in eMagiz need to be activated by adding the changes to the eMagiz release and activating said release. When setting up the initial connection, the Mendix system must be **in** the eMagiz release before connecting from Mendix to eMagiz with an **activation key**.{{/warning}}
28	28
29		-== 3. Calling a synchronous queue in Mendix ==
	29	+== 3. Calling an asynchronous queue in Mendix ==
30	30
31		-With the help of the Mendix module (called eMagiz Connector) created by the eMagiz team, you can easily connect between Mendix and eMagiz for data integration. This microlearning will focus on calling a synchronous queue in Mendix. For sending data to Mendix, we offer three options to send data:
	31	+With the help of the Mendix module (called eMagiz Connector) created by the eMagiz team, you can easily connect between Mendix and eMagiz for data integration. This microlearning will focus on calling an asynchronous queue in Mendix. For sending data to Mendix, we offer three options to send data:
32	32
33		-* Using the import and export mapping to send data to Mendix.
34		-* Sending a string to and from Mendix without using the import and export mapping.
	33	+* Using the import mapping to send data to Mendix.
	34	+* Sending a string to Mendix without using the import mapping.
35	35	* Any combination of the two above.
36	36
37		-Below, we will detail how to configure each option for sending data synchronously to Mendix.
	37	+Below, we will detail how to configure each option for sending data asynchronously to Mendix.
38	38
39		-=== 3.1 Sending synchronous messages with import and export mapping ===
	39	+=== 3.1 Sending asynchronous messages with import and export mapping ===
40	40
41		-To send data to Mendix, you must define several configuration options in the Mendix project. In this example, we will look at the configuration using the import and export mapping in Mendix. In the subsequent paragraph, we will look at configuring the exit if you do **not** want to use the import and export mapping.
	41	+To send data to Mendix, you must define several configuration options in the Mendix project. In this example, we will look at the configuration using the import mapping in Mendix. In the subsequent paragraph, we will look at configuring the exit if you do **not** want to use the import mapping.
42	42
43	43	In eMagiz, you will see a flow in Create that you cannot edit, as the autogenerated functionality provided by eMagiz is all you need. Once done, make sure the flow is transported to Deploy and ready to be used in a Mendix application by adding it to a release.
44	44
45	45	{{info}}The exit version must be altered when you change your system messages in Design.{{/info}}
46	46
47		-In parallel, earlier or later, the Mendix application needs to be developed to handle the message's consumption and respond to the request with a response mapping. This is done by adding the following configuration to the existing "After Startup" microflow.
	47	+In parallel, earlier or later, the Mendix application needs to be developed to handle the message's consumption. This is done by adding the following configuration to the existing "After Startup" microflow.
48	48
49	49	==== 3.1.1 Startup action ====
50		-In Mendix, you must add the "StartSyncMessageConsumer" Java Action to the after startup flow. The most important configuration items here are the following.
	50	+In Mendix, you must add the "StartMessageConsumer" Java Action to the after startup flow. The most important configuration items here are the following.
51	51
52		-[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix-start-consumer.png]]
	52	+[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix-start-consumer.png]]
53	53
54		-* The destination (i.e., the queue from which you want to consume the **request** messages). This can be supplied by the eMagiz developer or found under Deploy -> Mendix Connectors should you have access to the eMagiz model in question.
55		-* The export and import mapping (based on the system message definitions). These definitions can be determined by the eMagiz developer (and then shared with the Mendix developer) or determined by the Mendix developer (and then shared with the eMagiz developer).
56		-* The microflow that handles the incoming message and returns a result.
	54	+* The destination (i.e., the queue from which you want to consume the messages). This can be supplied by the eMagiz developer or found under Deploy -> Mendix Connectors should you have access to the eMagiz model in question.
	55	+* The import mapping (based on the system message definitions). These definitions can be determined by the eMagiz developer (and then shared with the Mendix developer) or determined by the Mendix developer (and then shared with the eMagiz developer).
	56	+* The microflow that handles the incoming message.
57	57
58		-[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix-on-receive-microflow-config.png]]
	58	+[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix-on-receive-microflow-config.png]]
59	59
60		-=== 3.2 Sending synchronous messages without import and export mapping ===
	60	+=== 3.2 Sending asynchronous messages without import and export mapping ===
61	61
62		-We just saw the example when working with the import and export mapping. Now we turn our attention to an instance without those mappings. In these cases, the string is just passed to the execute microflow, and you can determine in Mendix yourself what to do with it. The same applies to the export part of the logic.
	62	+We just saw the example when working with the import mapping. Now we turn our attention to an instance without that mapping. In these cases, the string is just passed to the execute microflow, and you can determine in Mendix yourself what to do with it.
63	63
64	64	In eMagiz, you will see a flow in Create that you cannot edit, as the autogenerated functionality provided by eMagiz is all you need. Once done, make sure the flow is transported to Deploy and ready to be used in a Mendix application by adding it to a release.
65	65
...	...	@@ -68,18 +68,18 @@
68	68	In parallel, earlier or later, the Mendix application needs to be developed to handle the consumption of the message and respond to the request with a response mapping. This is done by adding the following configuration to the existing "After Startup" microflow.
69	69
70	70	==== 3.1.1 Startup action ====
71		-In Mendix, you must add the "StartSyncStringConsumer" Java Action to the after startup flow. The most important configuration items here are the following.
	71	+In Mendix, you must add the "StartStringConsumer" Java Action to the after startup flow. The most important configuration items here are the following.
72	72
73		-[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix-start-consumer-string.png]]
	73	+[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix-start-consumer-string.png]]
74	74
75	75	* The destination (i.e., the queue from which you want to consume the **request** messages). This can be supplied by the eMagiz developer or found under Deploy -> Mendix Connectors should you have access to the eMagiz model in question.
76	76	* The microflow that handles the incoming message and returns a result.
77	77
78		-[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-a-synchronous-webservice-in-mendix-on-receive-microflow-config-string.png]]
	78	+[[image:Main.Images.Microlearning.WebHome@intermediate-mendix-connectivity-calling-an-asynchronous-webservice-in-mendix-on-receive-microflow-config-string.png]]
79	79
80	80	== 4. Key takeaways ==
81	81
82		-To call a synchronous queue in Mendix, you need the following:
	82	+To call an asynchronous queue in Mendix, you need the following:
83	83
84	84	* The destination (i.e., the queue from which you want to retrieve the information)
85	85	* Execute microflow (the microflow that will process the incoming data)