Search: "deployment plan"
Last modified by Rico Kieboom on 2022/04/11 14:18
Refine your search
Select a category and activate filters on the current results
Last modification date
Setting up a deployment plan
Located in
- Title
Setting up a deployment plan
- Attachment name
crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png
…crashcourse-platform-deploy-setup-deployment-plan-pic1.png
- Page
crashcourse-platform-deploy-setup-deployment-plan-gen3
- Raw document content
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
Located in
- Title
Setting up a deployment plan
- Attachment name
crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png
…crashcourse-platform-deploy-setup-deployment-plan-pic1.png
- Location
crashcourse-platform-deploy-setup-deployment-plan
- Raw document content
{{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.
Define deployment plan & create release
Located in
- Title
Define deployment plan & create release
- Location
crashcourse-platform-exercise-define-deployment-plan-and-create-release
- Raw document content
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
Located in
- Title
Define deployment plan & create release
- Location
crashcourse-platform-exercise-define-deployment-plan-and-create-release
- Raw document content
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}}
Deploy a release
Located in
- Attachment name
crashcourse-platform-deploy-execute-deployment-plan-pic1.png
…crashcourse-platform-deploy-execute-deployment-plan-pic2.png
…crashcourse-platform-deploy-execute-deployment-plan-pic3.png
- Location
crashcourse-platform-deploy-execute-deployment-plan
- Raw document content
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.
Deploy a release
Located in
- Attachment name
crashcourse-platform-deploy-execute-deployment-plan-pic1.png
…crashcourse-platform-deploy-execute-deployment-plan-pic2.png
…crashcourse-platform-deploy-execute-deployment-plan-pic3.png
- Location
crashcourse-platform-deploy-execute-deployment-plan-gen3
- Raw document content
{{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.
Runtime Settings
Located in
- Raw document content
{{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?
Grouping - Deploy Possibilities
Located in
- Raw document content
This microlearning will focus on configuring the deployment plan to control various inbound components in a typical group and failover configuration.
…Key concepts == This microlearning describes how to configure (parts of) your deployment plan to set up the grouping and, if needed, the failover functionality.
…The group name needs to match **exactly** to make it work. * You can control group and failover steps from the deployment plan. * Container inbounds can have a different failover status. == 5.
Creating a new Release
Located in
- Raw document content
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.
Actualize properties
Located in
- Raw document content
Key concepts == {{warning}}Regardless of what your change entails you always need to execute the deployment plan to deploy and actualize the changes on your environment.
…Once you have created your new release, you can use the deployment plan steps to activate the changes on both flow and property levels. More information on how to do this can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4.
next page »
Page
1
2
3
4
RSS feed for search on ["deployment plan"]