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"]]. ====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

Furthermore, the components of the API Gateway are the following: ** Gateway infra ** All entry (later replaced with single entries per operation) ** Exit gate (contains a connection to backend provider) These components can be made part of the Release and Deployment plans. The Deploy Architecture will contain the Cloud architecture to be deployed and can be applied with the Design Architecture.

{{/info}} {{info}}In the 3rd generation runtime, you need to create a new release and deploy this with the help of your deployment plan to an environment. After you have deployed the flow, you can test the settings via the Swagger UI, which you can access via the Runtime Dashboard -> View Swagger UI.

Key takeaways == Flow tests are a powerful way in which flows components can be tested without the specific need to deploy them on the eMagiz runtimes using releases and deployment plans. Individual behavior can be tested and verified, without the need to run expensive debug components inside the actual flow.

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.

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.

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan-gen3

The release is active in that all changes made to it compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a basic Deployment plan.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan-gen3.png]] Running a deployment plan means machines are stopped, and new images are deployed. eMagiz does this by comparing your currently running release and the recent release you have activated.

{{info}} At any given moment when you are satisfied with your configuration, you can press "Save" to store your changes for the runtime settings {{/info}} === 3.3 Effectuate changes on architecture === To effectuate the changes made to your deployed architecture, you should create a new release and deploy this via the deployment plan. In case you need more information on the creation of releases or deploying release you can check that information [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] and [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4. Key takeaways == * On the runtime level in Deploy -> Architecture, you have a context menu item called "Runtime Settings." * In this context menu item, you can configure the HTTP Settings and whether the control bus is enabled. * HTTP Settings are needed when hosting a SOAP or REST web service. ** When enabling, the port needs to be filled in. ** Optionally, you can configure one-way or two-way SSL for an on-premise endpoint. * By disabling the control bus, you will lose (parts of) the functionality that allows you to view or halt data. ** Queue browser. ** Message redelivery. ** Start/Stop flow components. * Changes must be deployed by creating a new release and deploying it via a deployment plan. == 5. Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: * [[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"]] *** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] *** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Securing Data Traffic (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.WebHome||target="blank"]] *** [[Securing a hosted web service with certificates in the eMagiz Cloud (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.intermediate-securing-your-data-traffic-securing-a-hosted-webservice-with-certificates-in-the-emagiz-cloud||target="blank"]] *** [[Creating a JKS (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Securing Data Traffic.intermediate-securing-your-data-traffic-creating-a-jks||target="blank"]] * [[Runtime Settings (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

[[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--track-update-status.png]] === 3.3 Actualize changes - On-premises === To effectuate the changes made to your deployed architecture, you should create a new release and deploy this via the deployment plan. In case you need more information on the creation of releases or deploying release you can check that information [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] and [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4.

Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: * [[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"]] *** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] *** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]] *** [[Apply to Environment (Explanation)>>Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.intermediate-emagiz-cloud-management-apply-to-environment||target="blank"]] * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] *** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] *** [[Configure needed runtime memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-configure-needed-memory.WebHome||target="blank"]] * [[Configure needed memory (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

. * To keep your project manageable, it's recommended to include a manual step in your ACCP or PROD deployment plan to clean up unused resources during every release cycle. == 5.