Search: "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)

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.

To execute this action please navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called restart runtime.

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