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
Result type
- 102Document
- 12Attachment
Last modification date
- Sort by:
- Relevance
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.
220 - Patch Parade
Located in
- Rendered document content
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)
- Raw document content
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)
Start/Stop Flows
Located in
- Raw document content
The preferred option when executing changes on the current generation runtime is via the deployment plan, which keeps all parts of your model in sync.
V3.0.6
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==== * Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. )))((({{toc/}}))){{/container}} {{/container}}
Incorrect property configuration
Located in
- Raw document content
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?
200 - Uncharted Territories
Located in
- Raw document content
. == **Next generation improvements and bug fixes** == //__Enhanced right-hand view within Deployment Plan context__// When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly.
…{{/info}} //__Improved timeout settings when deploying__// To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
211 - Log Luminary
Located in
- Raw document content
//__Deployment execution error message__// In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
…[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] //__Runtime restart or redeploy overview__// Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
V3.1.3
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"]]. ====Minor changes==== * It provides support for providing preferred authentication methods for (username/password-based) authentication for SFTP Session Factories. )))((({{toc/}}))){{/container}} {{/container}}
V2.1.1
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==== * 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}}