Search: "deploy architecture"

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

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 reset does the following on cloud 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.

The first part of the equation can be found under Deploy -> Architecture. The second part can be found under Deploy -> Properties by looking for the {technicalnameproject}.amqp01.host.

Note that for cloud runtimes you can combine this with a cloud template upgrade or by using the Reset functionality offered by eMagiz in Deploy -> Architecture. Note that for on-premise runtimes you will have to do these steps manually.

The native memory is subsequently divided into several categories: * metaspace (used to store information about the classes that have been loaded), * threads (memory used by threads in the JVM), * code cache (memory used by the JIT to store its output), * garbage collection (stores data used by the GC), * symbol (stores symbols such as field names, method signatures, and interned strings) * internal (stores other internal data that does not fit into any of the other areas) As a user, you can influence these heap and native memory settings under Deploy -> Architecture to create the best balance. eMagiz supports this by advising you on the desired setting per JVM (runtime).