Search: "deploy architecture"

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.

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

. === 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.

Please learn more about our Runtime Image release notes. Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889) Minor changes Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.

Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) Deploy - User Management: Roles are sorted alphabetically. (#806) Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup.

Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]]. * Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889) ====Minor changes==== * Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information. * Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors. * Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) * Deploy - User Management: Roles are sorted alphabetically. (#806) * Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup.

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.

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

Update Steps Use the final R8 template (non service affecting) (duration: 4 minutes) User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all images have been installed according to the active release.

**Update Steps** * Use the final R8 template (non service affecting) (duration: 4 minutes) * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all images have been installed according to the active release. ** Check if messages pass through the bus by verifying a critical message flow in external systems.

Update Steps Use the final R17 template (non service affecting) (duration: 4 minutes) User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all images have been installed according to the active release.

**Update Steps** * Use the final R17 template (non service affecting) (duration: 4 minutes) * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all images have been installed according to the active release. ** Check if messages pass through the bus by verifying a critical message flow in external systems.

Update Steps Use the final template (non-service affecting) 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.

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

Update Steps Use the final template (non-service affecting) 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.

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

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.

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

Prerequisites == * Basic knowledge of the eMagiz platform * Basic Understanding of certificates * Flow that hosts the web service is successfully created and deployed to the correct environment * Route in Deploy Architecture has been configured for this specific web service == 2.

Important things to remember are: * Configuration on eMagiz Cloud level is done via Deploy -> Architecture * Certificate is generated via the support department (with or without CSR) * No actions are needed on flow level, only on Cloud level * All you need for the configuration is the common name of the certificate Now that we have introduced the topic let us see how to configure the certificate within Deploy -> Architecture.

Key takeaways == * Certificates serve as essential tools for establishing trust between parties by verifying identities, which is crucial for secure communications. * Easily enhance the security of your eMagiz web service in the eMagiz Cloud by configuring it with certificates, ensuring that only authenticated clients can access it. * The main configuration happens at the eMagiz Cloud level through the Deploy -> Architecture section, with no changes needed at the flow level. * When applying changes, ensure you’re aware of other modifications, as they will be updated simultaneously in the eMagiz Cloud. == 5.