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

Summary

Details

Page properties
Content
... ... @@ -27,7 +27,7 @@
27 27  2. Locate the name of the queue that interacts with Mendix web service currently in place
28 28  2. Remove the Web service components in the Mendix model
29 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"]]
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 31  6. Test if the messages are properly working
32 32  
33 33  **Key considerations**
... ... @@ -56,7 +56,7 @@
56 56   - Standard eMagiz bus exceptions are recognized and converted into Mendix exceptions.
57 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 -{{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-4.2.0-to-5.0.0.WebHome||target="blank"]]{{/info}}
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-4~.~2~.~0-to-5~.~0~.~0.WebHome||target="blank"]]{{/info}}
60 60  
61 61  === 5.1 Infra download, installation and starting ===
62 62  
... ... @@ -65,7 +65,7 @@
65 65  
66 66  [[image:Main.Images.Migrationpath.WebHome@emc8-after-startup-retrieve-infra.png]]
67 67  
68 -This way you never have to execute those steps and eMagiz ensures that the Infra flow is the first to start up before any exits are registered.
68 +This way you never have to execute those steps and eMagiz ensures that the Infra flow is the first to start up before any exits are registered.
69 69  To make this possible we have added logic to the AfterStartup microflow of eMagiz to retrieve the properties from eMagiz, download the infra and start the infra.
70 70  
71 71  In case there is a problem with internet connectivity or you simply cannot reach eMagiz, the microflow ensures that the latest known infra will be started up.