Search: "deploy architecture"

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

//__Endpoint URL Information__// Endpoint URL for routes are shown on the view/edit pop-up of specific routes on the Deploy architecture that run in your cloud. Additionally, the help text explains how the endpoint URL is constructed. == **Bug Fixes** == //__Display Name__// System display names in all phases are updated progressively with the change in the Capture phase.

* Unit test completed on Acceptance * Test scenarios are accepted by the business * Criteria for a successful end to end test known * Acceptance environments of involved systems are representative for the integration to test * Dates are agreed jointly to run the test * eMagiz specifics * All flows are released on Acceptance * Connectivity check done on Acceptance * Properties are properly configured on Acceptance == 3.6 Tollgate T6 – Go-live Ready == The objective of this tollgate is to prepare the Go-live of the Release to production * End to end test completed * Go live plan ready and reviewed * Go live date agreed with the business * Rollback scenario's ready * Risk assessment completed and actions set out * eMagiz specifics * All flows are inside a proper release * Connectivity check done on Production * Properties are properly configured on Production * Deploy Architecture current == 3.7 Tollgate T7 – Go-live Done == The objective of this tollgate is to validate the production environment if the Release is running on Production

Configuring routes is relatively simple and can be done via the Deploy Architecture canvas. As you by now probably know we first need to enter "Start Editing" mode.

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"]] ** [[Discovery (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-discovery.WebHome||target="blank"]] ** [[Multi-Model Explained (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome||target="blank"]] * [[Crash Courses (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"]] *** [[Storing Metadata - Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-storing-metadata||target="blank"]] *** [[Settings (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-project-settings||target="blank"]] ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] *** [[Finishing the Design Phase (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-finishing-the-design-phase.WebHome||target="blank"]] * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]] *** [[Understanding Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-understanding-design-architecture||target="blank"]] ** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Lifecycle Management.WebHome||target="blank"]] *** [[Cleanup Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Lifecycle Management.intermediate-lifecycle-management-cleanup-design-architecture||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"]] * [[Design Architecture (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

To resolve this, please restart the containers, which can be done via a deployment plan or the deploy architecture.{{/warning}} ===3.4 Uninstall Docker=== To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights: {{code language="cmd"}} Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1 {{/code}} Example usage: {{code language="cmd"}} .

//__Show status on machine level under Deploy Architecture__// With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture. //__Improved validation feedback on non-supported WSS4J interceptor __// We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.

Furthermore, the components of the API Gateway are the following: ** Gateway infra ** All entry (later replaced with single entries per operation) ** Exit gate (contains a connection to backend provider) These components can be made part of the Release and Deployment plans. The Deploy Architecture will contain the Cloud architecture to be deployed and can be applied with the Design Architecture.