Search: "deployment plan"

Deployment is done through the deployment plan 4. On premise runtime deployment through the eMagiz portal (after installing the control agent) eliminating the need to locally install runtimes ====Runtime specific updates==== 1.

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.

Bug fixes Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.

====Bug fixes==== * Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes. * Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed. * Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.

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

Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model.

. * Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) * Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model. * Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310) * Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture.

. * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms === **Improvements** === * Performance Deployment plan When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU.

//__Random stuck in deployment plan execution__// We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

. ** HTTP Statistics - Overview *** Problematic requests *** All requests == **Feedback Items** == //__Failover deployment plan__// The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.

. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment.

With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow. //__Stop deployment plan when a property is missing__// Currently, the execution of your deployment plan continues when eMagiz notices a missing property.

This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan. //__Cap stack trace of error messages and log entries__// To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.