Search: "deploy architecture"

Overview Security improvements to the eMagiz infrastructure Update Ubuntu version Update Docker version Update control agent version Update Authorization Server (if applicable) Update Steps Use the final R18 template (service affecting) (duration: 15 minutes) 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.

**Overview** * Security improvements to the eMagiz infrastructure * Update Ubuntu version * Update Docker version * Update control agent version * Update Authorization Server (if applicable) **Update Steps** * Use the final **R18** template (service affecting) (duration: 15 minutes) * 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.

See this link Update Steps Use the final R6 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.

See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]] **Update Steps** * Use the final R6 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.

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.

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.

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 == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design & Deploy architecture aspects == 2. Key concepts == The eMagiz Cloud is the set of services and machines that make up together the engine in which the integrations are made active.

XL size **> 16Gb memory per machine === 3.3 Cloud sizing advice === In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]] you can see how your current machine(s) can be reviewed for available memory. === 3.4 Impact of Cloud sizing === The actual assigned machine size will be implemented in the Deploy architecture. In case your total runtime and machines are consuming more than the available memory of that specific size, the runtimes will not properly load and become disfunctional.

See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] for more information This count is also handy when verifying the actual assigned values in Deploy Architecture. == 4. Key takeaways == Part of the eMagiz platform is the Cloud which has specific upper limits for sizing.

[[image:Main.Images.Release Blog.WebHome@release-231-manage-log-entries.png]] [[image:Main.Images.Release Blog.WebHome@release-231-flowtest-logs.png]] == **Bug Fixes** == //__Unused properties__// We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. //__Router deletion__// Router containers for failover that were deleted from the Deploy Architecture, are now cleaned up completely from the environment. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

. (#341) Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users. Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects.

These changes will remain active for future operations. (#1537) Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537) Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’.

. (#341) * Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users. * Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects.

These changes will remain active for future operations. (#1537) * Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537) * Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’.

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.