Search: "deployment plan"

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==== * Added SpEL functions for: ** Encoding & decoding Base64, Hex and hmac. ** Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond). ** Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser). * Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily.

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.

//__Refresh behavior within the deployment plan is fixed__// This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Deployment is done through the deployment plan 4. On premise runtime deployment through the eMagiz portal (after installing the control agent) eliminating the need to locally install runtimes ====Runtime specific updates==== 1.

. * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms === **Improvements** === * Performance Deployment plan When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU.

//__Random stuck in deployment plan execution__// We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

. ** HTTP Statistics - Overview *** Problematic requests *** All requests == **Feedback Items** == //__Failover deployment plan__// The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow. //__Stop deployment plan when a property is missing__// Currently, the execution of your deployment plan continues when eMagiz notices a missing property.

This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan. //__Cap stack trace of error messages and log entries__// To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png

Those are used by eMagiz for separate purposes * All business tags are prefixed with Business * Use the deployment plan to tell you which alerts you might need to update based on your Production deployment [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png]] === 3.2 Create or Update alerting === 1.

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.