Search: "deployment plan"
Last modified by Rico Kieboom on 2022/04/11 14:18
Refine your search
Select a category and activate filters on the current results
Last modification date
230 - Petite Peaks
Located in
- Rendered document content
Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more here. Minor changes Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
- Raw document content
Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
197 - Pay Attention
Located in
- Rendered document content
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.
- Raw document content
====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.
195 - Easter Party
Located in
- Rendered document content
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.
- Raw document content
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.
206 - Situational Deployment
Located in
- Rendered document content
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.
- Raw document content
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.
222 - Flee Frustration
Located in
- Rendered document content
. (#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.
- Raw document content
. (#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)
188 - Close Encounters
Located in
- Rendered document content
. (#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.
- Raw document content
. (#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.
210 - Deployment Delights
Located in
- Rendered document content
. (#1100) Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
- Raw document content
. (#1100) * Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. * Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck. * Deploy - Runtimes: We improved the out of memory behavior of runtimes.
220 - Patch Parade
Located in
- Rendered document content
For this fix, a new runtime image has been released. Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)
- Raw document content
For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. * Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) * Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) * Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) * Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)
212 - Failover Fiesta
Located in
- Rendered document content
More information can be found here. Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment.
- Raw document content
More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. * Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment.
185 - Get Ready
Located in
- Rendered document content
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.
- Raw document content
. * 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.