Search: "deploy architecture"

Service affecting R25 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in one step to use the new R25 release of the cloud template.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

Service affecting R25 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in one step to use the new R25 release of the cloud template.

**Update Steps** * Use the final template (service affecting) (duration: 4 minutes) ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. ** The runtimes on the machines will be restored using the active release in the eMagiz portal. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in one step to use the new R8 release of the cloud template.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in one step to use the new R8 release of the cloud template.

**Update Steps** * Use the final template (service affecting) (duration: 10 minutes) ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. ** The runtimes on the machines will be restored using the active release in the eMagiz portal. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

Service affecting R18 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in two steps to use the new R18 release of the cloud template.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

Service affecting R18 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in two steps to use the new R18 release of the cloud template.

**Updates** * Ability to fetch Static IP Addresses * New Ubuntu version with new security patches. * Improved Cloud instance status check and auto repair **Update Steps** * Use the intermediate template (non-service affecting) (duration: 4 minutes) ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot. ** The network drive containing the Artemis queue store and your Elastic IPs will remain. * Use the final template (service affecting) (duration: 4 minutes) ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. ** The runtimes on the machines will be restored using the active release in the eMagiz portal. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. Process We upgrade in two steps to use the new R9 release of the cloud template.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. **Process** We upgrade in two steps to use the new R9 release of the cloud template.

**Update Steps** * Use the intermediate template (non-service affecting) (duration: 10 minutes) ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot. ** The network drive containing the Artemis queue store and your Elastic IPs will remain. * Use the final template (service affecting) (duration: 10 minutes) ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. ** The runtimes on the machines will be restored using the active release in the eMagiz portal. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

Update Steps Use the final R7 template (non service affecting) (duration: 4 minutes) User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all images have been installed according to the active release.

**Update Steps** * Use the final R7 template (non service affecting) (duration: 4 minutes) * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all images have been installed according to the active release. ** Check if messages pass through the bus by verifying a critical message flow in external systems.

User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems