Search: "deploy architecture"

In other words, the cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting for instance) are available for your environment.

You can determine both with the help of the Upgrade functionality within Deploy Architecture. When you navigate to Deploy and open the Architecture you can enter "Start Editing" mode.

To activate this functionality navigate to the Upgrade screen via the context menu in Deploy -> Architecture and enable the option Automatic Upgrade.

Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543) Deploy - Architecture: We improved the auto-healing feature of AWS machines.

. * Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. * Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543) * Deploy - Architecture: We improved the auto-healing feature of AWS machines.

Minor changes Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store. Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud.

====Minor changes==== * Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store. * Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud.

. (#1284) Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053) Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282) Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293) Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.

. (#1284) * Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053) * Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282) * Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293) * Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05. * Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)

Important things to remember are: * Configuration on eMagiz Cloud level is done via Deploy -> Architecture * Certificate is generated via the support department (with or without CSR) * No actions are needed on flow level, only on Cloud level * All you need for the configuration is the common name of the certificate Now that we have introduced the topic let us see how to configure the certificate within Deploy -> Architecture.

Key takeaways == * Set up certificates within eMagiz Cloud under Deploy -> Architecture, and ensure certificates are properly linked to routes to control access securely. * As the security best practices, for REST services, use OAuth2.0; for both SOAP and REST, combine API-Key with certificates for robust security. * Use the "Apply to environment" button carefully to apply changes across configurations, avoiding unintended impacts. * Restarting runtimes will reset all flows, including infrastructure, to their initial state, so plan and execute with precision. == 5.

//__Removed specific dependencies between Deploy Architecture and Releases__// In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.

Deploy - Releases: Copy to clipboard buttons have been added to various pages. Deploy - Architecture: For our current runtime architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.

. * Deploy - Releases: Copy to clipboard buttons have been added to various pages. * Deploy - Architecture: For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.

With this fix we ensured the widget will always load correctly. (#362) Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.

With this fix we ensured the widget will always load correctly. (#362) * Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) * Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. * Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.

. (#151) Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group. Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".

. (#151) * Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group. * Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". * Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324) * Catalog: For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.

This action can be found in Deploy Architecture, when right clicking on the white canvas. * We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture.