Search: "deploy architecture"

. === 3.1 How to use it === You can access this functionality via the [["Deploy Architecture">>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-understanding-deploy-architecture-basic||target="blank"]] overview in the Deploy phase.

Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] *** [[Understanding Deploy Architecture - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-understanding-deploy-architecture-basic||target="blank"]] * [[Start Stop Flows (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

{{container}} {{container layoutStyle="columns"}} ((( In this microlearning, we will focus on how to influence the runtime settings via the Deploy -> Architecture overview. With the help of this functionality, you can configure two settings.

For example, part of these settings is located on the runtime level in Deploy -> Architecture. Executing a right-click while in "Start Editing" mode on a runtime provides you with one of the following context menus.

Key takeaways == * On the runtime level in Deploy -> Architecture, you have a context menu item called "Runtime Settings." * In this context menu item, you can configure the HTTP Settings and whether the control bus is enabled. * HTTP Settings are needed when hosting a SOAP or REST web service. ** When enabling, the port needs to be filled in. ** Optionally, you can configure one-way or two-way SSL for an on-premise endpoint. * By disabling the control bus, you will lose (parts of) the functionality that allows you to view or halt data. ** Queue browser. ** Message redelivery. ** Start/Stop flow components. * Changes must be deployed by creating a new release and deploying it via a deployment plan. == 5.

This guide will help you understand how to make these adjustments within the Deploy Architecture, whether you’re working in the cloud or on-premises.

In cases where all or part of the assumptions are violated, you should determine the correct number and based on that change the settings to mimic your calculations. === 3.1 Deploy Architecture === Editing the memory settings can be done within the Deploy Architecture overview.

Pressing this button will send a command to the eMagiz Cloud to change the configuration of your eMagiz Cloud setup based on the changes made in Deploy Architecture. [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--deploy-architecture-apply-to-environment.png]] When you open the context menu on the eMagiz cloud slot itself (right mouse click in Deploy Architecture away from the integration landscape overview) you can access the details page [[image:Main.Images.Microlearning.WebHome@intermediate-emagiz-runtime-management-configure-needed-memory--deploy-architecture-cloud-slot-details.png]] On this page, you can track the progress of your update.

The exact command to run inside the Docker instance is specific for the machine configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal under Deploy Architecture.

This way, deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system is possible.

To execute this action please navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called restart runtime.

[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] To execute this action please navigate to Deploy -> Architecture. After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called "Reset H2".

. * The reset does the following on runtime level: ** Stops the runtime service (if running) ** Removes data (except Artemis folder + revision info) ** Removes local repository folder ** Starts the runtime service (if stopped at step 1) * With a reset, you start with a clean slate ** Flow version could be different based on changes in the release ** Custom H2 database is emptied To execute this action please navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called "Reset runtime".