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
196 - The Last Post
Located in
- Rendered document content
Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) Manage/Event streaming statistics.
- Raw document content
. * Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) * Manage/Event streaming statistics.
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?
229 - XPath Alignment
Located in
- Raw document content
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.
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.
V2.1.0
Located in
- Raw document content
For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====New features==== New components to support a failover setup: * Clustered lock registry: obtain a lock that can be shared over different containers * Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock * New & extended operations for controlling integration components ** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time ** New: List all roles and whether they support leadership ** Extended: List flow components now also shows whether a component is configured to be in a role Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”. )))((({{toc/}}))){{/container}} {{/container}}
Runtime Overview
Located in
- Raw document content
Prerequisites == * Basic knowledge of the eMagiz platform * Understanding Releases and be able to run a Deployment plan effectively * Understanding Containers and how flows are managed across them == 2.
…If you want to know more about when a new image is created for a container, please read this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ** Note that this can be **red** in case the latest changes are not deployed on the certain runtime. For example if your deployment plan stops half way and there were changes which need to be deployed in the second part, you could end up in this situation. * State ** Throughout the lifetime of a container it can have one of the 6 states mentioned below.
209 - Max Verstappen
Located in
- Raw document content
** 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.
206 - Situational Deployment
Located in
- Raw document content
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.