Search: "deploy architecture"

Only applies to third generation runtimes. Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture.

Bug fixes General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models. Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation.

Only applies to third generation runtimes. * Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture.

====Bug fixes==== * General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models. * Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation.

Please check out the cloud template release notes for more information Minor changes Infra - Control Tower: In addition to credentials, receive model metrics, pause/un-pause notifications status, and notification recipients daily. Deploy-Architecture: Added the ability to choose a previously active release for a single container for disaster recovery. Note that this functionality is only available for the new monitoring stack. Deploy - Architecture: Configure HTTP settings for containers that run on the new monitoring stack, enabling TLS and two-way SSL use for on-premises deployments.

It is not recommended to use it in production environments yet, as this feature can only be configured manually for now. Deploy - Architecture: Manage routes and certificates in Deploy instead of solely AWS Slots.

Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information ====Minor changes==== * Infra - Control Tower: In addition to credentials, receive model metrics, pause/un-pause notifications status, and notification recipients daily. * Deploy-Architecture: Added the ability to choose a previously active release for a single container for disaster recovery. Note that this functionality is only available for the new monitoring stack. * Deploy - Architecture: Configure HTTP settings for containers that run on the new monitoring stack, enabling TLS and two-way SSL use for on-premises deployments. * Create - Flow designer: Updated versions of the 'HTTP Security' and 'Authentication manager' components allow the use of HTTP Basic authentication for your HTTP services if they run on the new monitoring stack. It is not recommended to use it in production environments yet, as this feature can only be configured manually for now. * Deploy - Architecture: Manage routes and certificates in Deploy instead of solely AWS Slots.

New features Design - API Gateway: The path length in OpenAPI specification that can be imported is now increased to a maximum of 300 characters. eMagiz Mendix Connector: We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. Deploy - Architecture: We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal.

Create - Flow Designer: Default error handling is now migrated correctly when moving to the current runtime architecture. (#1266) Create - Flow Designer: If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab. Deploy - Architecture: SFTP session factories did not close their connection after it was complete.

A new runtime image containing a fix is available, please check it out here. Deploy - Architecture: Passwords for network volumes are now hidden on the machine after deployment. (#984) Deploy - Unused properties: eMagiz properties, which cannot be edited or removed by a user, are not shown in the unused properties overview anymore. (#1267) All: Legacy pages are now hidden correctly for models running on the current runtime architecture. (#1068)

. * eMagiz Mendix Connector: We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. * Deploy - Architecture: We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal.

====Bug fixes==== * Create - Add integrations: When removing an integration from Create, the Create phase is now correctly updated. (#1053) * Create - Flow Designer: Enumeration values for event processors can now be edited in Create. * Create - Flow Designer: Default error handling is now migrated correctly when moving to the current runtime architecture. (#1266) * Create - Flow Designer: If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab. * Deploy - Architecture: SFTP session factories did not close their connection after it was complete.

A new runtime image containing a fix is available, please check it out [[here>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]]. * Deploy - Architecture: Passwords for network volumes are now hidden on the machine after deployment. (#984) * Deploy - Unused properties: eMagiz properties, which cannot be edited or removed by a user, are not shown in the unused properties overview anymore. (#1267) * All: Legacy pages are now hidden correctly for models running on the current runtime architecture. (#1068)

. === 3.7 Apply to environment (per environment) === Navigate to Deploy -> Architecture and press apply to environment. If you have not executed the previous steps correctly, you will get a warning that you are not allowed to do this.

. (#576) Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps. Deploy - Architecture: Added reset feature for 3rd generation runtimes.

Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.

. (#576) * Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps. * Deploy - Architecture: Added reset feature for 3rd generation runtimes. ====Bug fixes==== * Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows. * Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances. * Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. * Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) * Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. * Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.

Service affecting R8 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 R8 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 R8 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 R8 release of the cloud template.

**Update Steps** * 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.

. (#1463) Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618) Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture.

. (#1463) * Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618) * Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture.

Service affecting R18 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 R18 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 R18 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 R18 release of the cloud template.

**Updates** * Ability to fetch Static IP Addresses * New Ubuntu version with new security patches. * Improved Cloud instance status check and auto repair **Update Steps** * Use the intermediate template (non-service affecting) (duration: 4 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: 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.

Deploy Phase Possibilities == === 3.1 Deploy Architecture === After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture.

As you might have noticed in the Deploy>Architecture earlier when opening the "Failover" tab in your machines' "Details", there are properties regarding the machines' "Internal IP address" and "Failover port".

To continue failover behavior, please use the steps above in Deploy -> Architecture. ===== 3.5.1.4 Leader (single node) Status ===== The last possible status is Leader (single node).

Please check out the cloud template release notes for more information. Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

Furthermore, there is no deployment step configuration to "enable" triggers anymore. Bug fixes Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957) Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.

Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. * Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. * Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

====Bug fixes==== * Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957) * Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet. * Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases.