Search: "deployment plan"

{{info}} At any given moment when you are satisfied with your configuration, you can press "Save" to store your changes for the runtime settings {{/info}} === 3.3 Effectuate changes on architecture === To effectuate the changes made to your deployed architecture, you should create a new release and deploy this via the deployment plan. In case you need more information on the creation of releases or deploying release you can check that information [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] and [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4. Key takeaways == * On the runtime level in Deploy -> Architecture, you have a context menu item called "Runtime Settings." * In this context menu item, you can configure the HTTP Settings and whether the control bus is enabled. * HTTP Settings are needed when hosting a SOAP or REST web service. ** When enabling, the port needs to be filled in. ** Optionally, you can configure one-way or two-way SSL for an on-premise endpoint. * By disabling the control bus, you will lose (parts of) the functionality that allows you to view or halt data. ** Queue browser. ** Message redelivery. ** Start/Stop flow components. * Changes must be deployed by creating a new release and deploying it via a deployment plan. == 5. Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] *** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] *** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Securing Data Traffic (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.WebHome||target="blank"]] *** [[Securing a hosted web service with certificates in the eMagiz Cloud (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.intermediate-securing-your-data-traffic-securing-a-hosted-webservice-with-certificates-in-the-emagiz-cloud||target="blank"]] *** [[Creating a JKS (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.intermediate-securing-your-data-traffic-creating-a-jks||target="blank"]] * [[Runtime Settings (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

New features Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

Bug fixes Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.

It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message.

====New features==== * Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. * Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

====Bug fixes==== * Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors.

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.

In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default.

Minor changes Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.

Bug fixes Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.

In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default.

====Minor changes==== * Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. * Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. * Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server. ====Bug fixes==== * Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. * Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. * Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.

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.

We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.

Minor changes Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model.

On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you still need to enable triggers manually if you have manually disabled them before deploying.

We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.

====Minor changes==== * Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model.

On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you **still** need to enable triggers manually if you have manually disabled them before deploying.

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.

We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Find out all the improvements and bug fixes below!

Note that the timer starts when your deployment plan's "disable" step is finished. [[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]] {{warning}}Note that the end action is only triggered when the deployment plan cannot complete all steps.

This also covers cases where the deployment plan is automatically executed (by pressing the play button), after which the user moves on to other things and forgets to move away from the page once the deployment plan is completed.

. (#1423) Deploy - Architecture: The helptext of volume mappings has been improved. (#1405) Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

. (#1405) * Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan. * Deploy - History: We added logging for when properties are deleted from the unused properties screen. (#1428) * Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview.

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.