Search: "deployment plan"

. == **Next generation improvements and bug fixes** == //__Enhanced right-hand view within Deployment Plan context__// When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly.

{{/info}} //__Improved timeout settings when deploying__// To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.

//__Deployment execution error message__// In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.

[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] //__Runtime restart or redeploy overview__// Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Minor changes==== * Tracing errors in flow testing has been improved.

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * The JMS server could fail to startup when migrating from the Spring 5 to the Spring 6 runtime in case a queue existed that at one point was auto-created, but no longer had a matching address setting. )))((({{toc/}}))){{/container}} {{/container}}

For more information, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * Support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names. * Updates our Java runtime version from Java 17.0.13 to Java 17.0.15.

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * We improved the out of memory behavior of next generation architecture runtimes.

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * SFTP session factories did not close their connection after it was complete.

For more information, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * Support for the ‘NTCredentials’ authentication method in a custom HttpComponentsMessageSender support object has been reintroduced. * In some edge cases, log messages produced with the Logging channel adapter component did not reach the Manage phase.

Among these improvements, we have improved the performance of the deployment plan, and we made sure that you can analyze your XML validation errors from the Manage Dashboard once more.

==**Import definition with multiple namespace from the store**== On top of that, we have made it possible that when you import a message definition from the store that contains multiple namespaces (typical for EDI), eMagiz will automatically import all namespaces and link the namespaces to the correct entities and attributes of your system message. == **Bug fixes ** == See below for all bug fixes that are solved with this release //__Deployment plan improvements__// Previously, when you tried to execute your deployment plan (especially in larger environments), this could take a while. Both in terms of opening and managing the deployment plan. With this release, we have made structural changes that will improve the opening and execution of the deployment plan.

The complete list is as follows. * Deploy → Deployment Plan * Deploy → Properties → History * Deploy → User Management → Roles * Manage → Error Messages → Error Messages * Manage → Error Messages → Flows with Error Messages * Manage → Error Messages → Exceptions of Error Messages * Manage → Log Entries * Manage → Alerts * Manage → Triggers * Manage → Tags – Cant find (only Gen2) * Manage → Notifications * Manage → Notification Settings * Manage → Data Usage → History * Manage → Code mappings → All tabs == **Bug fixes ** == //__Loading problems of Deployment plan execution overview__// We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.