Search: "deployment plan"

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan-gen3

The release is active in that all changes made to it compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a basic Deployment plan.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan-gen3.png]] Running a deployment plan means machines are stopped, and new images are deployed. eMagiz does this by comparing your currently running release and the recent release you have activated.

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we will focus on setting up a deployment plan and learn about the considerations when setting up such a deployment plan.

Active in that all changes made to the release compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a very basic Deployment plan.

crashcourse-platform-deploy-execute-deployment-plan-pic1.png

crashcourse-platform-deploy-execute-deployment-plan-pic2.png

crashcourse-platform-deploy-execute-deployment-plan-pic3.png

crashcourse-platform-deploy-execute-deployment-plan

Key concepts == This microlearning centers around the execution of a Deployment plan. The deployment plan is a series of steps that need to be executed on any TAP environment to make the release defined active inside the eMagiz runtimes.

Execute a Deployment plan == Provided there is a deployment plan, the execution is initialized from the Releases section.

Key takeaways == * The execution of a deployment plan is a smooth process to avoid manual deployments of flows * Be aware of the specific considerations involved * Tune the deployment plan continuously to make it better all the time. == 5.

crashcourse-platform-deploy-execute-deployment-plan-pic1.png

crashcourse-platform-deploy-execute-deployment-plan-pic2.png

crashcourse-platform-deploy-execute-deployment-plan-pic3.png

crashcourse-platform-deploy-execute-deployment-plan-gen3

{{container}} {{container layoutStyle="columns"}}((( In this microlearning, we’ll focus on how to execute a Deployment plan within eMagiz. A Deployment plan is a sequence of steps required to apply updates and make a release active in your TAP environment.

Key concepts == This microlearning centers around the execution of a Deployment plan. The deployment plan is a series of steps that need to be executed on any TAP environment to make the release defined active inside the eMagiz runtimes.

Execute a Deployment plan == Provided there is a deployment plan, the execution is initialized from the Releases section.

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}}

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}}

crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png

Those are used by eMagiz for separate purposes * All business tags are prefixed with Business * Use the deployment plan to tell you which alerts you might need to update based on your Production deployment [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png]] === 3.2 Create or Update alerting === 1.

crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png

{{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.