Search: "deployment plan"

Last modified by Rico Kieboom on 2022/04/11 14:18

Results 1 - 10 of 101 next page » Page 1 2 3 4 5 6 7 8 9 ... 11

eMagiz Runtime Generation 3

Last modified by Erik Bakker on 2024/12/13 11:02
Raw document content
This also means that your deployment plan changes as well. For example, instead of deploying on a flow-by-flow basis, we will package the whole runtime in one image and deploy that to the machine. Therefore new steps have been added to the deployment plan to deploy changes on your machine. For example, the first time you introduce a Generation 3 runtime on a machine, you must add a Deploy Machine step to the deployment plan and remove all actions referencing the runtime you migrated.
[[image:Main.Images.Migrationpath.WebHome@migration-path-migration-path-emagiz-runtime-generation-3--deployment-plan-example.png]] {{info}} When selecting the option for the "big bang" approach of migrating your model, you can use the "Default plan" option to update your Deployment plan {{/info}} {{info}} When opting for the "step-by-step" approach of migrating your model, depending on which part of your model you are already updating, you must manually add a "Deploy machine" step per machine that is migrated to the next-generation architecture.

Deploy a release

Last modified by Erik Bakker on 2024/11/24 09:32
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.

Standard Alerting eMagiz

Last modified by Danniar Firdausy on 2024/11/20 12:48
Attachment name
crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png

V3.2.0

Last modified by Carlijn Kokkeler on 2024/11/18 15:22
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==== We have removed some deprecated components from our runtime image. * TCP support object 'Byte array text length header (de)serializer' * Mikrotik service activator **Removed libraries** * Removed library aopalliance:aopalliance 1.0 * Removed deprecated library com.emagiz.components:emagiz-components-core 12.1.1 * Removed deprecated library com.emagiz.components:emagiz-components-tcp 12.1.1 * Removed deprecated library com.emagiz.components:emagiz-components-tracking 12.1.1 * Removed deprecated library com.emagiz.core:emagiz-util-codec 9.0.1 * Removed duplicate library com.sun.xml.bind:jaxb-core 4.0.4 * Removed duplicate library com.sun.xml.bind:jaxb-impl 4.0.4 * Removed library org.springframework.cloud:spring-cloud-commons 4.1.0 * Removed library org.springframework.cloud:spring-cloud-config-client 4.1.0 * Removed library org.springframework.cloud:spring-cloud-starter 4.1.0 * Removed library org.springframework.cloud:spring-cloud-starter-config 4.1.0 * Removed library org.springframework.security:spring-security-rsa 1.1.1 **Added libraries** * Added library com.emagiz.boot:emagiz-boot-logging 2.1.0 * Added library com.emagiz.components:emagiz-components-bucket4j 12.2.0 **Updated libraries** * Updated library com.emagiz.batch:emagiz-batch-aws-redshift from 5.0.0 to 5.0.1 * Updated library com.emagiz.batch:emagiz-batch-azure-eventhubs from 5.0.0 to 5.0.1 * Updated library com.emagiz.batch:emagiz-batch-core from 5.0.0 to 5.0.1 * Updated library com.emagiz.batch:emagiz-batch-file from 5.0.0 to 5.0.1 * Updated library com.emagiz.batch:emagiz-batch-http from 5.0.0 to 5.0.1 * Updated library com.emagiz.batch:emagiz-batch-jdbc from 5.0.0 to 5.0.1 * Updated library com.emagiz.boot:emagiz-boot-autoconfigure from 2.0.3 to 2.1.0 * Updated library com.emagiz.boot:emagiz-boot-bus from 2.0.3 to 2.1.0 * Updated library com.emagiz.boot:emagiz-boot-control from 2.0.3 to 2.1.0 * Updated library com.emagiz.boot:emagiz-boot-metrics from 2.0.3 to 2.1.0 * Updated library com.emagiz.components:emagiz-components-artemis from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-batch from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-error from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-file from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-ftp from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-http from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-infinispan from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-jdbc from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-jms from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-json from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-kafka from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-mail from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-mapping from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-qpid from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-security from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-sftp from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-smooks from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-staedi from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-staxon from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-ws from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-wssec from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-xml from 12.1.1 to 12.2.0 * Updated library com.emagiz.components:emagiz-components-xslfo from 12.1.1 to 12.2.0 * Updated library com.emagiz.core:emagiz-core-charset from 7.0.0 to 7.1.0 * Updated library com.emagiz.core:emagiz-core-premain from 7.0.0 to 7.1.0 * Updated library com.emagiz.core:emagiz-core-xml from 7.0.0 to 7.1.0 * Updated library com.emagiz.core:emagiz-util-base from 9.0.1 to 10.0.0 * Updated library com.emagiz.core:emagiz-util-xml from 9.0.1 to 10.0.0 * Updated library com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.14.3 to 2.15.3 {{warning}}**Remarks** We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals

233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
Raw document content
//__Failover__// Several improvements for our failover functionality have been done: * We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.

233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
Rendered document content
Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
Raw document content
. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment.

Start/Stop Flows

Last modified by Danniar Firdausy on 2024/09/30 10:15
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.

Failover - Deploy Possibilities

Last modified by Erik Bakker on 2024/09/27 14:07
Raw document content
When you have made your decision, and assuming that your machines are already deployed and running, then you can move to the other page discussed in the next section. === 3.3 Deployment Plan === If this is the first time that you configure your failover setup, then the next step in Deploy is to check your Deployment Plan.
[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-balance-failover.png]] To make sure that this functionality works correctly, then this step should be placed at the end of your deployment plan (i.e., after the deployment of all runtimes).
[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-deployment-plan.png]] === 3.4 Deploy Release === Once you have configured your Deployment Plan, then it is time to create a new release for your updated flows in the Deploy>Release page.

230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:36
Rendered document content
Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more here. Minor changes Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
Raw document content
Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].

230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:35
Raw document content
Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]. == **Bug Fixes** == //__Queues with illegal characters__// Existing queues with illegal characters will not generate errors anymore.
next page » Page 1 2 3 4 5 6 7 8 9 ... 11
RSS feed for search on ["deployment plan"]