Search: "deploy architecture"

Please find out more here. Bug fixes Deploy - Architecture: The failover container will now be shown correctly.

====Bug fixes==== * Deploy - Architecture: The failover container will now be shown correctly.

Exercise == Below the exercises for this part of the crash course. === 2.1 Deploy architecture === * Apply user management * Ensure to gather all user information that a Producer or Consumer requires to acces the topic == 3.

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. === 3.5 Managing sizing of Event topics === In the Design architecture you can manage your sizing of Event Streaming topics. eMagiz sees the topics as part of the Cloud infrastructure.

And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543) Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.

And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543) * Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

* The status verification gives you the option to monitor the progress of your change To verify the status simply navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu on the white part of the canvas just shy of the integration platform itself.

Key takeaways == * The status verification gives you the option to monitor the progress of your change * Via the details screen in Deploy -> Architecture you can view the last known state == 5.

In other words, the 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.

You can determine both with the help of the Upgrade functionality within Deploy Architecture. When you navigate to Deploy and open the Architecture you can enter "Start Editing" mode.

To activate this functionality navigate to the Upgrade screen via the context menu in Deploy -> Architecture and enable the option Automatic Upgrade.

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 == * Set up certificates within eMagiz Cloud under Deploy -> Architecture, and ensure certificates are properly linked to routes to control access securely. * As the security best practices, for REST services, use OAuth2.0; for both SOAP and REST, combine API-Key with certificates for robust security. * Use the "Apply to environment" button carefully to apply changes across configurations, avoiding unintended impacts. * Restarting runtimes will reset all flows, including infrastructure, to their initial state, so plan and execute with precision. == 5.

Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543) Deploy - Architecture: We improved the auto-healing feature of AWS machines.

. * Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. * Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543) * Deploy - Architecture: We improved the auto-healing feature of AWS machines.