Search: "deploy architecture"

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

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.

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

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.

The first part of the equation can be found under Deploy -> Architecture. The second part can be found under Deploy -> Properties by looking for the {technicalnameproject}.amqp01.host.

{{info}}Note that when running your web service in the eMagiz cloud, the first part (the host part) will change depending on your configuration in Deploy Architecture and the cloud slot on which you are running.

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.

. (#845) Create - Framework: The framework used in the flow designer has been updated, improving performance. Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.

. (#845) * Create - Framework: The framework used in the flow designer has been updated, improving performance. * Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing. * Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009) * Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993) * Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase. * Deploy - Release properties: The description of a property can be changed by editing the property. (#1064) * Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines. * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well. * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy. * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024) * Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications. * Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069) * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070) * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) * Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action. * Administration - My account: When changing a password, it is compared to a list of known database breaches for security.

. (#687) Bug fixes Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.

. (#687) ====Bug fixes==== * Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) * Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. * Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087) * Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.

//__Deploy architecture changes__// The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed.