Search: "deploy architecture"

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.

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.

//__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.

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.

Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. == **Deploy Architecture - Apply To Environment improvements ** == As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture.

The Cloud architecture can be designed in the Design - Architecture section and effectuated via the Deploy - Architecture section. Please check out the microlearnings mentioned below for more information on how to configure these or make the right architecture decisions. **Design Architecture** [[image:Main.Images.Fundamental.WebHome@fundamental_architecture-2.png]] **Deploy Architecture** [[image:Main.Images.Fundamental.WebHome@fundamental_architecture-3.png]] == 4.

New features Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime.

====New features==== * Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime.

For this, a new runtime image is available. Deploy - Architecture: It is now possible to search in the Start/Stop flows overview. (#1311) Manage - Alerting: The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.

For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V312.WebHome||target="blank"]] is available. * Deploy - Architecture: It is now possible to search in the Start/Stop flows overview. (#1311) * Manage - Alerting: The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.