Search: "deployment plan"

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 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==== * When using a SOAP outbound gateway with a custom SSL web service message sender, using key- and truststores, the truststores were not correctly used in the network communication, resulting in exceptions with ‘certificate_required’. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====New features==== * Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. )))((({{toc/}}))){{/container}} {{/container}}

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==== * Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5.

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==== * Added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. * Improved the error message when configuring an Infinispan Cache Manager with 'TCP-ping' transport type, when the list of peer hosts are passed in invalid format.

. (#1053) Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282) Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293) Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.

. (#1282) * Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293) * Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05. * Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)

[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] //__Trigger activation__// Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. //__Multiple users deploying__// Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.

Minor Changes Deploy - Releases: Improved performance for deploying releases using the deployment plan. Capture - Requirements Designer: The requirements designer got a visual refresh.

. ==== Minor Changes ==== * Deploy - Releases: Improved performance for deploying releases using the deployment plan. * Capture - Requirements Designer: The requirements designer got a visual refresh.

. (#572) When a cloud slot change is pending, you will be notified. (#606) Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

. (#606) * Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) * Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

Message Redelivery - admin logs improved to better analyze issues when they occur Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed Bug fixes Deploy - Deployment plan. Performance of page to deploy a release increased significantly Store - Import resources was incorrectly done in specific cases, which is now fixed Store - Target namespace will be imported when importing an XML Message Definition Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.

. * Message Redelivery - admin logs improved to better analyze issues when they occur * Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality * Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed ====Bug fixes==== * Deploy - Deployment plan. Performance of page to deploy a release increased significantly * Store - Import resources was incorrectly done in specific cases, which is now fixed * Store - Target namespace will be imported when importing an XML Message Definition * Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. * Store - Importing items from the store sometimes resulted in invalid JMS connection factories.