Search: "deploy architecture"

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

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.

Deploy - Architecture: Improved feedback when trying to deploy Gen3 runtimes to offline machines.

You only need to press once to select or change a flow version. (#594) Deploy - Architecture: We fixed a bug where upgrading to the latest Gen3 cloud release caused JMS connectivity issues. Deploy - Architecture: Improved Route generation so the streaming container will no longer be added to the existing gateway routes.

. (#599) * Deploy - Releases: The release attribute to prevent deletion of the release can be edited if the release is locked. * Deploy - Architecture: Name change of the Status tab on the runtime popup. * Deploy - Architecture: Improved feedback when trying to deploy Gen3 runtimes to offline machines. * Deploy - Event Streaming: The event streaming tab in the Deploy phase has been removed. (#542) * Deploy - User management: Access key, access certificate, and Keystore filenames are generated with the corresponding deploy user’s name. (#426) * Manage - Dashboard: A new button “Refresh“ is added to the right panel of the Dashboard.

You only need to press once to select or change a flow version. (#594) * Deploy - Architecture: We fixed a bug where upgrading to the latest Gen3 cloud release caused JMS connectivity issues. * Deploy - Architecture: Improved Route generation so the streaming container will no longer be added to the existing gateway routes.

. (#1439) Create - Transformation: Source filters will now display the attribute filter statement correctly. (#1353) Deploy - Architecture: 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. (#1104) Deploy - Containers: The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. (#1464) Deploy - Releases: We updated the user rights in a model such that in order to deploy a release in Deploy, you should have both edit rights in Deploy and Manage. (#1495) Manage - Code Mappings: When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated.

. (#1439) * Create - Transformation: Source filters will now display the attribute filter statement correctly. (#1353) * Deploy - Architecture: 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. (#1104) * Deploy - Containers: The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. (#1464) * Deploy - Releases: We updated the user rights in a model such that in order to deploy a release in Deploy, you should have both edit rights in Deploy and Manage. (#1495) * Manage - Code Mappings: When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated.

Key concepts == With cloud template, we mean: A Cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting, for instance) are available for your environment.

All changes can be handled with a single push of a button, but it may become harder to isolate the root cause when an issue occurs. So keep your Deploy Architecture as current as possible.{{/info}} * Duration of the upgrade ** A Cloud template upgrade will take between 5 and 15 minutes, depending on the size of the slot in terms of machines.

Regardless of the type of environment (Test, Acceptance, or Production) * Double lane Cloud template upgrades are non-service affecting. * Keep your Deploy architecture current - less risk of the impact of Cloud template upgrade issues. == 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.