Search: "restart runtime"

Restart Runtime

intermediate-emagiz-runtime-management-restart-runtime

. * With runtime, we mean: This is the component in which the individual integration flows are deployed into. == 3. Restart runtime == In this microlearning, we will focus on the action to restart a runtime.

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.Microlearning.WebHome@novice-emagiz-cloud-management-restart-runtime--context-menu-runtime.png]] After a grace period please execute the standard checks, i.e checking the logs under Manage -> Log Entries and verify if you can access the runtimes via runtime dashboard. == 4.

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: * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] *** [[Reset Runtime (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-reset-runtime.WebHome||target="blank"]] * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Recovery Guide (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.WebHome||target="blank"]] *** [[Signal received - Recovery Needed (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.expert-recovery-guide-signals-reproducable-steps||target="blank"]] * [[Restart Runtime (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

In our microlearnings of [[cloud management>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]], we have encountered actions that impact the eMagiz Cloud directly (i.e., Slot Wakeup, Restart Runtime, Reset Runtime, etc.) and those with an indirect effect (i.e., Add Route, Add Certificate, Remove Runtime, etc.).

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.

| **Direct Effect** | **Indirect Effect** | | --------------------------------------- | ----------------------------------------- | | Restart Runtime (Not JMS) | Add Route | | Restart Runtime (JMS) | Update Route | | Reset Runtime (Not JMS) | Delete Route | | Reset Runtime (JMS) | Add Certificate | | Restart Runtime (Not JMS) | Update Certificate | | Restart Connector Machine | Delete Certificate | | Restart Core Machine | Add runtime to connector machine | | Stop Connector Machine | Add runtime to core machine | | Stop Core Machine | Remove runtime from connector machine | | Start Connector Machine | Remove runtime from core machine | | Start Core Machine | Update memory settings runtime (not JMS) | | Wake up Cloud Slot | Update memory settings runtime (JMS) | | Put Cloud Slot to sleep | Change Cloud Template | | Clean Store | | Upgrade Cloud Slot* | {{info}}~* Note that the upgrade of the cloud slot can be planned for a later moment in time.

{{container}} {{container layoutStyle="columns"}} ((( In the previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]], we covered how to restart runtimes without affecting their underlying data or configurations.

Reset runtime == In the previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]], we learned about restarting runtimes. In that [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]], we learned that restarting the runtime does not affect flows, data, psychical hardware, or otherwise.

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: * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] *** [[Restart Runtime (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]] *** [[Reset H2 Database (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]] * [[Advanced Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] ** [[Key Concepts (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Key Concepts.WebHome||target="blank"]] *** [[What data is stored on runtime level (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Key Concepts.advanced-key-platform-concepts-what-data-is-stored-on-runtime-level||target="blank"]] * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Recovery Guide (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.WebHome||target="blank"]] *** [[Signal received - Recovery Needed (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Recovery Guide.expert-recovery-guide-signals-reproducable-steps||target="blank"]] ** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.WebHome||target="blank"]] ** [[Clean Store (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]] * [[Reset Runtime (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

{{container}} {{container layoutStyle="columns"}} ((( In a previous microlearning, we learned about restarting runtimes. In that microlearning, we learned that restarting the runtime does not affect flows, data, psychical hardware, or otherwise.

Reset runtime == In a previous microlearning, we learned about restarting runtimes. In that microlearning, we learned that restarting the runtime does not affect flows, data, psychical hardware, or otherwise.

Search for the runtime for which you have received the alert and activate the drop down menu via a right click of your mouse 1*. Select **[[Restart Runtime>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]]**. 1.

Right mouse click on the JMS runtime and select Restart Runtime 1. Restart the JMS (backup) runtime 1*.

Right mouse click on the JMS runtime and select Restart Runtime 1. [[Check message traffic>>||anchor="H3.12Checkmessagetraffic"]] 1*.

. * The first is to execute a "restart runtime" action via Deploy Architecture or the on-premise server. * Secondly, you could deploy a new version of the infra (via the Releases functionality).

On top of that you can execute a lot of actions on the runtimes, such as: * [[Start/Stop Flows>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]] * [[Restart Runtime>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]] * [[Reset Runtime>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-reset-runtime.WebHome||target="blank"]] * [[Reset H2>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]] === 3.3 Used and available size === Apart from determining where an instance (runtime) should be running (cloud or on-premise) the Deploy Architecture also tells you how much memory (i.e. size) is already claimed by the runtimes running on the machine (including machine memory) and how much is still available to be distributed or to be assigned to a new runtime.

Suggested Additional Readings == * [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] ** [[eMagiz Architecture (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-architecture.WebHome||target="blank"]] ** [[eMagiz Cloud (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-cloud-inner-workings||target="blank"]] * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] ** [[File Based Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.WebHome||target="blank"]] *** [[Volume Mapping (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] ** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] *** [[Runtime Settings (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-runtime-settings.WebHome||target="blank"]] *** [[Start/Stop Flows (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]] *** [[Restart Runtime (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-restart-runtime.WebHome||target="blank"]] *** [[Reset Runtime (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-reset-runtime.WebHome||target="blank"]] *** [[Reset H2 (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]] * [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]] *** [[Architectural Runtime Decisions (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-runtime-decision.WebHome||target="blank"]] *** [[Key differences Design & Deploy Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-diffs-design-deploy.WebHome||target="blank"]] *** [[Consequences Of Cloud Size (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-consequence-size-cloud.WebHome||target="blank"]] * [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] *** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] * [[Deploy Architecture (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

* Install (updated) flows from that container * Stop all flows from that container * Start all flows from that container * Remove all old flows from that container === 3.3 Restart runtime === In specific cases, an entire runtime can be just restarted.

. ** Flows return in original state * By stopping the machine, you stop the machine (double lane) or you terminate the machine (single lane) ** Termination of the machine (single lane) ** Runtime states are temporarily stored in EFS (single lane) ** Dorment machine (double lane) ** In case you stop the core machine on which the JMS is running no data traffic can happen (single and double lane) * By starting the machine, you start the machine (double lane) or you generate a new machine (single lane) ** Generation of the machine (single lane) ** Runtime states are retrieved from EFS (single lane) ** Start the virtual machine, the machine may have moved to different physical hardware (double lane) == 3. Restart runtime == In this microlearning, we will focus on the action to (re)start or stop a machine.

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