From version 7.1
edited by Mariia Safronova
on 2026/09/09 09:39
on 2026/09/09 09:39
Change comment:
There is no comment for this version
To version 2.1
edited by Andrej Rylov
on 2025/11/19 11:40
on 2025/11/19 11:40
Change comment:
Upload new image "smc_MMP.png", version 1.1
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Data transmission from RetailEngineSystem to Smart Communications via RabbitMQ1 +Data transmission from Loymax System to Smart Communications via RabbitMQ - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. safronovams1 +XWiki.arylov - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% class="lead" %) 2 -The RetailEngineSystem allows exchanging event results with Smart Communications. This allows real-time updates on events in Smart Communications. Events are transmitted via the message broker [[RabbitMQ>>https://www.rabbitmq.com/documentation.html]].2 +The Loymax System allows exchanging event results with Smart Communications. This allows real-time updates on events in Smart Communications. Events are transmitted via the message broker [[RabbitMQ>>https://www.rabbitmq.com/documentation.html]]. 3 3 4 4 (% class="box" %) 5 5 ((( ... ... @@ -8,7 +8,7 @@ 8 8 {{toc depth="2" start="2"/}} 9 9 ))) 10 10 11 -== Data transmission process from the RetailEngineSystem to Smart Communications via RabbitMQ ==11 +== Data transmission process from the Loymax System to Smart Communications via RabbitMQ == 12 12 13 13 Let’s use the **Customer registration** event as an example. 14 14 ... ... @@ -21,10 +21,10 @@ 21 21 22 22 (% class="box infomessage" %) 23 23 ((( 24 -To transmit events to the Smart Communications platform, the [[ Retailengine.Plugins.SmartCommunications>>doc:Main.Installation_and_configuration.Additional_modules_configuring.Plugins_and_adapters.Plugins_list.WebHome||anchor="009"]] plugin must be connected. Enabling the plugin creates a dedicated queue linked to Smart Communications, and event messages are placed in that queue.24 +To transmit events to the Smart Communications platform, the [[Loymax.Plugins.SmartCommunications>>doc:Main.Installation_and_configuration.Extra_modules.Plugins_and_adapters.Plugins_list.WebHome||anchor="009"]] plugin must be connected. Enabling the plugin creates a dedicated queue linked to Smart Communications, and event messages are placed in that queue. 25 25 ))) 26 26 27 -|(% style="border-color:#ffffff; text-align:center" %){{lightbox image=" smc_MMP.png" width="900"/}}27 +|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="image 33 (2).png" width="900"/}} 28 28 29 29 == Protocols of event transmission via RabbitMQ == 30 30 ... ... @@ -49,7 +49,7 @@ 49 49 50 50 (% class="table-bordered table-scroll" %) 51 51 |=(% style="width: 20%;" %)Event|=(% style="width: 30%;" %)Description|=(% style="width: 15%;" %)Routing keys|=(% style="width: 35%;" %)Example model sent to the queue 52 -|(% style="width:20%" %)[[Registration started>>doc: Sandbox.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HRequesttostartregistration"]]|(% style="width:30%" %)The event is enqueued when a customer begins the LP registration process.|(% style="width:15%" %)customer.registration.begin|(% style="width:35%" %)(((52 +|(% style="width:20%" %)[[Registration started>>doc:Main.Integration.API.Public_Api_Methods.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HRequesttostartregistration"]]|(% style="width:30%" %)The event is enqueued when a customer begins the LP registration process.|(% style="width:15%" %)customer.registration.begin|(% style="width:35%" %)((( 53 53 {{showhide showmessage="Show model" hidemessage="Hide model"}} 54 54 ((({{code language="json"}} 55 55 { ... ... @@ -67,7 +67,7 @@ 67 67 ))) 68 68 {{/showhide}} 69 69 ))) 70 -|(% style="width:20%" %)[[Registration completed>>doc: Sandbox.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HRegistrationcompletion"]]|(% style="width:30%" %)The event is enqueued when a customer successfully completes registration.|(% style="width:15%" %)customer.registration.finish|(% style="width:35%" %)(((70 +|(% style="width:20%" %)[[Registration completed>>doc:Main.Integration.API.Public_Api_Methods.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HRegistrationcompletion"]]|(% style="width:30%" %)The event is enqueued when a customer successfully completes registration.|(% style="width:15%" %)customer.registration.finish|(% style="width:35%" %)((( 71 71 {{showhide showmessage="Show model" hidemessage="Hide model"}} 72 72 {{code language="json"}} 73 73 { ... ... @@ -85,7 +85,7 @@ 85 85 {{/showhide}} 86 86 ))) 87 87 |(% style="width:20%" %)((( 88 -[[Card linking>>doc: Sandbox.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HCardlinking"]]88 +[[Card linking>>doc:Main.Integration.API.Public_Api_Methods.Papi_examples.Customer_registration.General_algorithm.WebHome||anchor="HCardlinking"]] 89 89 )))|(% style="width:30%" %)((( 90 90 Card linking includes three events: 91 91