Search: "deployment plan"

Furthermore, the components of the API Gateway are the following: ** Gateway infra ** All entry (later replaced with single entries per operation) ** Exit gate (contains a connection to backend provider) These components can be made part of the Release and Deployment plans. The Deploy Architecture will contain the Cloud architecture to be deployed and can be applied with the Design Architecture.

. * To keep your project manageable, it's recommended to include a manual step in your ACCP or PROD deployment plan to clean up unused resources during every release cycle. == 5.

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.

[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--track-update-status.png]] === 3.3 Actualize changes - On-premises === 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.

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"]] ** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]] *** [[Apply to Environment (Explanation)>>Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.intermediate-emagiz-cloud-management-apply-to-environment||target="blank"]] * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] *** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] *** [[Configure needed runtime memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-configure-needed-memory.WebHome||target="blank"]] * [[Configure needed memory (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

{{/info}} {{info}}In the 3rd generation runtime, you need to create a new release and deploy this with the help of your deployment plan to an environment. After you have deployed the flow, you can test the settings via the Swagger UI, which you can access via the Runtime Dashboard -> View Swagger UI.

Prerequisites == * Basic knowledge of the eMagiz platform * Completed all microlearnings from Deploy till this specific microlearning * Have an environment where you can add releases and that is operational to try out the deployment plan == 2. Key concepts == eMagiz provides the capability to manage your deployments effectively so that all your updated flow components as created in the previous ILM phases of eMagiz.

Select the option set as active to make this the release that the deployment plan will use to deploy the updated, new, and changed flows.

Key takeaways == * The Release defines what is to be deployed on a specific environment, as compared to the Deployment plan that determines what is to be deployed * Use proper naming and clean your old releases regularly.

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

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.