Skip to Content

198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14

release-blog-intro.png

Hi there, eMagiz developers! In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.

3rd generation improvements and bug fixes

"Stop" action when running a hybrid situation is not causing issues anymore
Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.

Information

Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read here

Improved efficiency in deploying a release
This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.

Removed specific dependencies between Deploy Architecture and Releases
In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.

Improved validation errors on the invalid configuration of HTTP outbound components
This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.

Improved migration behavior
This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
A smoother migration of your JMS (and backup JMS) process.
Shortening of names that otherwise would be too long, additional feedback given to the user.
Feedback when the migration process is finished.

Additional checks when deploying
This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.

Fancy Forum Answers

As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:

Key Takeaways

Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:

  • If you have questions surrounding our Program Increment Planning, please get in touch with productmanagement@emagiz.com
  • If you have feedback or ideas for us, talk to the Platypus
  • Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these. 
  • Clear your browser cache (Ctrl + Shift + Del)
  • Check out the release notes here
  • Start thinking about how the license tracker can aid your development
  • Start thinking about major, minor, and patch
  • Upgrade to the latest build number
  • Keep making great integrations

Let's stay in touch and till next time!

Information

* Indicates a Beta feature. If you would like to get access to this beta feature, please contact productmanagement@emagiz.com

** Indicates a GEN3-only feature.