Search: "deploy architecture"

As you all are working in the same integration data model eMagiz will actualize **all** changes when your colleague presses Apply to Environment in Deploy Architecture. So be aware of when you change things and when you do ensure to communicate with all stakeholders related to the project how you plan to actualize those changes. === 3.4 Design vs Deploy Architecture === In the previous segment, we talked about the impact of changing things in Design Architecture. In this segment, we will look at some scenarios in which the Design Architecture view can differ from the Deploy Architecture view. There are three main reasons why both of them differ: * This is the first time you open Deploy Architecture * This means you need to spin up your cloud infrastructure for the first time * There is no flow related to the runtime embedded in the release * Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release * The runtime is excluded in Design Architecture * With this functionality, you explicitly mention that a certain runtime should not be deployed Knowing this should make you better equipped to handle 'unexpected' situations you occur while implementing your data model with the help of the eMagiz platform.

Coordinate with stakeholders to manage changes in Design Architecture and avoid conflicts. * Understand why Design and Deploy Architectures may differ due to setup, dependencies, and exclusions. == 5.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.