Search: "deploy architecture"

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.

. (#1544) XML to EDI transformer EDI to XML transformer XML to UN/EDIFACT transformer UN/EDIFACT to XML transformer 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.

Bug fixes Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456) Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559) Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532) Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523) Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511) Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.

. (#1544) ** XML to EDI transformer ** EDI to XML transformer ** XML to UN/EDIFACT transformer ** UN/EDIFACT to XML transformer * 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. * Manage - Statistics: We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards. ====Bug fixes==== * Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456) * Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559) * Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532) * Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523) * Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511) * Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.

. (#857) Design - Message Mapping: Users can now refresh their Design message mappings. (#848) Deploy - Architecture (Routes): Various help texts have been updated on this pop-up to better clarify what these fields are used for. (#1536) 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. Prevent auto-fill on specific fields by renaming labels Applied styling to hide the Keeper button in input fields where undesired. Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646) Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful.

. (#857) * Design - Message Mapping: Users can now refresh their Design message mappings. (#848) * Deploy - Architecture (Routes): Various help texts have been updated on this pop-up to better clarify what these fields are used for. (#1536) ==== 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. ** Prevent auto-fill on specific fields by renaming labels ** Applied styling to hide the Keeper button in input fields where undesired. * Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646) * Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful.

The properties' history is on the Deploy phase's History page. Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966) Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.

Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913) Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973) Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero." Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.

The properties' history is on the Deploy phase's History page. * Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966) * Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.

The speed of creating the dialog to enter the component’s name is also improved. * Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913) * Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973) * Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero." * Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text. * Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839) * Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).

. (#983) Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979) Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown.

These changes can be applied to the environment or reverted. (#828) Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.

. (#983) * Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979) * Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown.

These changes can be applied to the environment or reverted. (#828) ** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release. ** Changes with a direct effect will not be listed (for example, restarting a machine).

{{container}}{{container layoutStyle="columns"}}((( With this exercise, we learn how to use the "apply to environment" functionality in Deploy -> Architecture. This functionality is a key component in sending changes to our eMagiz cloud to actualize these changes.

To complete this exercise you need to execute the following steps: * Navigate to Deploy -> Architecture * Enter "Start Editing" mode and open the context menu (by clicking on the white area of the canvas) * Select the certificate option and fill in the following things: ** CN Name ** Client Name * Save your changes on certificate level * Open the context menu again and select the route option. * Fill in the following things: ** DNS Left most label ** Port ** Runtime(s) ** Certificate to use * Save your changes == 3.

. (#643) Create - Transformation: For new transformers the default output data type is set to the destination attribute data type. Deploy - Architecture Planned cloud upgrades can be executed manually before the plan date.

This does not happen anymore and long messages can be written with no further inconvenience. (#635) Create - Message type: The message type’s display will be updated when you change the its display name in Capture phase or Design phase. (#656) Create - System Message: Improved creation of enumeration for xml definition attributes so that the enumeration is automatically coupled to the attribute. (#200) Deploy - Architecture: For new machines, size changes in design architecture were not applied to deploy architecture, until after the first deployment. (#521) Deploy - Manage: Leaving the API statistics page does not result in error messages. (#541) Design - Message Mapping: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) Create - Transformation: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) Design - Integrations: For the data pipeline integration, errors of message mapping will be ignored. (#592) Remarks Capture - Settings: Tags: Added Save button for when creating/editing a tag. (#247) Mendix Runtime has been upgraded to Mendix 9.12.3.

. (#643) * Create - Transformation: For new transformers the default output data type is set to the destination attribute data type. * Deploy - Architecture * Planned cloud upgrades can be executed manually before the plan date.

This does not happen anymore and long messages can be written with no further inconvenience. (#635) * Create - Message type: The message type’s display will be updated when you change the its display name in Capture phase or Design phase. (#656) * Create - System Message: Improved creation of enumeration for xml definition attributes so that the enumeration is automatically coupled to the attribute. (#200) * Deploy - Architecture: For new machines, size changes in design architecture were not applied to deploy architecture, until after the first deployment. (#521) * Deploy - Manage: Leaving the API statistics page does not result in error messages. (#541) * Design - Message Mapping: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) * Create - Transformation: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) * Design - Integrations: For the data pipeline integration, errors of message mapping will be ignored. (#592) ====Remarks==== * Capture - Settings: Tags: Added Save button for when creating/editing a tag. (#247) * Mendix Runtime has been upgraded to Mendix 9.12.3.

//__Show values on the runtime level in Deploy Architecture__// We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.

{{/info}} == **Bug Fixes** == //__Gain the ability again to configure certificates in Deploy Architecture again__// In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. //__Ensure that differing container configurations deploy the correct configuration__// When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes.