Search: "deploy architecture"

. === 2.1 Define and write a header line === Navigate to Deploy -> Architecture and look at the Volume mapping options, read the help texts, and play around with the settings (if it is not a customer environment).

* The status verification gives you the option to monitor the progress of your change To verify the status simply navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu on the white part of the canvas just shy of the integration platform itself.

Key takeaways == * The status verification gives you the option to monitor the progress of your change * Via the details screen in Deploy -> Architecture you can view the last known state == 5.

In other words, the cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting for instance) are available for your environment.

You can determine both with the help of the Upgrade functionality within Deploy Architecture. When you navigate to Deploy and open the Architecture you can enter "Start Editing" mode.

To activate this functionality navigate to the Upgrade screen via the context menu in Deploy -> Architecture and enable the option Automatic Upgrade.

The first part of the equation can be found under Deploy -> Architecture. The second part can be found under Deploy -> Properties by looking for the {technicalnameproject}.amqp01.host.

{{info}}Note that when running your web service in the eMagiz cloud, the first part (the host part) will change depending on your configuration in Deploy Architecture and the cloud slot on which you are running.

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

* 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

First, you must navigate to Deploy -> Architecture on the model level. This overview lets you access the Volume mapping per runtime deployed on-premise.