Search: "deploy architecture"

The unexpected maintenance resulted in a user pressing the Apply to Environment button in Deploy -> Architecture in eMagiz. As a result, the complete machine was stopped, recreated, and started again. == 2.

The reset runtime action in the Deploy Architecture cleans up the data folder (excluding the H2 folder) but doesn't cleanup the libraries.

Situation == Pressing the 'Apply to Environment' button in Deploy Architecture led to an 'Update rollback complete' state. == 2. Problem == The problem in this case was that two routes were pointing at the same port configured in Deploy Architecture. == 3. Analysis == === 3.1 Reproduction === N/A === 3.2 Analysis === We started off by checking the CloudFormation in AWS.

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?

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?

. * 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).

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.

. ** For example, when you command the container to stop via Deploy Architecture or when eMagiz stops the container, e.g.