Search: "deploy architecture"

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

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)

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.

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.

Key concepts == * This migration path allows you to maintain your hosted REST web service in the 3rd generation runtime * Consequences of this migration are: ** Your all-entry will be split up into separate entries ** HTTP Settings now need to be configured under Deploy -> Architecture == 3. Technical Migration Path == As part of the "Transfer Settings from Design" step in the general migration path on migrating to the 3rd generation runtime, you will see an additional option displayed below this option called "Split Combined Entries."

{{/warning}} [[image:Main.Images.Migrationpath.WebHome@migration-path-migration-path-emagiz-runtime-generation-3--release-overview-splitted-entry-rest-web-service.png]] === 3.5 Check the Runtime Settings === One last step of the migration is to check the runtime settings of the runtime you are migrating under Deploy -> Architecture. This new functionality allows you to define the port on which the REST web service needs to be running (and optionally SSL settings when running it on-premise).

Key takeaways == * This migration path allows you to maintain your hosted REST web service in the 3rd generation runtime * Consequences of this migration are: ** Your all-entry will be split up into separate entries ** HTTP Settings now need to be configured under Deploy -> Architecture == 5. Suggested Additional Readings == * [[Migration Paths (Navigation)>>doc:Main.eMagiz Support.Migration Paths.WebHome||target="blank"]] ** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3||target="blank"]] * [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] ** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] *** [[Runtime Settings (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-runtime-settings.WebHome||target="blank"]] * [[Host Rest Web Service (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?