Search: "deploy architecture"

{{container}}{{container layoutStyle="columns"}}((( With this exercise, we learn how to use the "apply to environment" functionality in Deploy -> Architecture. This functionality is a key component in sending changes to our eMagiz cloud to actualize these changes.

To complete this exercise you need to execute the following steps: * Navigate to Deploy -> Architecture * Enter "Start Editing" mode and open the context menu (by clicking on the white area of the canvas) * Select the certificate option and fill in the following things: ** CN Name ** Client Name * Save your changes on certificate level * Open the context menu again and select the route option. * Fill in the following things: ** DNS Left most label ** Port ** Runtime(s) ** Certificate to use * Save your changes == 3.

. * With "apply to environment", we mean: Actualizing all changes, with an indirect effect, within the eMagiz Cloud that were made by users on the Deploy Architecture canvas after the last press on this button. == 3.

As we saw in previous microlearnings and will see in microlearnings to come with regards to cloud management is that some actions in Deploy Architecture have a direct effect (i.e. Slot Wakeup, Restart Runtime, Reset Runtime, etc.) and others have an indirect effect (i.e.

{{/info}} So, in short, when you execute one (or more) actions on Deploy Architecture that have an indirect effect, you need to press Apply to Environment to actualize the changes within the eMagiz Cloud.

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.

Configuring routes is relatively simple and can be done via the Deploy Architecture canvas. As you by now probably know we first need to enter "Start Editing" mode.