Search: "deployment plan"

Suggested Additional Readings == * [[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"]] *** [[Properties (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] *** [[Execute Deployment Plan (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] * [[RCA Knowledge Base (Menu)>>doc:Main.eMagiz Support.RCA Knowledge Base.WebHome||target="blank"]] ** [[Configuration Issues (Navigation)>>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.WebHome||target="blank"]] *** [[Incorrect flow configuration (Explanation)>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.rca-knowledgebase-incorrect-flow-configuration.WebHome||target="blank"]] *** [[Design runtime changes after Create (Explanation)>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-runtime-issues.rca-knowledgebase-design-runtime-changes-of-created-runtimes.WebHome||target="blank"]] * [[Property Configuration (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

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"]]. ====Bug Fixes==== * Error messages with a lengthy message history will also be displayed. * Error messages with a stack trace larger than 32kb will also be displayed. )))((({{toc/}}))){{/container}} {{/container}}

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==== * When using a failover manager, the runtime will now indicate its leadership status taking into account whether it is connected to other containers. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====Minor changes==== * It provides support for providing preferred authentication methods for (username/password-based) authentication for SFTP Session Factories. )))((({{toc/}}))){{/container}} {{/container}}

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==== * Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. )))((({{toc/}}))){{/container}} {{/container}}

If the flow version is as expected, we can check the [[properties>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] to see whether we see any changes.

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.

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

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.

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