Search: "deploy architecture"

This effectively disables backwards-compatible version negotiation. Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.

This action can be found in Deploy Architecture, when right clicking on the white canvas. We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.

This effectively disables backwards-compatible version negotiation. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas. ** We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture.

New features Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141) Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.

Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup.

====New features==== * Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141) * Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.

====Bug fixes==== * Create - Flow Designer: The help text of the Group attribute has been improved. * Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) * Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup.

. (#1179) Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false. Deploy - Architecture: Changes can now be deployed on SSL level without creating a new version of a flow in Create. (#1286) Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325) Manage - Explore: We fixed an issue where navigating to the “Explore” tab in “Manage” phase would sometimes redirect users to the homepage.(#1237) Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278) Bug fixes Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852) Create - Flow designer: The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. (#1303) Create - Flow designer: We fixed the incorrect generation of gateway infra flow for models using the OAuth 2.0 security scheme in Spring 6. Deploy - Architecture: Machines deleted in Design are excluded from the memory health check. (#1282) Deploy - Architecture: Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers.

. (#1179) * Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false. * Deploy - Architecture: Changes can now be deployed on SSL level without creating a new version of a flow in Create. (#1286) * Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325) * Manage - Explore: We fixed an issue where navigating to the “Explore” tab in “Manage” phase would sometimes redirect users to the homepage.(#1237) * Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278) ====Bug fixes==== * Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852) * Create - Flow designer: The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. (#1303) * Create - Flow designer: We fixed the incorrect generation of gateway infra flow for models using the OAuth 2.0 security scheme in Spring 6. * Deploy - Architecture: Machines deleted in Design are excluded from the memory health check. (#1282) * Deploy - Architecture: Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers.

Minor Changes Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks. Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture." Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401) General - eMagiz Connector: The new version is available in the Mendix Marketplace.

====Minor Changes==== * Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks. * Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture." * Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401) * General - eMagiz Connector: The new version is available in the Mendix Marketplace. ** The "eMagiz Connector" Mendix module has been updated in preparation for event streaming support.

Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in two steps to use the new R9 release of the cloud template.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in two steps to use the new R9 release of the cloud template.

**Update Steps** * Use the intermediate template (non-service affecting) (duration: 10 minutes) ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot. ** The network drive containing the Artemis queue store and your Elastic IPs will remain. * Use the final template (service affecting) (duration: 10 minutes) ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. ** The runtimes on the machines will be restored using the active release in the eMagiz portal. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

Minor Changes Manage - Monitoring: The memory graphs of runtimes running on Gen3 have improved. Deploy - Architecture: Under certain circumstances, the HTTP route for the API gateway was generated twice, causing an invalid cloud configuration. Bug fixes Deploy - Properties: Specific properties could cause the property history page to break and show error popups. Deploy: Architecture: Improved the mechanism for updating the last known state of machines running Gen3 runtimes.

. ==== Minor Changes ==== * Manage - Monitoring: The memory graphs of runtimes running on Gen3 have improved. * Deploy - Architecture: Under certain circumstances, the HTTP route for the API gateway was generated twice, causing an invalid cloud configuration. ==== Bug fixes ==== * Deploy - Properties: Specific properties could cause the property history page to break and show error popups. * Deploy: Architecture: Improved the mechanism for updating the last known state of machines running Gen3 runtimes.

Minor changes Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected. Deploy - Architecture: The container calculations are improved.

Create - 3rd Generation runtime migration: Your containers will be validated for 3rd Generation runtimes first before you approve the migration. Deploy - Architecture: Users with edit rights in deploy can edit certificates.

====Minor changes==== * Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected. * Deploy - Architecture: The container calculations are improved.

The other types of containers display the amount of intergrations deployed. * Create - 3rd Generation runtime migration: Your containers will be validated for 3rd Generation runtimes first before you approve the migration. * Deploy - Architecture: Users with edit rights in deploy can edit certificates. * Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.

Minor changes Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. Deploy - Architecture: The container calculations are improved.

The other types of containers display the amount of integrations deployed. (#544) (#869) Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052) Bug fixes Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.

====Minor changes==== * Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. * Deploy - Architecture: The container calculations are improved.

The other types of containers display the amount of integrations deployed. (#544) (#869) * Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052) ====Bug fixes==== * Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) * Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. * General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. * Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.

As you all are working in the same integration data model eMagiz will actualize **all** changes when your colleague presses Apply to Environment in Deploy Architecture. So be aware of when you change things and when you do ensure to communicate with all stakeholders related to the project how you plan to actualize those changes. === 3.4 Design vs Deploy Architecture === In the previous segment, we talked about the impact of changing things in Design Architecture. In this segment, we will look at some scenarios in which the Design Architecture view can differ from the Deploy Architecture view. There are three main reasons why both of them differ: * This is the first time you open Deploy Architecture * This means you need to spin up your cloud infrastructure for the first time * There is no flow related to the runtime embedded in the release * Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release * The runtime is excluded in Design Architecture * With this functionality, you explicitly mention that a certain runtime should not be deployed Knowing this should make you better equipped to handle 'unexpected' situations you occur while implementing your data model with the help of the eMagiz platform.

Coordinate with stakeholders to manage changes in Design Architecture and avoid conflicts. * Understand why Design and Deploy Architectures may differ due to setup, dependencies, and exclusions. == 5.

It consists of a revert of our announced functionality regarding Windows memory limits. Reverts Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.

====Reverts==== * Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.