Search: "deploy architecture"

Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design and Deploy Architecture phase. == 2. Key concepts == In the various microlearnings until the intermediate level, we have explained the [[eMagiz runtime>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-install-local-connector.WebHome||target="blank"]] itself .

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

[[image:Main.Images.Release Blog.WebHome@release-254-define-headers.png]] //__Refresh Runtimes__// We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. [[image:Main.Images.Release Blog.WebHome@release-254-deploy-refresh-runtime.png]] == **Bug Fixes** == //__Resizing columns__// * Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. * Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup.

Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan. Deploy - Architecture: Certificates only editable by system admin.

. * Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan. * Deploy - Architecture: Certificates only editable by system admin. * Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions.

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.