Search: "deployment plan"

//__Refresh behavior within the deployment plan is fixed__// This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. == **Deployment Plan** == //__Improved deployment plan to make the process better and more predictable__// The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again.

//__Store disclaimer__// Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer. == **Feedback Items** == //__Alerting manual pause__// A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser.

//__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.

** We have improved the performance of our deployment plan, it should be finished much quicker now.

{{/warning}} == **Quicker Deployment Plan Execution** == 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.

//__Deployment plan__// We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. //__View all store items__// An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.

//__Deployment execution error message__// In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.

[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] //__Runtime restart or redeploy overview__// Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

When you are finished with all runtimes navigate back to the Releases overview in Deploy and press the Deploy icon to activate your deployment plan. This is a great way to ensure that you did not accidentally miss one or more flows and will automatically ensure that the eMagiz alerting is activated again (assuming you make use of the best practices of eMagiz). == 4. Key takeaways == * Make your life easier by keeping up to date with regards to the build numbers that eMagiz releases * Determine the impact of the build number upgrade based on the release notes and the comparison functionality * Communicate before executing the upgrade * Ensure that data traffic is limited (or even better halted) during the upgrade * Verify your work by running the deployment plan == 5. Suggested Additional Readings == If you are interested in this topic and want more information on it please read the help text provided by eMagiz. )))((({{toc/}}))){{/container}}{{/container}}

Exercise == In this exercise, execute the following steps: * Make sure that either you or the trainer has the possible to deploy on Docker * Deploy the release via the deployment plan * Verify all runtimes started up == 3.

Define deployment plan & create release

crashcourse-platform-exercise-define-deployment-plan-and-create-release

This exercise will explain how you can define a deployment plan for your environment and create a release based on what we have just finished in the Create phase of eMagiz.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

{{video attachment="crashcourse-platform-exercise-define-deployment-plan-and-create-release-update.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}

Define deployment plan & create release

crashcourse-platform-exercise-define-deployment-plan-and-create-release

This exercise will explain how you can define a deployment plan for your environment and create a release based on what we have just finished in the Create phase of eMagiz.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

{{video attachment="crashcourse-platform-exercise-define-deployment-plan-and-create-release.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}