Search: "deploy architecture"

{{/info}} //__Deploy - Architecture__// Within deploy architecture, we fixed the following bugs. * Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. * You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model.

. (#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.

{{/info}} == **Minor Changes** == //__Changing data retention__// * When DSH retention time is changed on the company level, deleting the topic by excluding it in Design > Architecture and applying the change in Deploy > Architecture and including it again in Design > Architecture and applying the change in Deploy > Architecture results in the retention time being updated in DSH. ** Note that this action will delete the topic and therefore will result in **data loss** //__Importing old OpenAPI Version deprecated__// Importing an Open Specification V2 is deprecated and no longer supported at eMagiz.

. (#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.

//__Architecture - Routes__// We have improved the help texts for the "Routes" configuration in Deploy - Architecture. == **Bug Fixes** == //__Deploy - User Management__~*// For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.

Setting the release means creating a new Docker image. * Deploy Architecture ** You can see the running status of a Docker image at every runtime.

The following will change in this new configuration. *** All-entry will be split into separate entries *** WSDL will be automatically generated based on your system messages *** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture *** Configuration of endpoints is streamlined better between cloud-hosted endpoints and on-premise endpoints * Handling local file communication ** As our third-generation runtime uses Docker technology, your containers are, by default, closed off from their host.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.

This allows you to transfer them from Design Architecture to Deploy Architecture to be utilized in future deployments. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] To execute this action please navigate to Deploy -> Architecture. 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 "Reset H2".