Search: "deploy architecture"
Last modified by Rico Kieboom on 2022/04/11 14:18
Refine your search
Select a category and activate filters on the current results
Result type
- 157Document
- 10Attachment
Location
- 167Home
Language
- 159English
- 8No language
Last modification date
- Sort by:
- Relevance
R11 Docker - Double lane
Located in
- Rendered document content
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.
- Raw document content
. * 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.
Apply to environment
Located in
- Raw document content
. * With "apply to environment", we mean: Actualizing all changes, with an indirect effect, within the eMagiz Cloud that were made by users on the Deploy Architecture canvas after the last press on this button. == 3.
…As we saw in previous microlearnings and will see in microlearnings to come with regards to cloud management is that some actions in Deploy Architecture have a direct effect (i.e. Slot Wakeup, Restart Runtime, Reset Runtime, etc.) and others have an indirect effect (i.e.
…{{/info}} So, in short, when you execute one (or more) actions on Deploy Architecture that have an indirect effect, you need to press Apply to Environment to actualize the changes within the eMagiz Cloud.
eMagiz Deploy agent
Located in
- Raw document content
The exact command to run inside the Docker instance is specific for the machine configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal under Deploy Architecture.
…This way, deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system is possible.
234 - Alert Adventures
Located in
- Rendered document content
Please find out more here. Bug fixes Deploy - Architecture: The failover container will now be shown correctly.
- Raw document content
====Bug fixes==== * Deploy - Architecture: The failover container will now be shown correctly.
236 - Another Agent
Located in
- Rendered document content
And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543) Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
- Raw document content
And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543) * Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
Allow access to Consumers/Producers
Located in
- Raw document content
Exercise == Below the exercises for this part of the crash course. === 2.1 Deploy architecture === * Apply user management * Ensure to gather all user information that a Producer or Consumer requires to acces the topic == 3.
Define deployment plan & create release
Located in
- Raw document content
Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.
Define deployment plan & create release
Located in
- Raw document content
Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.
Consequences of cloud size
Located in
- Raw document content
Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design & Deploy architecture aspects == 2. Key concepts == The eMagiz Cloud is the set of services and machines that make up together the engine in which the integrations are made active.
…XL size **> 16Gb memory per machine === 3.3 Cloud sizing advice === In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]] you can see how your current machine(s) can be reviewed for available memory. === 3.4 Impact of Cloud sizing === The actual assigned machine size will be implemented in the Deploy architecture. In case your total runtime and machines are consuming more than the available memory of that specific size, the runtimes will not properly load and become disfunctional.
…See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] for more information This count is also handy when verifying the actual assigned values in Deploy Architecture. === 3.5 Managing sizing of Event topics === In the Design architecture you can manage your sizing of Event Streaming topics. eMagiz sees the topics as part of the Cloud infrastructure.
Verify the status of ongoing change
Located in
- Raw document content
* 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.