Search: "deployment plan"

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.

For this fix, a new runtime image has been released. Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)

For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. * Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) * Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) * Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) * Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)

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.

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.

More information can be found here. Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment.

More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. * Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment.

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

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.

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

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.

Message Redelivery - admin logs improved to better analyze issues when they occur Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed Bug fixes Deploy - Deployment plan. Performance of page to deploy a release increased significantly Store - Import resources was incorrectly done in specific cases, which is now fixed Store - Target namespace will be imported when importing an XML Message Definition Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.

. * Message Redelivery - admin logs improved to better analyze issues when they occur * Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality * Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed ====Bug fixes==== * Deploy - Deployment plan. Performance of page to deploy a release increased significantly * Store - Import resources was incorrectly done in specific cases, which is now fixed * Store - Target namespace will be imported when importing an XML Message Definition * Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. * Store - Importing items from the store sometimes resulted in invalid JMS connection factories.