Skip to Content
Last modified by Erik Bakker on 2025/02/25 16:09
From version 19.1
edited by Erik Bakker
on 2023/01/23 13:16
Change comment: There is no comment for this version
To version 20.1
edited by Erik Bakker
on 2023/10/05 13:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,38 +23,38 @@
23 23  
24 24  == 3. Migration Path ==
25 25  
26 -1. Download the package and update the eMagiz Mendix Connector. If you are unsure how, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Mendix Connectivity.novice-mendix-connectivity-update-emagiz-mendix-connector.WebHome||target="blank"]]
27 -2. Locate the name of the queue that interacts with Mendix web service currently in place
28 -2. Remove the Web service components in the Mendix model
29 -3. At the point where this web service component was called, replace it with the appropriate Java action from the Connector module. Use the queue name located in step 1
30 -4. Use the configuration items of the Java action as described in the approriate [[microlearnings>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Mendix connectivity.WebHome||target="blank"]]
31 -6. Test if the messages are properly working
26 +* Download the package and update the eMagiz Mendix Connector. If you are unsure how, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Mendix Connectivity.novice-mendix-connectivity-update-emagiz-mendix-connector.WebHome||target="blank"]]
27 +* Locate the name of the queue that interacts with Mendix web service currently in place
28 +* Remove the Web service components in the Mendix model
29 +* At the point where this web service component was called, replace it with the appropriate Java action from the Connector module. Use the queue name located in the first step.
30 +* Use the configuration items of the Java action as described in the approriate [[microlearnings>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Mendix connectivity.WebHome||target="blank"]]
31 +* Test if the messages are properly working
32 32  
33 33  **Key considerations**
34 -- Check if [%CurrentUser%] is not used in the microflow when processing incoming messages. Mendix loses this value when using a Java action microflow. An error message is generated and the message is not processed.
35 -- Understand the impact of the user that is updating/creating the domain model object. The web service user is no longer used to update/create the domain model object
36 -- A best practice can be to store the XSDs of the various integrations into the resources folder of the mendix project so that the entire team has access to the latest
37 -- During restart of the Mendix application, there is no consumer on the synchronous response queues. Once the first message is processed, the consumer will become active. eMagiz alerting will trigger on this scenario which can be considered a false positive.
34 +* Check if [%CurrentUser%] is not used in the microflow when processing incoming messages. Mendix loses this value when using a Java action microflow. An error message is generated and the message is not processed.
35 +* Understand the impact of the user that is updating/creating the domain model object. The web service user is no longer used to update/create the domain model object
36 +* A best practice can be to store the XSDs of the various integrations into the resources folder of the mendix project so that the entire team has access to the latest
37 +* During restart of the Mendix application, there is no consumer on the synchronous response queues. Once the first message is processed, the consumer will become active. eMagiz alerting will trigger on this scenario which can be considered a false positive.
38 38  
39 39  == 4. Key takeaways ==
40 40  
41 41  Please take care of the following items when you start to use this version of the Connector to ensure you can use it properly
42 -- Use supplied Java actions in the eMagiz Mendix connector to set up the connections
43 -- These 2 libraries could cause issues with the current version of the Connector - please evaluate the necessity of these before deleting them
44 - - xerces.xercesImpl.2.8.1.jar
45 - - xmlbeans-3.0.1.jar.ExcelImporter.jar
46 -- Make sure that you configure the exits in eMagiz correctly when using the latest version of the eMagiz Mendix Connector.
42 +* Use supplied Java actions in the eMagiz Mendix connector to set up the connections
43 +* These 2 libraries could cause issues with the current version of the Connector - please evaluate the necessity of these before deleting them
44 + ** xerces.xercesImpl.2.8.1.jar
45 + ** xmlbeans-3.0.1.jar.ExcelImporter.jar
46 +* Make sure that you configure the exits in eMagiz correctly when using the latest version of the eMagiz Mendix Connector.
47 47  
48 48  == 5. Addendum eMagiz Mendix Connector 5.1.0 ==
49 49  
50 50  With the release of the newewst version of the eMagiz Mendix Connector a couple of things have changed.
51 51  
52 -- On project startup the connector-infra configuration is downloaded, installed, and started automatically.
53 - - When it is not possible to retrieve the active release, the previous connector-infra will be used.
54 - - The Configuration Overview snippet is back so you can download the release if needed.
55 -- Improved exception handling for synchronous entry integrations.
56 - - Standard eMagiz bus exceptions are recognized and converted into Mendix exceptions.
57 -- Improved way of working with synchronous exits and entries in combination with the import and export mapping (or the absence of them)
52 +* On project startup the connector-infra configuration is downloaded, installed, and started automatically.
53 + ** When it is not possible to retrieve the active release, the previous connector-infra will be used.
54 + ** The Configuration Overview snippet is back so you can download the release if needed.
55 +* Improved exception handling for synchronous entry integrations.
56 + ** Standard eMagiz bus exceptions are recognized and converted into Mendix exceptions.
57 +** Improved way of working with synchronous exits and entries in combination with the import and export mapping (or the absence of them)
58 58  
59 59  {{info}}Note that this is a brief description of how to migrate from 3.0.0 to a higher version of the eMagiz Mendix Connector. For a full migration path from 4.2.0 towards 5.X.0 please see this [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-mendix-connector-420-to-500||target="blank"]]{{/info}}
60 60