Search: "deploy architecture"

These prechecks can be executed via Deploy > Architecture. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Using it on Production would probably mean that the cure is worse than your problem. 1. Navigate to Deploy -> Architecture for the bus you want to perform this action 2.

To execute these actions 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 machine (via a right mouse click) and select one of the options (Restart, Start or Stop).

You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.

//__Machine details pop-up__// * The machine details pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. * The machine health indicator has been improved visually. * Several progress bars have been improved visually.

//__Improved sorting of Design and Deploy archticture__// With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design phase Architecture and Deploy Architecture * Created several API gateway integrations == 2.

Suggested Additional Readings == If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following link: * [[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"]] *** [[Flow Editor - Basics (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-flow-editor-basics||target="blank"]] *** [[Promote flows to deploy (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-promote-flows-to-deploy||target="blank"]] ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] *** [[Configure A Backend Operation (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-configure-backend-operation||target="blank"]] *** [[Setting up Entry gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-entry-gate||target="blank"]] * [[Novice Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] ** [[SOAP Web service Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome||target="blank"]] *** [[SOAP Headers (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-soap-headers||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Testing API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing API Gateway.WebHome||target="blank"]] *** [[Testing API Gateway (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing API Gateway.intermediate-testing-emagiz-api-gateway-testing-api-gateway||target="blank"]] * [[Advanced Level (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"]] *** [[API Gateway Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-apigw-architecture.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"]] ** [[API Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.API Management.WebHome||target="blank"]] *** [[Running part of your API Gateway solution on-premise (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.API Management.advanced-api-management-running-part-of-your-api-gateway-solution-on-premise||target="blank"]] * [[Exit Gate (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

//__Improved auditability on Deploy Architecture__// To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).

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