Search: "deployment plan"

. (#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.

This can be disabled by changing the machine step in your deployment plan. Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.

This can be disabled by changing the machine step in your deployment plan. * Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) * Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it. * General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser.

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. * Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. * Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser.

. (#958) Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982) Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990) Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972) Manage - Manage Dashboards: The screen loading speed is significantly improved for all models.

. (#982) * Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990) * Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972) * Manage - Manage Dashboards: The screen loading speed is significantly improved for all models.

In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.

Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing. Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009) Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993) Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.

In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.

====Minor changes==== * Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845) * Create - Framework: The framework used in the flow designer has been updated, improving performance. * Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing. * Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009) * Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993) * Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase. * Deploy - Release properties: The description of a property can be changed by editing the property. (#1064) * Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines. * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well. * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy. * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024) * Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications. * Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069) * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070) * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) * Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action. * Administration - My account: When changing a password, it is compared to a list of known database breaches for security.