Search: "deployment plan"

[[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.

. (#785) Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems.

Bug fixes Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly.

. (#785) * Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. * Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems.

====Bug fixes==== * Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) * Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) * Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly.

Deploy - Check properties: Informative error messages when saving or creating a property. (#576) Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.

Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.

. (#576) * Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps. * Deploy - Architecture: Added reset feature for 3rd generation runtimes. ====Bug fixes==== * Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows. * Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances. * Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. * Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) * Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. * Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.

In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work. Bug fixes Create - Flow Designer: We applied a new settings for the jms flow where the jms flow will try to shrink the journal files to 50 so it does not end up with a high amount of jms files which take too long to read.

In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work. ====Bug fixes==== * Create - Flow Designer: We applied a new settings for the jms flow where the jms flow will try to shrink the journal files to 50 so it does not end up with a high amount of jms files which take too long to read.

With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed.

Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime. Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step. Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.

With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed.

That helps you choose the correct integrations to add to the Create phase more quickly. * Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime. * Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step. * Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan. * Deploy - Architecture: Certificates only editable by system admin. * Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions.

Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) Manage/Event streaming statistics.

. * Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) * Manage/Event streaming statistics.

Minor changes Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side.

Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments. Design - Message Definitions: "Message format" button is also available in view mode. (#919) Remarks Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture.

====Minor changes==== * Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. * Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side.

Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments. * Design - Message Definitions: "Message format" button is also available in view mode. (#919) ====Remarks==== * Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture.