Search: "deploy architecture"

. (#687) Bug fixes Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.

. (#687) ====Bug fixes==== * Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) * Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. * Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087) * Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.

//__Deploy architecture changes__// The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed.

//__Architecture - Routes__// We have improved the help texts for the "Routes" configuration in Deploy - Architecture. == **Bug Fixes** == //__Deploy - User Management__~*// For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.

Setting the release means creating a new Docker image. * Deploy Architecture ** You can see the running status of a Docker image at every runtime.

The following will change in this new configuration. *** All-entry will be split into separate entries *** WSDL will be automatically generated based on your system messages *** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture *** Configuration of endpoints is streamlined better between cloud-hosted endpoints and on-premise endpoints * Handling local file communication ** As our third-generation runtime uses Docker technology, your containers are, by default, closed off from their host.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.

Note that you can automatically upgrade your Cloud Template with the Upgrade functionality located in Deploy -> Architecture. With the help of this function, you can schedule the cloud template upgrade at a time most convenient for you.

This allows you to transfer them from Design Architecture to Deploy Architecture to be utilized in future deployments. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

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

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.Fundamentals.fundamental-runtime-generation3||target="blank"]] itself .

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.