Search: "deploy architecture"

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

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)

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.

You can also give more information in a description. (#1326) Deploy - Architecture: For clarity purposes, a confirmation pop-up will be shown when deleting routes. (#1380) Manage - Explore: The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.

You can also give more information in a description. (#1326) * Deploy - Architecture: For clarity purposes, a confirmation pop-up will be shown when deleting routes. (#1380) * Manage - Explore: The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. * Deploy - Releases: A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.

//__Architecture - Retention Bytes__// Deploy architecture for displaying the retention bytes is aligned with the Design architecture.

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.

{{/warning}} === 3.3 Deploy Machine === In Architecture, you can deploy the machine for every separate machine defined in your Deploy Architecture. You also have the option to start, stop, or restart machines that run in the AWS Cloud

* Deploy Machine * Start Machine (only AWS) * Stop Machine (only AWS) * Restart Machine (only AWS) [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan--deploy-machine-options.png]] When you execute actions via Deploy Architecture, you can manually disable the triggers by going to Manage -> Alerting -> Triggers -> Notification Settings and pressing "Pause Notifications."

* The key aspects are: ** The description is your way of communicating the history of the flow ** Using vague descriptions (or placing a dot as description) hurts the auditability ** For all things versioned in eMagiz it is crucial that you supply the correct description ** eMagiz provides audit trails on Architectural overviews (Design and Deploy architecture) including a description ** eMagiz provides audit trails on message definitions and transformations including a description === 3.1 Versioning by users === Three key parts within eMagiz require versioning by a user.

The main parts on which eMagiz keeps an audit trail are: * Architectural overviews (Design and Deploy Architecture) * Message definitions and transformations In all cases, you will find a History button on the page in question that will guide you to the history (audit trail) of what has changed by whom at which point in time. == 4.

In turn the user will be notified which flows could not be updated automatically and should be checked manually. (#701) Deploy - Architecture: For runtimes on the new monitoring stack that run on-premises, volumes can be registered in order to persist data and/or to access the hosts file system.

In turn the user will be notified which flows could not be updated automatically and should be checked manually. (#701) * Deploy - Architecture: For runtimes on the new monitoring stack that run on-premises, volumes can be registered in order to persist data and/or to access the hosts file system. * Store: The download counter will only be increased if the importing party is a normal user and not a system admin.