Search: "deploy architecture"

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.

This can be done by moving to Deploy -> Architecture and pressing 'Reset H2'. Do remember that resetting the H2 database or removing and readding it will result in a loss of all the data on the database. == 5.

Key concepts == * This migration path allows you to maintain your hosted SOAP web service in the 3rd generation runtime * Consequences of this migration are: ** Your all-entry will be split up into seperate entries ** Your WSDL will be generated based on your system message ** The system message will be altered based on your configuration in Design by adding a new root entity named Send{givenname}Request ** This alteration of your system message will not impact your transformation towards your data model ** 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-soap-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 is a new piece of functionality that allows you define the port on which the SOAP 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 SOAP web service in the 3rd generation runtime * Consequences of this migration are: ** Your all-entry will be split up into seperate entries ** Your WSDL will be generated based on your system message ** The system message will be altered based on your configuration in Design by adding a new root entity named Send{givenname}Request ** This alteration of your system message will not impact your transformation towards your data model ** HTTP Settings now need to be configured under Deploy -> Architecture == 5. Key takeaways == * [[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 SOAP Web Service (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

{{info}}After you create a new version of your flow, before you create and deploy a new release, you also need to configure a new route in Deploy>Architecture of your desired environment for the clients (publishers and subscribers) of this MQTT broker to connect.

This holds for releases that are deployed and promoted to a next environment. Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'.

This holds for releases that are deployed and promoted to a next environment. * Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'.

. * The first is to execute a "restart runtime" action via Deploy Architecture or the on-premise server. * Secondly, you could deploy a new version of the infra (via the Releases functionality).

In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise. //__Empty runtime feedback when deploying a release (or setting the release as active)__// To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.

Create - Resources: You can change the file of a resource used in a flow without encountering errors such as 'Failed to commit'. Deploy - Architecture: Improved functionality of waking up a cloud slot so that no strange errors occur.

. * Create - Resources: You can change the file of a resource used in a flow without encountering errors such as 'Failed to commit'. * Deploy - Architecture: Improved functionality of waking up a cloud slot so that no strange errors occur. * Manage - Error messages: XML Validation errors are available for inspection when opening a certain error message. (#330)

Once that is done, 'Apply to environment' should be pressed in Deploy -> Architecture. As a result, the Deploy agent option will be available on your new machine in Deploy Architecture.

To apply the changes from Design Architecture to Deploy Architecture, you need to press the "Apply to Environment" button just as you would now if you add or change a runtime in the current architecture.

Below you can find more information on these mechanisms. ==== 4.8.1 Verification in Deploy Architecture ==== The first check can be done in Deploy Architecture itself.