Search: "deploy architecture"

. (#1053) Deploy - Runtime overview: Insight into intended and actual deployments has been improved. Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968) Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977) Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.

Bug fixes Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021) Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030) Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.

. (#1053) * Deploy - Runtime overview: Insight into intended and actual deployments has been improved. * Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968) * Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977) * Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved. * Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved. ====Bug fixes==== * Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021) * Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030) * Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. * Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161) * Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. * Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151) * Manage - Notification settings: Internal recipients are now added correctly.

New features Deploy - Architecture: We added the possibility to register network shares in your container volume settings.

Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860) Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841) Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container. Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699) Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559) Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719) Deploy - Properties: We improved runtime selection when copying properties. (#796) Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696) Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.

====New features==== * Deploy - Architecture: We added the possibility to register network shares in your container volume settings.

It clearly states which Java classes can be used, along with some examples. (#742) * Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823) * Deploy - Releases: We improved the notification pop-ups of failed machine deployments. * Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860) * Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841) * Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container. * Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699) * Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559) * Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719) * Deploy - Properties: We improved runtime selection when copying properties. (#796) * Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696) * Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it. * Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856) * Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486) ====Bug fixes==== * Design - Solution design: We hide systems without functional integration now. (#714) * Create - API Gateway: Security header case insensitive * Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting. * Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546) * Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice.

This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system was impossible. We have now implemented a fix allowing users to run these multi-environment setups on their Windows Server 2022 machines. Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen.

The context menu containing the versions also shows a caption to show what exact component has been right-clicked and whose flow versions are showing (i.e., entry, exit, onramp, offramp) Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits and show a message that changes are pending. (#1079) Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606) Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144) Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen.

This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system was impossible. We have now implemented a fix allowing users to run these multi-environment setups on their Windows Server 2022 machines. * Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen.

The context menu containing the versions also shows a caption to show what exact component has been right-clicked and whose flow versions are showing (i.e., entry, exit, onramp, offramp) * Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits and show a message that changes are pending. (#1079) * Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606) * Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144) * Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen.

Deploy - Releases: The activate release functionality improved performance for 3rd generation models. Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828) Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571) Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.

Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863) Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814) Deploy - Architecture: The deploy runtimes option is only visible for admin.

. * Deploy - Releases: The activate release functionality improved performance for 3rd generation models. * Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828) * Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571) * Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime. * Deploy - Releases - You will be reminded of empty runtimes when activating a release.

====Bug fixes==== * Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508) * Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793) * Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step. * Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863) * Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814) * Deploy - Architecture: The deploy runtimes option is only visible for admin.

Added a search field for 'logger'. Bug fixes Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment. Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)

====Bug fixes==== * Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment

* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)

Afterward, you can run that step again by selecting "Refresh" and "Execute." Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. Bug fixes Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments.

Afterward, you can run that step again by selecting "Refresh" and "Execute." * Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. ====Bug fixes==== * Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. * Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) * Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) * Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. * Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments.

This guide will help you understand how to make these adjustments within the Deploy Architecture, whether you’re working in the cloud or on-premises.

In cases where all or part of the assumptions are violated, you should determine the correct number and based on that change the settings to mimic your calculations. === 3.1 Deploy Architecture === Editing the memory settings can be done within the Deploy Architecture overview.

Pressing this button will send a command to the eMagiz Cloud to change the configuration of your eMagiz Cloud setup based on the changes made in Deploy Architecture. [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--deploy-architecture-apply-to-environment.png]] When you open the context menu on the eMagiz cloud slot itself (right mouse click in Deploy Architecture away from the integration landscape overview) you can access the details page [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--deploy-architecture-cloud-slot-details.png]] On this page, you can track the progress of your update.

Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. Deploy - Architecture: The machine health indicator and other progress bars have been improved visually.

. * Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. * Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. * Deploy - Architecture: The machine health indicator and other progress bars have been improved visually. * Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. * Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.

You can toggle to a higher size machine and effectuate this via Deploy Architecture. Before you can do so, cloud approval is needed.

Service affecting R25 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in one step to use the new R25 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 R25 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in one step to use the new R25 release of the cloud template.

**Update Steps** * Use the final template (service affecting) (duration: 4 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.