Skip to Content
Last modified by Erik Bakker on 2025/02/25 16:09
From version 10.1
edited by Erik Bakker
on 2022/07/27 14:08
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/07/27 14:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  This document describes the difference between the 3.0 version of the eMagiz Mendix Connector and the 4.X and onwards versions of the eMagiz Mendix Connector. On top of that it describes the checks and balances one has to go through while migrating from the 3.0 version to a newer version.
4 4  
5 -== 1. Positioning of the eMagiz Connector for Mendix 8 package ==
5 +== 1. Positioning ==
6 6  
7 7  This packages has been created to support clients that are moving towards Mendix 8 in their environment. The latest version of eMagiz has been upgraded to use AMQP queues, which effectively means that direct connections from Mendix to onramp and offramp queues can be made. This has a positive effect as less effort is required in Mendix to interact with eMagiz and there is an easier management of the environment as only the infra flows need to be deployed (no exit and entry flows managed in Mendix).
8 8  
... ... @@ -12,7 +12,7 @@
12 12  
13 13  Please find the package on the usual location: Under Deploy --> On-premise --> Runtime downloads tab
14 14  
15 -== 2. Comparing eMagiz Mendix connector ==
15 +== 2. Comparison ==
16 16  
17 17  | Mendix V6/V7 Connector| Mendix V8 Connector|
18 18  | ------ | ------ |
... ... @@ -21,7 +21,7 @@
21 21  | Each flow (exit, entry and infra) needs to be deployed | Only infra flow needs to be deployed once, microflows connected to the queues directly|
22 22  |Incoming webservice|Microflow - Java action details |
23 23  
24 -== 3. General steps to move from previous eMagiz Connector versions to this version ==
24 +== 3. Migration Path ==
25 25  
26 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 27  2. Locate the name of the queue that interacts with Mendix web service currently in place
... ... @@ -35,9 +35,8 @@
35 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 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 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 -
39 39  
40 -== 4. Key notes in using this package ==
39 +== 4. Key takeaways ==
41 41  
42 42  Please take care of the following items when you start to use this version of the Connector to ensure you can use it properly
43 43  - Use supplied Java actions in the eMagiz Mendix connector to set up the connections